bmad-create-story

Generates a complete dev-story document from an epic/story input.

Updated May 5, 2026
One-click install
npx skills add https://github.com/b566776/whitebox --skill bmad-create-story-b566776
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/b566776/whitebox/tree/main/.gemini/skills/bmad-create-story
Command: npx skills add https://github.com/b566776/whitebox --skill bmad-create-story-b566776

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generates a comprehensive, production-ready story document that provides the dev agent with guardrails, context, and references needed to implement a feature end-to-end.

Core Features & Use Cases

  • Generates a ready-to-run story skeleton from an epic/story input, including goals, acceptance criteria, and tasks.
  • Embeds developer guardrails, prior story learnings, architecture considerations, testing guidance, and references for rapid implementation.
  • Enables a repeatable workflow for sprint planning and consistent story documentation across projects.

Quick Start

Provide the epic and story identifier (for example, "1-2-user-auth") to generate a ready-for-dev story document that can be opened in your IDE.

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 a developer story document from an epic for sprint planning?

To generate a developer story document from an epic, provide your epic and story identifier to produce a ready-for-dev narrative that includes goals, acceptance criteria, and structured tasks.

What is a ready-for-dev story and how does it guide feature implementation?

A ready-for-dev story is a comprehensive document that provides development guardrails, architecture context, and testing references to guide agents through flawless end-to-end feature implementation.

How do I include architecture constraints and prior learnings in my dev stories?

You include architecture constraints and prior learnings by applying embedded guardrails and references during story generation, ensuring prior story knowledge integrates directly into the new narrative.

Can I use automated story generation for consistent documentation across sprint teams?

Automated story generation enables a repeatable workflow for sprint planning, ensuring consistent story documentation and reusable developer guidance across multiple projects and teams.

Do I need a specific epic identifier format to create a story skeleton?

You need an epic and story identifier, such as a structured string like "1-2-user-auth", to automatically generate a ready-to-run story skeleton that opens directly in your IDE.

What's the best way to standardize acceptance criteria and testing guidance in development stories?

Standardize acceptance criteria and testing guidance by applying a structured template during story generation, embedding developer guardrails and references to ensure consistent implementation.