Writing

Removes Wikipedia-documented “AI writing” tells—significance inflation, -ing fluff, em-dash stacks, chatbot closers—and runs a final “still obviously AI?” pass before shipping prose.

Frames review requests around risk, test gaps, and rollout impact—so reviewers know where to spend their limited attention.

Turns frozen requirements into step-by-step implementation plans with clear file touchpoints, checkpoints, and verifiable outcomes before any code lands.

Structures responses to review feedback—separating nitpicks from defects and tracking follow-ups—so merges stay focused and respectful.