write-spec
Installation
SKILL.md
Write Spec
Synthesize what is already settled into a spec, adding the uncontested facts a decision record drops: no interview, no new decisions. If the work fits in the current context, say once that implementing directly is cheaper.
If an argument names a file, issue, or URL, read it in full first.
With no argument, propose the one spec/features/<slug>/decisions.md that has no spec.md beside it, or ask.
Read spec/vision.md and spec/glossary.md if they exist.
1. Ground it in the code
Run three searches, as parallel subagents if your harness has them:
- Locate: where the affected code lives.
- Analyze: how the current implementation works, traced.
- Prior art: the closest existing feature of the same shape, and its tests.
Each is a documentarian: describe, never design.
Also look for a verification skill: a project skill (in .agents/skills/ or a harness skills folder) whose SKILL.md says it runs the product and records whether a check passed.