bmad-create-story

Generate a ready-for-dev story file from an epic-story identifier.

Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-create-story-cbanzaime23
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/Cbanzaime23/Booking-System/tree/main/.agent/skills/bmad-create-story
Command: npx skills add https://github.com/Cbanzaime23/Booking-System --skill bmad-create-story-cbanzaime23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a comprehensive, ready-to-use story file that contains all context the development agent needs to implement a new story, ensuring consistent structure, guardrails, and references.

Core Features & Use Cases

  • Automatically extracts epic, architecture, and previous story intelligence to seed a new story file.
  • Provides a detailed developer guide including requirements, constraints, and testing notes.
  • Updates sprint tracking and outputs a ready-for-dev story document for immediate handoff to dev-story agents.

Quick Start

Provide an epic-story identifier (for example 1-2-user-auth) to generate a complete 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 create a developer story file with full epic and architecture context?▼

To create a developer story file, you provide an epic-story identifier to automatically extract epic details, architecture constraints, and prior learnings, generating a ready-for-dev document with all required context.

How do I generate story files automatically from an epic identifier?▼

Generating story files automatically requires providing an epic-story identifier like 1-2-user-auth, which triggers automated workflow resolution to extract artifacts and apply guardrails for immediate story creation.

Can I reuse previous story intelligence and learnings for new story generation?▼

Yes, story generation automatically extracts previous story intelligence and prior learnings to seed a new story file, ensuring past development context is reused for consistent implementation across the epic.

Does automated story generation include architecture constraints and guardrails?▼

Automated story generation applies architecture constraints and guardrail-driven rules to the output file, ensuring the generated developer guide respects existing system design and project standards.

What is the best way to prepare a ready-for-dev story document for handoff?▼

The best way to prepare a ready-for-dev story document is using automated workflow resolution to aggregate epic details, architecture constraints, and testing notes into a single file for immediate handoff to dev-story agents.

When do I need a comprehensive story file for dev automation workflows?▼

You need a comprehensive story file when requesting new stories in a dev automation workflow, as it provides the complete developer guide and sprint tracking updates required for autonomous implementation.