spec-workflow
**WORKFLOW SKILL** — Interview the user about specification changes and generate one or more standalone SPEC.md documents (one per spec folder) that serve as a high-level overview of the component or process: contract, behavior, and business intent, captured as user stories and EARS-notation acceptance criteria. Technical architecture, diagrams, and implementation-level detail live in companion documents (DESIGN.md, DOMAIN.md, DATABASE.md, KAFKA.md, CONVENTIONS.md). The agent uses SPEC.md plus companion documents together for planning and code generation.
Pinned to revision e61398bb2f69, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.