bmad-dev-story

Automate story implementation from specification files with red-green-refactor cycles.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher --skill bmad-dev-story-jingyiwng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher/tree/main/_bmad/bmm/workflows/4-implementation/bmad-dev-story
Command: npx skills add https://github.com/JingyiWng/databricks_ai_dev_kit_price_watcher --skill bmad-dev-story-jingyiwng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often spend excessive time manually locating, loading, and executing story specifications, updating sprint status, and ensuring each task meets the definition of done. This Skill automates the entire story implementation workflow, reducing manual effort and human error.

Core Features & Use Cases

  • Automated Story Discovery: Finds the next ready‑for‑dev story from sprint‑status or directly from the repository.
  • Context‑Driven Execution: Loads story Dev Notes, runs a step‑by‑step red‑green‑refactor cycle, creates tests, and performs validations.
  • Sprint Status Integration: Updates sprint‑status.yaml and story status automatically, ensuring traceability.
  • Definition‑of‑Done Validation: Executes an enhanced checklist to certify completeness before marking the story ready for review.

Quick Start

Ask the skill to develop the next story by saying, “dev this story.”

Frequently Asked Questions about bmad-dev-story

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

FAQPage Schema
How do I automate sprint story implementation from a spec file?

Automate sprint story implementation by loading a context-filled specification file to automatically locate, execute, and validate story tasks without manual intervention. It runs red-green-refactor cycles, creates tests, and updates sprint status automatically.

What is definition-of-done validation in automated story development?

Definition-of-done validation in automated story development executes an enhanced checklist to certify completeness before marking the story ready for review. It ensures all tests, validations, and status checkpoints are met automatically.

How do I run red-green-refactor cycles automatically during sprint execution?

Run red-green-refactor cycles automatically by triggering context-driven execution from a story specification file. The workflow loads Dev Notes, creates tests, and performs step-by-step validation cycles without manual intervention.

Does automated story development update sprint-status.yaml automatically?

Automated story development updates sprint-status.yaml and story status automatically, ensuring traceability throughout the sprint execution workflow. It locates the next ready-for-dev story and maintains status synchronization.

Can I use automated story implementation without manually locating the next story?

Automated story implementation finds the next ready-for-dev story automatically from sprint-status or directly from the repository. You simply trigger the workflow and it discovers, loads, and executes the story tasks.

When should I not use automated story implementation for sprint execution?

Avoid automated story implementation when story specifications lack sufficient context or Dev Notes, as the workflow depends on context-driven execution. Manual intervention is also needed if definition-of-done criteria require subjective review.