bmad-create-story

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

1|Updated Aug 3, 2025

Search Tags:#automation #workflow #architecture #epics #guardrails #story-creation #dev-agent

Ready to run

npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-create-story-mazenmrad

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/MazenMrad/Obsidio/tree/main/.cursor/skills/bmad-create-story
Command: npx skills add https://github.com/MazenMrad/Obsidio --skill bmad-create-story-mazenmrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automatically generates a complete, ready-to-use dev-story document that captures all the context a developer needs to implement a requested epic or story.

Core Features & Use Cases

Automated generation of a unified story file from planning artifacts, architecture notes, workflows, and project context.
Inclusion of previous story learnings and, where available, git intelligence to inform implementation decisions.
Guardrails, acceptance criteria, and deployment/testing guidance to prevent misinterpretation and duplication.

Quick Start

Provide the epic and story identifier, and the tool will generate a ready-for-dev story file containing all required context.

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 a dev-story from an epic with all necessary context?▼

It automatically generates a ready-to-use dev-story file by consolidating planning artifacts, architecture notes, and workflow guidance. This unified document captures all required context, ensuring developers have everything needed for implementation.

What is a unified dev-story file and when do I need it?▼

A unified dev-story file encapsulates all context a developer needs to implement a requested story, including epic context and guardrails. You need it when converting epic requests into actionable stories to prevent misinterpretation and duplication.

How do I include previous story learnings and guardrails in story creation?▼

During story creation, the Skill automatically incorporates previous story learnings and applies guardrails. It uses available git intelligence and project context to inform implementation decisions and prevent misinterpretation.

Does automated story generation work with existing architecture notes and project context?▼

Yes, automated story generation integrates existing architecture notes and project context directly into the dev-story. It aligns the output with sprint status and includes testing and deployment guidelines.

What is the best way to convert epic requests into actionable developer stories?▼

The best way to convert epic requests is using an automated workflow that extracts epic context and planning artifacts. This generates a production-ready story file aligned with sprint status, ensuring complete implementation guidance.

Can I generate testing and deployment guidelines within a dev-story file?▼

Yes, you can generate testing and deployment guidelines within the dev-story file. The Skill ensures these guidelines are included alongside acceptance criteria to guide developers through implementation and release.