bmad-create-story

Create implementation story files from epics, PRD, architecture, and UX context.

Updated May 23, 2026
One-click install
npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-create-story-diegosanchespereira1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-create-story
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-create-story-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns messy product and architecture context into a complete, implementation-ready story file so developers can start with clear requirements, guardrails, and testing guidance instead of guessing.

Core Features & Use Cases

  • Story Discovery and Selection: Finds the next backlog story or accepts a specific epic-story key to target.
  • Context Aggregation: Loads epics, PRD, architecture, UX, prior stories, and project facts to build a full implementation brief.
  • Developer Handoff: Produces a structured story document with acceptance criteria, dev notes, references, and status updates for the implementation workflow.

Quick Start

Ask this Skill to create the next backlog story from the project context or to generate a story for a specific epic-story key.

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 developer stories from epics and architecture context?

Implementation-ready developer stories are created by aggregating epics, PRD, architecture, and prior-story context into a structured document with acceptance criteria, dev notes, and testing guidance. This eliminates guessing by providing clear requirements and guardrails.

What is the process for discovering the next backlog story in a software project?

Backlog-story discovery involves analyzing existing project context, including epics and prior stories, to identify and select the next logical story for implementation. The process applies workflow customization resolution and sprint-status updates to maintain momentum.

Can I generate a story file for a specific epic-story key instead of auto-discovering the next backlog item?

Yes, you can target a specific epic-story key to generate a story file. The system accepts the key, loads the relevant PRD, architecture, and UX context, and produces the comprehensive implementation brief for that targeted story.

What project artifacts do I need before generating a story from architecture and PRD context?

Generating a story requires existing project artifacts including epics, a Product Requirements Document (PRD), architecture documents, and UX context. Prior-story analysis and project facts are also loaded to build a complete implementation brief with architecture guardrails.

How does prior-story analysis improve the generation of developer context for sprints?

Prior-story analysis improves developer context generation by extracting historical implementation patterns and completed requirements from previous stories. This ensures new stories maintain continuity, respect architecture guardrails, and accurately update sprint-status.