spec-assistant

To write testable feature specifications, use a guided Q&A process that iteratively gathers requirements across six core areas including Commands, Testing, and Boundaries. This structured discovery defines scope and acceptance criteria before coding begins.

The best way to gather clear requirements for technical blueprinting is through collaborative discovery. By asking targeted questions, stakeholders define success metrics and acceptance criteria within a structured framework, reducing miscommunication and rework.

You structure feature planning using a phase-based workflow by progressing sequentially through SPECIFY, PLAN, TASKS, and IMPLEMENT phases. Gated progress ensures quality checks pass at each stage before moving to actual coding or technical blueprinting.

Yes, collaborative Q&A works for defining project structure and code style guidelines. The framework organizes information into six core areas, explicitly ensuring code style, git workflow, and project structure are clarified during the discovery process.

Yes, you can use guided discovery for gathering requirements across product, design, and engineering teams. The iterative questioning process builds shared specifications and aligns cross-functional stakeholders on acceptance criteria before implementation starts.

Feature planning requires gated progress before implementation to enforce self-verification prompts and ensure quality. Completing the SPECIFY, PLAN, and TASKS phases prevents premature coding, reducing rework and miscommunication across technical teams.