spec-writer

To write a specification for agent-driven development, you convert informal feature ideas into a structured .spec.md file containing stable REQ IDs and Given/When/Then acceptance criteria for main flows and edge cases.

Defining scope boundaries and guardrails involves creating a bounded specification that explicitly separates in-scope and out-of-scope elements, while adding Always allowed, Ask before, and Never do sections to prevent unsafe changes.

Creating a testable specification from a bug report requires translating the observed behavior into an explicit verification plan with traceable requirements, ensuring the output defines a clear Definition of Done.

Yes, you can use this specification format with missing details because it accommodates ambiguity by automatically generating an open questions or assumptions section to clarify intent before implementation begins.

Rewriting an imprecise specification does not require discarding existing acceptance criteria if they remain valid, but it does enforce standard Given/When/Then formats and stable REQ IDs to ensure traceability.

A limitation of converting informal ideas is that the resulting specification only captures explicitly stated intent and defined scope boundaries, meaning completely unstated assumptions might require manual clarification through open questions.