bmad-quick-devlisted

> **Attribution:** Sourced from [bmad-code-org/BMAD-METHOD](https://github.com/bmad-code-org/BMAD-METHOD) by [BMAD Code Org](https://github.com/bmad-code-org). # Quick Dev New Preview Workflow **Goal:** Turn user intent into a hardened, reviewable artifact. **CRITICAL:** If a step says "read fully and follow step-XX", you read and follow step-XX. No exceptions. ## READY FOR DEVELOPMENT STANDARD A specification is "Ready for Development" when: - **Actionable**: Every task has a file path and specific action. - **Logical**: Tasks ordered by dependency. - **Testable**: All ACs use Given/When/Then. - **Complete**: No placeholders or TBDs. ## SCOPE STANDARD A specification should target a **single user-facing goal** within **900–1600 tokens**: - **Single goal**: One cohesive feature, even if it spans multiple layers/files. Multi-goal means >=2 **top-level independent shippable deliverables** — each could be reviewed, tested, and merged as a separate PR without breaking the others. Never count surface verbs, "and" conjunctions, or noun phrases. Never split cross-layer implementation details inside one user goal. - Split: "add dark mode toggle AND refactor auth to JWT AND build admin dashboard" - Don't split: "add validation and display errors" / "support drag-and-drop AND paste AND retry" - **900–1600 tokens**: Optimal range for LLM consumption. Below 900 risks ambiguity; above 1600 risks context-rot in implementation agents. - **Neither limit is a gate.** Both are pro