bmad-dev-story

Implement development stories from specifications and drive them to review-ready status.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-dev-story-ncptuan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/ncptuan/stock_backtest_project/tree/main/.claude/skills/bmad-dev-story
Command: npx skills add https://github.com/ncptuan/stock_backtest_project --skill bmad-dev-story-ncptuan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement a development story from a prepared story spec without skipping requirements, tests, or status updates. It is designed for situations where a sprint or story file already contains detailed context and you want disciplined execution from implementation through review readiness.

Core Features & Use Cases

  • Story-Driven Implementation: Loads the target story, reads its acceptance criteria, tasks, Dev Notes, and status, then executes work in the defined order.
  • Structured Delivery Workflow: Enforces red-green-refactor, comprehensive testing, validation gates, file tracking, and completion updates before marking the story ready for review.
  • Sprint-Aware Execution: Can discover the next ready story from sprint status files, resume after AI review feedback, and keep story and sprint tracking in sync.
  • Use Case: When a team maintains story markdown files and sprint-status.yaml, use this Skill to implement the next ready-for-dev story while preserving process discipline and updating only approved story sections.

Quick Start

Ask the AI to use the bmad-dev-story skill to implement the next ready-for-dev story or to dev a specific story file path.

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 development story from a markdown spec without skipping requirements?

To implement a development story from a markdown spec without skipping requirements, use a story-driven implementation tool that loads the story file, executes tasks in order, and enforces acceptance criteria. It ensures disciplined execution from implementation through review readiness.

What is the best way to enforce red-green-refactor during story implementation?

The best way to enforce red-green-refactor during story implementation is using a structured delivery workflow that applies test-driven development gates. It validates comprehensive testing and file tracking before marking the story ready for review.

How does sprint tracking synchronization work with story files?

Sprint tracking synchronization works by updating sprint-status.yaml files after a story implementation completes. The workflow discovers the next ready story from sprint status files and keeps story and sprint tracking in sync automatically.

Can I resume story implementation after receiving AI review feedback?

Yes, you can resume story implementation after receiving AI review feedback. Sprint-aware execution handles review-follow-up by loading the story file, applying the requested changes, and updating only approved story sections to reach review-ready status.

What are the limitations when modifying story sections during development?

The limitation when modifying story sections is that the workflow applies strict limits on which story sections may be modified. It preserves process discipline by updating only approved sections while executing tasks and syncing sprint status.