bmad-create-story

Generate a dev-ready story file from project context and planning artifacts.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/AhmedKaram50/research --skill bmad-create-story-ahmedkaram50
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/AhmedKaram50/research/tree/main/shopify-builder/_bmad/bmm/workflows/4-implementation/bmad-create-story
Command: npx skills add https://github.com/AhmedKaram50/research --skill bmad-create-story-ahmedkaram50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the time and cognitive load required to craft a comprehensive dev story by automatically generating a ready-to-use document that embeds context, guardrails, and references for flawless implementation.

Core Features & Use Cases

  • Automated story generation: Produces a complete story file from planning artifacts and previous work to ensure consistency.
  • Developer guardrails: Includes explicit technical requirements, architecture constraints, and testing guidance to prevent misimplementation.
  • References and context integration: Pulls in epics, architecture details, git history, and project context to provide end-to-end coverage.

Quick Start

Provide a target epic/story and I will generate a complete, ready-to-use story file populated with context and implementation guidance.

Frequently Asked Questions about bmad-create-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I auto-generate developer stories with full architecture context and guardrails?

Auto-generating developer stories requires providing target epics and planning artifacts to produce a comprehensive story file populated with architecture references, developer context, and technical guardrails for implementation.

What is a dev-ready story file and what context should it include?

A dev-ready story file is a single document embedding end-to-end developer guidance. It includes explicit developer_context, architecture references, technical guardrails, and testing guidance to prevent misimplementation during development.

How do I create a comprehensive development story from project planning artifacts and git history?

Creating a comprehensive development story involves pulling epics, architecture details, and project context from existing planning artifacts. This integrates git history and previous work to ensure consistency and end-to-end coverage.

Can I use automated story generation for projects requiring strict architecture constraints and testing guidance?

Automated story generation fits projects needing strict architecture constraints. It embeds explicit technical requirements, architecture constraints, and testing guidance directly into the story file to ensure flawless implementation.

What's the best way to reduce cognitive load when crafting developer stories with epics and architecture references?

The best way to reduce cognitive load is automating story creation from project context. This generates a complete document embedding references, guardrails, and context, replacing manual crafting of comprehensive developer guides.