bmad-create-story

Name: bmad-create-story
Availability: InStock
Author: GenEd

Generate implementation-ready story files with acceptance criteria, tasks, and dev notes.

Updated Mar 30, 2026

Search Tags:#validation #sprint planning #architecture analysis #story generation #bmad #developer context

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-create-story-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-create-story
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-create-story-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a backlog epic and story into a complete, implementation-ready story file so developers do not have to reconstruct context from scattered project documents.

Core Features & Use Cases

Story creation: Generates a full story document with acceptance criteria, tasks, dev notes, references, and completion tracking.
Context synthesis: Pulls together epics, architecture, PRD, UX, sprint status, and prior-story learnings into one coherent implementation guide.
Quality guardrails: Adds validation and anti-mistake context to reduce wrong file placement, duplicate work, vague implementation, and regression risk.

Quick Start

Ask this Skill to create the next backlog story for the selected epic, and it will produce a complete ready-for-dev story file with the right context and guardrails.

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 an implementation-ready story file for sprint planning?▼

To generate an implementation-ready story file, you need to provide epics, architecture, PRD, UX, sprint-status, and prior-story inputs. The system synthesizes these documents into a single coherent developer context guide with acceptance criteria, tasks, and dev notes.

What is a ready-for-dev story document and what context does it include?▼

A ready-for-dev story document provides comprehensive developer context for a backlog item. It includes synthesized information from epics, architecture, and PRD, along with acceptance criteria, tasks, dev notes, references, and sprint status updates.

How do I create developer context that prevents wrong file placement and duplicate work?▼

You can prevent wrong file placement and duplicate work by generating a story file with built-in quality guardrails. These guardrails add validation and anti-mistake context to the developer notes, reducing regression risk and vague implementation.

What inputs are required to synthesize project documents into a story generation workflow?▼

Story generation requires epics, architecture, PRD, UX, sprint-status, and prior-story inputs. Pulling these sources together ensures the resulting implementation guide has comprehensive context and accurate completion tracking.

Can I validate create-story workflows against existing architecture and PRD documents?▼

Yes, you can validate create-story workflows by applying the system to a backlog item that needs comprehensive developer context. It cross-references your architecture and PRD inputs to produce a document with validation and anti-mistake guardrails.

Does story generation work for updating sprint status alongside writing developer context?▼

Yes, story generation works for updating sprint status by including it as a required input. The resulting ready-for-dev document automatically contains sprint status updates alongside the tasks, dev notes, and references.