bmad-ralph-generate

Automates BMAD story preparation workflow steps 1-5 including validation, ATDD generation, review and context compilation.

1|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/sidart10/orion-slackbot --skill bmad-ralph-generate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-ralph-generate
Source: https://github.com/sidart10/orion-slackbot/tree/main/.claude/skills/bmad-ralph-generate
Command: npx skills add https://github.com/sidart10/orion-slackbot --skill bmad-ralph-generate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ruamel.yaml, filelock, pytest, pytest-cov, and includes scripts (resource) and prompts (resource) components.

What problem does it solve?

This Skill automates the multi-step process of preparing user stories for development, ensuring consistency and reducing manual effort in the BMAD workflow.

Core Features & Use Cases

  • Automated Story Generation: Creates stories from epics, validating them against defined criteria.
  • End-to-End Workflow: Executes Steps 1-5 of the BMAD workflow, including ATDD generation if enabled.
  • Context Preservation: Spawns fresh agents for each step to prevent context degradation.
  • Use Case: When you have completed your BMAD planning (PRD, epics, etc.), use this skill to automatically generate and prepare all stories for the current sprint, ensuring they are 'ready-for-dev'.

Quick Start

Use the bmad-ralph-generate skill to prepare stories for epic 1.

Frequently Asked Questions about bmad-ralph-generate

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

FAQPage Schema
How do I automate agile story creation and preparation for development?

Automated story creation executes the BMAD workflow steps 1-5, handling story generation, validation, ATDD generation, and context compilation. It requires planning artifacts like prd.md, epics.md, and sprint-status.yaml as input to prepare ready-for-dev stories.

What planning artifacts do I need before generating sprint stories?

Generating sprint stories requires prd.md, epics.md, and sprint-status.yaml files as input. These planning artifacts provide the necessary product requirements, epic definitions, and sprint status configurations for the automated story preparation workflow.

How does automated ATDD generation work within agile story preparation?

Automated ATDD generation occurs during step 4 of the story preparation workflow, creating acceptance test driven development criteria after story validation. It spawns fresh agents via the Task tool to execute autonomously, preventing context degradation across steps.

Can I use this workflow to validate stories against defined criteria automatically?

Story validation against defined criteria happens automatically during step 2 of the BMAD workflow. The process selects epics and stories from your sprint-status.yaml configuration, validating generated stories before proceeding to ATDD generation and context compilation.

What's the best way to prevent context degradation during multi-step story generation?

Preventing context degradation during multi-step story generation is handled by spawning fresh agents for each workflow step. This autonomous execution approach via the Task tool ensures each step from story creation to context compilation maintains clean context.

Does the BMAD story preparation workflow support autonomous execution without manual intervention?

BMAD story preparation supports autonomous execution by spawning agents via the Task tool for each of the 5 steps. After configuring sprint-status.yaml and providing planning artifacts, the workflow runs automatically from story generation through context compilation.