Skip to content
🤖 Consolidated, AI-optimized BMAD docs: llms-full.txt. Fetch this plain text file for complete context.

Implementation FAQ

Quick answers to common questions about implementation in the BMad Method.

Does create-story include implementation context?

Section titled “Does create-story include implementation context?”

Yes! The create-story workflow generates story files that include implementation-specific guidance, references existing patterns from your documentation, and provides technical context. The workflow loads your architecture, PRD, and existing project documentation to create comprehensive stories. For Quick Flow projects using tech-spec, the tech-spec itself is already comprehensive, so stories can be simpler.

After dev-story completes and code-review passes:

  1. Open sprint-status.yaml (created by sprint-planning)
  2. Change the story status from review to done
  3. Save the file

Yes, if you have capacity! Stories within different epics can be worked in parallel. However, stories within the same epic are usually sequential because they build on each other.

What if my story takes longer than estimated?

Section titled “What if my story takes longer than estimated?”

That’s normal! Stories are estimates. If implementation reveals more complexity:

  1. Continue working until DoD is met
  2. Consider if story should be split
  3. Document learnings in retrospective
  4. Adjust future estimates based on this learning

After completing all stories in an epic (when epic is done). Retrospectives capture:

  • What went well
  • What could improve
  • Technical insights
  • Learnings for future epics

Don’t wait until project end — run after each epic for continuous improvement.

Have a question not answered here? Please open an issue or ask in Discord so we can add it!