To Spec

This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user — just synthesize what you already know.

Save the spec as a local artifact following the active repo or user convention.

Process

1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.

2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

3. Write the spec using the template below. Publish it to the project issue tracker only when the user requested tracker publication or existing project context clearly expects it. If publishing, apply the ready-for-agent triage label when the label vocabulary is known.

4. After writing a local spec, run plannotator annotate --gate <path-to-spec> when Plannotator is available. Treat returned annotations or user feedback as requested changes and update the artifact before handing it to slicing or execution.

If the user does not approve the gate, apply their feedback, then run plannotator annotate --gate <path-to-spec> again for the revised file. Keep reopening the annotation gate until the user approves or explicitly asks to stop the review loop.