bmad-create-story

It automatically generates a ready-to-use dev-story file by consolidating planning artifacts, architecture notes, and workflow guidance. This unified document captures all required context, ensuring developers have everything needed for implementation.

A unified dev-story file encapsulates all context a developer needs to implement a requested story, including epic context and guardrails. You need it when converting epic requests into actionable stories to prevent misinterpretation and duplication.

During story creation, the Skill automatically incorporates previous story learnings and applies guardrails. It uses available git intelligence and project context to inform implementation decisions and prevent misinterpretation.

Yes, automated story generation integrates existing architecture notes and project context directly into the dev-story. It aligns the output with sprint status and includes testing and deployment guidelines.

The best way to convert epic requests is using an automated workflow that extracts epic context and planning artifacts. This generates a production-ready story file aligned with sprint status, ensuring complete implementation guidance.

Yes, you can generate testing and deployment guidelines within the dev-story file. The Skill ensures these guidelines are included alongside acceptance criteria to guide developers through implementation and release.