bmad-create-story

Generates comprehensive developer-ready story files from epics, architecture, and sprint status.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-create-story-asygnuz-s-a-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/Asygnuz-S-A-S/one-star/tree/main/.claude/skills/bmad-create-story
Command: npx skills add https://github.com/Asygnuz-S-A-S/one-star --skill bmad-create-story-asygnuz-s-a-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development agents often fail because stories lack context, causing wrong libraries, broken regressions, and vague implementations. This Skill creates a complete story file that gives the dev agent everything needed for correct implementation. ## Core Features & Use Cases - Automatic Story Discovery: Reads sprint-status.yaml to find the next backlog story, or accepts an explicit epic-story identifier like "1-2-user-auth". - Exhaustive Context Gathering: Analyzes epics, PRD, architecture, UX documents, previous story learnings, and git history to build developer guardrails. - Quality Validation: Validates the generated story against a checklist that detects missing requirements, regression risks, and LLM optimization issues before marking it ready-for-dev. - Use Case: A team following the BMad method asks to "create the next story"; the Skill locates the next backlog item, assembles architecture constraints and prior learnings, writes the story file, and updates sprint status to ready-for-dev. ## Quick Start Ask the agent to create the next story from the sprint backlog, or specify a story such as "create story 2-4" to generate a fully contexted implementation file.

Frequently Asked Questions about bmad-create-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create the next story from my sprint backlog?▼

Run the create-story workflow with no arguments. It reads sprint-status.yaml, finds the first story with backlog status, gathers context from epics and architecture, and writes a ready-for-dev story file.

How do I create a specific story by epic and story number?▼

Provide the identifier directly, such as "create story 2-4" or "1-2-user-auth". The workflow parses the epic number, story number, and title, then skips auto-discovery and generates the story file for that item.

What documents does the create-story workflow need?▼

It uses sprint-status.yaml for tracking, plus epics, PRD, architecture, and UX files from your planning artifacts directory. Missing documents are tolerated, but epics content is the primary source for story requirements.

Can I customize the create-story workflow behavior?▼

Yes. Edit customize.toml or place team and user override TOML files under _bmad/custom. You can add activation steps, persistent facts such as project-context.md files, and an on_complete action.

What happens if no backlog stories exist in sprint status?▼

The workflow halts and reports that no backlog stories were found. It suggests running sprint-planning to refresh tracking, adding stories via correct-course, or running a retrospective if the sprint is complete.