bmad-dev-story

Name: bmad-dev-story
Availability: InStock
Author: GenEd

Execute story-driven development tasks from a structured story specification file.

Updated Mar 30, 2026

Search Tags:#code review #developer productivity #status tracking #test validation #story implementation #sprint workflow

Ready to run

npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-dev-story-geneducation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/bmad-dev-story
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill bmad-dev-story-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers execute a structured story from start to finish without losing track of requirements, review feedback, tests, or sprint status.

Core Features & Use Cases

Story-Driven Implementation: Works from a complete story file and follows its tasks and acceptance criteria in order.
Review Follow-Up Handling: Detects code review continuations, resolves flagged items, and updates the story record accordingly.
Validation and Tracking: Keeps file lists, change logs, test results, and status updates aligned with the implementation.
Use Case: A developer asks for the next ready story to be implemented, and this Skill coordinates the workflow through completion and review readiness.

Quick Start

Ask the skill to implement the next ready story from the sprint plan and follow the workflow exactly.

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 a story from a structured specification file without losing track of tasks?▼

Story-driven implementation executes tasks and acceptance criteria from a structured story specification file in strict sequence, tracking file lists, change logs, and status updates to ensure no sprint requirements are lost during development.

How does story implementation handle code review follow-ups and flagged items?▼

Story implementation detects code review continuations by loading previous context, resolving flagged items, and updating the story record accordingly so review feedback is systematically addressed and tracked through to completion.

What is the best way to enforce test validation and status tracking during sprint execution?▼

Enforcing test validation during sprint execution requires strict workflow sequencing with validation gates that check test results, update file tracking, and verify review-state updates before marking a story ready for review.

Can I use this story workflow for both ready-for-dev and in-progress sprint tasks?▼

Yes, the story workflow applies to both ready-for-dev and in-progress work, coordinating status tracking and context loading across all sprint execution stages while maintaining strict workflow control throughout the implementation lifecycle.

Does story-driven development require a complete story file before starting implementation?▼

Yes, story-driven development works from a complete story specification file containing tasks and acceptance criteria, ensuring the implementation follows structured requirements rather than ad-hoc development without clear sprint tracking.

What happens if validation gates fail during story implementation?▼

Validation gates block the story from being marked ready for review if test validation or workflow sequencing requirements are not met, preventing incomplete implementations from advancing in the sprint workflow.