bmad-create-story

Create implementation-ready story files from epics, PRD, architecture, UX, and sprint metadata.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-create-story-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-create-story
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-create-story-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a complete, implementation-ready story file for a development agent, reducing ambiguity, missing context, and avoidable implementation mistakes.

Core Features & Use Cases

  • Story creation: Generates a structured story document from epics, PRD, architecture, UX, and sprint context.
  • Context synthesis: Pulls together technical constraints, prior-story learnings, and file-structure guidance so the developer can implement correctly the first time.
  • Quality validation: Reviews the generated story for gaps, regressions, vague guidance, and other risks that could derail implementation.
  • Use case: When you need the next backlog story turned into a precise, dev-ready work item with strong guardrails and testing guidance.

Quick Start

Ask the skill to create the next story from the current sprint and source documents.

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 development-ready stories from epics and PRDs?

Development-ready story creation synthesizes epics, architecture, PRD, UX, and sprint metadata into a structured story file. This process extracts technical constraints and prior-story learnings to provide comprehensive implementation guidance and reduce ambiguity.

What is story context synthesis for sprint planning?

Story context synthesis for sprint planning pulls together cross-document requirements, file-structure guidance, and technical constraints. It provides exhaustive artifact analysis and prior-story intelligence so developers can implement correctly the first time.

How do I validate story readiness for development sprints?

Validating story readiness for development sprints involves reviewing generated story context for gaps, regressions, vague guidance, and duplicate risks. This quality validation applies guardrails against ambiguous or regression-prone implementation before development begins.

Can I generate implementation guides from existing backlog story metadata?

Yes, generating implementation guides from backlog story metadata is possible by applying exhaustive artifact analysis. The system uses your sprint metadata, architecture, and PRD to produce precise, dev-ready work items with testing guidance.

What is the best way to prevent regressions when preparing backlog stories?

The best way to prevent regressions during backlog story preparation is applying quality validation guardrails. This involves analyzing prior-story intelligence and cross-document requirements to identify and block regression-prone implementation paths.