bmad-create-story

Creates implementation-ready story files from sprint status and planning artifacts.

Updated May 17, 2026
One-click install
npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-create-story-thuantan2060
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/thuantan2060/facebook-sale-tracking/tree/main/.agents/skills/bmad-create-story
Command: npx skills add https://github.com/thuantan2060/facebook-sale-tracking --skill bmad-create-story-thuantan2060

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3.

What problem does it solve?

bmad-create-story turns an epic/story request into a comprehensive, implementation-ready story file, preventing omissions and “LLM dev” mistakes by front-loading exhaustive project, architecture, UX, and prior-work context.

Core Features & Use Cases

  • Story context compilation: Builds a dedicated story document that includes epic-derived requirements, architecture guardrails, UX context, and project facts.
  • Sprint-aware story targeting: Auto-discovers the next backlog story from sprint-status.yaml (or uses a user-provided epic-story identifier/path).
  • Developer guardrail packaging: Produces a ready-for-dev story that instructs the dev agent what to preserve, what to change, what to read, and how to validate completion.

Quick Start

Ask your agent to run bmad-create-story with the identifier 1-2-your-story-slug to create the next ready-for-dev story 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 generate implementation-ready story context for sprint planning?

Implementation-ready story context is generated by resolving the target epic or story from sprint status and compiling exhaustive requirements, architecture constraints, and prior-work intelligence into a deterministic dev execution file.

What is the best way to compile architecture guardrails and dev requirements into a story file?

Compiling architecture guardrails and dev requirements involves stepwise extraction from planning artifacts to instruct the dev agent what to preserve, what to change, what to read, and how to validate completion within the story file.

How does sprint-aware story generation auto-discover the next backlog item?

Sprint-aware story generation auto-discovers the next backlog story by reading the sprint-status.yaml file, or alternatively accepts a user-provided epic-story identifier or path to target a specific story.

Do I need Python to run BMad methodology story generation?

Yes, Python3 is required as a dependency to run BMad methodology story generation, which applies workflow customization resolution and selective artifact loading to create ready-for-dev stories.

Can I use a custom epic-story identifier instead of auto-discovery for story generation?

Yes, you can provide a custom epic-story identifier or path, which bypasses auto-discovery from the sprint-status.yaml file and directly targets the specified story for context compilation.

Why does story context compilation include prior story and git-informed review?

Optional prior story and git-informed review is included during story context compilation to capture prior-work intelligence, preventing omissions and LLM development mistakes by front-loading exhaustive project history.