skills.rest
devalexanderdaza
devalexanderdazaCOMMUNITY
Explore all skills by this author →
Website𝕏@devalexanderdazGitHub

bmad-create-story

Generate implementation-ready BMAD story files from epics, PRD, architecture, and UX artifacts.

Updated May 5, 2026
Search Tags:#story-creation#agile-development#sprint-tracking#bmad#artifact-analysis#implementation-guide#dev-context
One-click install
npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-create-story-devalexanderdaza
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/devalexanderdaza/bmad-any/tree/main/.agents/skills/bmad-create-story
Command: npx skills add https://github.com/devalexanderdaza/bmad-any --skill bmad-create-story-devalexanderdaza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of incomplete, vague story files that lead to developer mistakes, rework, broken regressions, and failed implementations in agile BMAD development workflows. It automates the creation of comprehensive, context-rich story files so development agents have all required information to implement features correctly on the first attempt.

Core Features & Use Cases

  • Exhaustive Artifact Analysis: Automatically extracts critical context from epics, PRD, architecture, UX, and previous story files to prevent missed requirements and reinvention of existing solutions.
  • Sprint Tracking Integration: Auto-discovers backlog stories from BMAD sprint status files, updates story status, and aligns with existing agile workflows.
  • Developer Guardrails: Includes architectural constraints, technical specifications, previous work learnings, and latest technical research to eliminate implementation errors.
  • Use Case: For a software team using BMAD, run this skill when you need to create an implementation-ready story file for a new backlog item, so the dev agent has all context, acceptance criteria, and guardrails to build the feature correctly without rework or bugs.

Quick Start

Use the bmad-create-story skill to generate a comprehensive implementation-ready story file for the next backlog item in your current BMAD sprint.

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 implementation-ready story files for agile development?▼

To create implementation-ready story files for agile development, you need to extract comprehensive context from epics, product requirements, architecture, and UX design artifacts. This ensures development agents receive technical specifications and acceptance criteria to build features correctly without rework.

What causes incomplete agile story files and developer implementation errors?▼

Incomplete agile story files and developer implementation errors are caused by missing architectural constraints, vague technical specifications, and overlooked previous story learnings. Generating exhaustive artifact analysis prevents missed requirements and the reinvention of existing solutions during sprint tracking.

How do I generate developer context from epics and product requirements?▼

You generate developer context from epics and product requirements through exhaustive artifact analysis, automatically extracting critical information to prevent missed requirements. This process compiles architectural guardrails, technical research, and acceptance criteria into a single implementation guide.

Does this story creation process work with BMAD sprint tracking?▼

Yes, this story creation process works directly with BMAD sprint tracking by auto-discovering backlog stories from BMAD sprint status files. It automatically updates story status and aligns the generated implementation context with your existing agile workflows.

Can I use architectural guardrails and previous learnings to prevent implementation mistakes?▼

Yes, you can use architectural guardrails and previous story learnings to prevent implementation mistakes by including them directly in the story context file. Incorporating technical constraints and prior work learnings eliminates common errors and failed regressions in agile development.

What is the best way to eliminate rework from broken story implementations in sprints?▼

The best way to eliminate rework from broken story implementations in sprints is to generate comprehensive, context-rich story files before development begins. Providing dev-ready implementation guides with technical specifications and acceptance criteria ensures features are built correctly on the first attempt.

Related Skills

Explore More Software Engineering Skills→
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate
ldk-hubldk-hub

bmad-dev-story

Executes story implementations from spec files across sprint workflows with built-in validation.

Community
Advanced
hongmaple0820hongmaple0820
9

agile-product-owner

Convert requirements into INVEST-aligned user stories and backlog items.

Community
Advanced
anderson-0anderson-0
4

create-story

Generate implementation stories with acceptance criteria from project requirements and technical context.

Community
Advanced