To Spec#
Synthesize the current conversation into a markdown spec under
resources/agent-docs/specs/.
Description#
The to-spec skill takes the current conversation context and codebase
understanding and produces a spec (PRD) — no interview, just synthesis
of what has already been discussed. If decisions are still open it
recommends grill-me first rather than guessing.
The spec is written to resources/agent-docs/specs/<NNN>-<slug>/spec.md with
sections for problem statement, solution, an extensive user-story list,
implementation decisions, testing decisions (including the agreed test
seams), a slices checklist (populated later by to-slices), out of
scope, and further notes.
Test seams are sketched and confirmed with the user before the spec is written: existing seams preferred, placed as high as possible, as few as possible.
Triggers#
/wf:to-spec
Also: “turn this into a spec”, “capture this as a spec”, “write the PRD”.
Output#
resources/agent-docs/specs/<NNN>-<slug>/spec.md, using the project glossary
vocabulary and respecting existing ADRs. The whole-spec completion
review is later performed by team-review-impl against this file.
Attribution#
Adapted from the to-spec skill in
mattpocock/skills (MIT
license). Publishes a markdown file instead of a tracker issue.