writing-for-agents

Diagnosis loop for hard bugs and performance regressions.

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…

Shared vocabulary for designing deep modules.

Test-driven development.

Build and sharpen a project's domain model.

Build a throwaway prototype to answer a design question.

Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time…

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

Grill the user relentlessly about a plan, decision, or idea.

Ask which skill or flow fits your situation.