bmad-create-story

Create implementation-ready story files from PRD, architecture, and UX artifacts.

36|16|Updated May 1, 2026
One-click install
npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-create-story-tronghieu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/tronghieu/lumina-wiki/tree/main/.agents/skills/bmad-create-story
Command: npx skills add https://github.com/tronghieu/lumina-wiki --skill bmad-create-story-tronghieu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It creates a comprehensive, implementation-ready story file by exhaustively analyzing epics, PRD, architecture, and UX artifacts, so developers don’t miss critical constraints or implement the wrong approach.

Core Features & Use Cases

  • Creates a dedicated story implementation blueprint: Produces a fully structured story document that tells a dev agent exactly what to build, how to comply with architecture, and what to preserve.
  • Loads sprint and story selection context: Automatically discovers the next backlog story from sprint-status.yaml (or uses a user-provided epic-story identifier/path).
  • Provides guardrails to prevent common LLM-dev failures: Enforces anti-mistake guidance (no reinvention, correct file locations, regression preservation, UX compliance) and includes prior-story intelligence when applicable.

Quick Start

Tell the agent: create story 1-2-user-authentication using the current workspace context.

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 developer stories from epic and PRD context?

To generate implementation-ready developer stories, this skill resolves the target epic and backlog story, loads PRD and architecture context, and applies workflow guardrails to produce an exhaustive developer instruction document. It ensures devs receive exact build constraints and compliance rules.

How do I automate sprint planning and select the next backlog story for development?

Automate sprint planning by using this skill to discover the next backlog story from sprint-status.yaml or a user-provided epic-story identifier. It analyzes the story against architecture and UX artifacts, then updates the sprint status to ready-for-dev upon checklist validation.

What are the best ways to prevent LLM developer agents from making architecture and UX compliance mistakes?

Preventing LLM developer mistakes requires applying workflow-driven guardrails during story generation. This skill enforces anti-mistake guidance including no reinvention, correct file locations, regression preservation, and UX compliance, while injecting prior-story intelligence to maintain continuity.

Does story generation work with BDD acceptance criteria and existing UX artifacts?

Story generation works with BDD acceptance criteria and UX artifacts by selectively loading these documents during context synthesis. The skill integrates behavioral acceptance criteria into the story blueprint, ensuring the developer agent validates functional compliance against UX specifications.

How to create a story implementation blueprint that enforces developer guardrails and architecture compliance?

Create a story implementation blueprint by triggering template-based story generation after workflow customization resolution. The skill executes activation steps, loads selective artifacts, and validates against checklists, outputting a dedicated file enforcing architecture compliance and developer guardrails.

Why does my dev agent implement the wrong approach when building sprint stories?

Dev agents implement wrong approaches when they lack exhaustive context synthesis from PRD, architecture, and prior stories. This skill solves that by resolving workflow customizations and generating an instruction document with strict guardrails preventing architectural deviations and missed constraints.