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. If the conversation hasn't reached a shared understanding yet, that's a grill-me session, not a spec.
The tracker. Read TRACKER.md beside the repo's engineer skill — it names the tracker, gives its commands, and maps meanings to this repo's label strings. If there is none, resolve the tracker for this run from what the user gave you, the git remote, and whichever CLI is installed and authenticated; default to a directory of local markdown files when nothing resolves.
The engineer skill's directory varies by harness, so find it by glob:
ls */skills/*-engineer/TRACKER.md .*/skills/*-engineer/TRACKER.md 2>/dev/null
Process
-
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.
-
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.
- Write the spec using the template below, then publish it to the tracker. Apply the label
TRACKER.mdnames for agent-ready work; if it names none, skip the labelling and say so.