bmad-dev-story

Execute story implementation workflows with test-first validation and status updates.

Updated May 23, 2026

Search Tags:#code review #workflow automation #test-driven development #sprint planning #task tracking #story implementation

Ready to run

npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-dev-story-diegosanchespereira1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/diegosanchespereira1/lavarapido/tree/main/lava-rapido/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/diegosanchespereira1/lavarapido --skill bmad-dev-story-diegosanchespereira1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a context-filled development story into a complete implementation workflow, reducing guesswork, missed steps, and incomplete handoffs during software delivery.

Core Features & Use Cases

Story-driven implementation: Follows the story file step by step, from loading context to completing tasks and updating status.
Test-first execution: Adds and runs tests before implementation, then validates against acceptance criteria and project quality gates.
Review continuation support: Resumes work after code review by resolving follow-up items and updating the story record accordingly.

Quick Start

Use the bmad-dev-story skill to implement the next ready story from the sprint plan and update the story file as you complete the workflow.

Frequently Asked Questions about bmad-dev-story

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

FAQPage Schema

How do I implement development stories from a sprint plan into shippable code?▼

Story implementation workflows process context-filled development story files into shippable code by enforcing strict task sequencing, test-first validation, and updating sprint status tracking upon task completion.

What is test-driven development validation for story implementation?▼

Test-first execution requires adding and running tests before implementation, then validating code against acceptance criteria and project quality gates to ensure the story meets its definition of done.

How do I resume code review follow-ups after a sprint pause?▼

Review continuation support resumes work after code review by resolving follow-up items and updating the story file record accordingly, ensuring incomplete review actions are tracked and finalized within the sprint workflow.

Can I update sprint status tracking directly within my development story files?▼

Yes, story-driven implementation updates sprint status tracking by editing approved sections of the story file, completing definition-of-done criteria and sprint-status updates as workflow tasks are finalized.

What are the limitations of automated story implementation workflows?▼

Story implementation workflows require context-filled development story files and restrict edits to approved sections only, meaning incomplete story context or undefined acceptance criteria will prevent proper task sequencing and validation.