spec-flow
Spec Flow
Keep a trace of intent and decisions in the repo without letting stale documents pass as current truth. The governing idea: a document's location states its status. A reader, human or agent, knows from the directory alone whether a file describes intent, reality, or history.
This skill owns the layout, the format of each document type, and the transitions between states.
A feature moves through propose → (implementation) → verify → archive. init runs once per repo. decide applies at any point.
Sources: plan and spec formats adapted from OpenSpec's spec-driven schema — https://github.com/Fission-AI/OpenSpec/blob/main/schemas/spec-driven/schema.yaml · the interview in propose adapted from Matt Pocock's grilling skill — https://github.com/mattpocock/skills