bmad-create-story

Generate detailed software development stories from project artifacts.

Updated Apr 25, 2026

Search Tags:#software development #contextualization #developer guidance #story generation #task documentation

Ready to run

npx skills add https://github.com/wahabmalik/whatsapp-chatbot --skill bmad-create-story-wahabmalik

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-create-story
Source: https://github.com/wahabmalik/whatsapp-chatbot/tree/main/.github/skills/bmad-create-story
Command: npx skills add https://github.com/wahabmalik/whatsapp-chatbot --skill bmad-create-story-wahabmalik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill generates a comprehensive story file that provides developers with all necessary context for implementing a software feature, ensuring accurate and efficient development processes.

Core Features & Use Cases

Comprehensive Story Generation: Creates a self-contained story file with all the context a developer needs to understand and implement a software feature.
Story Context Analysis: Analyzes epics, architecture, UX, and PRD files to ensure all necessary information is included in the story.
Story Optimization: Optimizes the story for readability and ease of understanding by the developer, using principles of clear and concise communication.

Quick Start

Run the 'bmad-create-story' command to generate a story for a feature in your project.

Frequently Asked Questions about bmad-create-story

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

FAQPage Schema

How do I generate detailed developer context for software development tasks?▼

Generating detailed developer context for software development tasks requires analyzing project artifacts like epics, architecture, and PRDs to create a comprehensive story file. This ensures developers have all necessary context for accurate feature implementation.

What is the best way to create task documentation from project artifacts?▼

Creating task documentation from project artifacts involves analyzing epics, architecture, and UX files to produce a self-contained story file. This approach optimizes readability and provides developers with thorough guidance for software feature implementation.

How does story context analysis work for software feature implementation?▼

Story context analysis works by examining PRD, architecture, and UX files to extract necessary information for software feature implementation. It compiles this data into an optimized, self-contained story file that guides developers through the task.

Can I build a development story without manually writing task documentation?▼

You can build a development story without manually writing task documentation by running a generation command that analyzes existing project artifacts. This process automatically compiles epics and PRDs into a self-contained story file for developer guidance.

Do I need PRD and architecture files to use a story generation process?▼

Yes, you need PRD and architecture files to use a story generation process. The generation mechanism requires access to existing project documentation such as epics, architecture, and UX files to ensure all necessary context is included in the developer story.

What limitations exist when creating story context from project artifacts?▼

A key limitation when creating story context from project artifacts is the strict dependency on pre-existing documentation like PRDs and architecture files. Without these foundational project artifacts, the story generation process cannot compile comprehensive developer guidance.