bmad-quick-dev

A reviewable implementation spec requires routing your request through workflow checkpoints that enforce specification quality. This ensures your software engineering task includes discovery, validation, review-ready acceptance criteria, and a governed execution path.

You can use this workflow for bug fixes and refactoring, not only new feature work. It applies to any code changes that need routing, planning, implementation, adversarial review, and final presentation within software engineering tasks.

The best way to structure code review acceptance criteria is to enforce specification quality during the planning phase. This produces a hardened, reviewable implementation spec that drives a disciplined workflow through implementation and adversarial review.

This specification workflow supports one-shot implementation, planned paths, and resume paths. It clarifies and routes intent by distinguishing between these execution methods to govern the implementation workflow appropriately for your software engineering tasks.

Implementation plans skip discovery and validation when they lack enforced workflow checkpoints. Moving from a vague change request to a hardened spec requires a governed execution path that validates intent and enforces specification quality before development begins.