bmad-quick-dev

To turn a feature request into a ready-for-development spec, provide your developer intent along with relevant planning artifacts. The system fills the spec template, enforces Ready-for-Development standards, and preserves frozen intent blocks.

Epic context compilation works by distilling your existing planning artifacts into focused epic-<N>-context.md files. This provides targeted context when implementing epic-linked stories, ensuring the generated code aligns with broader project goals.

Yes, you can enforce test gates and review loops during code generation. The system drives a step-by-step workflow through clarify, plan, implement, review, and present stages, structuring review loops and requiring tests for implementation tasks.

To generate testable code artifacts, you need reachable repository context and planning documents. Supplying these inputs validates outputs and allows the system to compile epic context for story-based work, bug fixes, or refactors.

Yes, this workflow automation tool supports bug fixes and refactoring tasks. It applies implementation pipelines to these scenarios by converting informal intent into structured implementation tasks with required tests and a suggested review order.

Code generation requires reachable repository context because the system uses it to validate outputs against your actual software project. Without this context and planning documents, it cannot accurately enforce test gates or compile epic context.