bmad-quick-spec

To turn a feature idea into an implementation-ready tech spec, describe the desired change to trigger a structured workflow. It maps your request through frontmatter creation, task breakdown, acceptance criteria, and a multi-step review cycle.

The best way to document a feature delta is using a repeatable tech-spec workflow that covers scope, constraints, and acceptance criteria. This process ensures clear handoffs and reduces back-and-forth communication with developers.

The tech spec generation workflow handles iterative refinement through optional elicitation and review steps. After generating the initial implementation plan, you can collaborate and refine the acceptance criteria and task breakdown across multiple steps.

Yes, you can use this specification workflow for rapid feature changes in existing software projects. It enables consistent, reusable specs by mapping user requests directly to an end-to-end implementation plan starting from a delta.

No specific frameworks are required to generate implementation-ready specifications. The workflow operates independently by structuring your feature request into a reusable template with clear frontmatter, task breakdown, and acceptance criteria.