bmad-dev-story

Read sprint story files and guide development through tests and status updates.

1|Updated Dec 22, 2022
One-click install
npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-dev-story-rinzler78
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/Rinzler78/osmosis-launcher/tree/main/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/Rinzler78/osmosis-launcher --skill bmad-dev-story-rinzler78

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you execute a development story end to end when you have a filled-in story spec, so you can move from requirements to implementation without missing workflow steps, validation, or required updates.

Core Features & Use Cases

  • Story-guided implementation: Follows the story file's tasks, acceptance criteria, dev notes, and review follow-ups in order.
  • Test-first development support: Encourages red-green-refactor execution with validation before marking work complete.
  • Workflow tracking: Updates story status, file lists, change logs, and dev agent records as work progresses.
  • Use case: A developer receives the next sprint story and uses this Skill to implement it, test it, record changes, and prepare it for review.

Quick Start

Ask the AI to implement the next ready story from your sprint plan and keep the story file updated through review readiness.

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 sprint story from a markdown file without missing workflow steps?

Sprint story implementation from markdown files is guided by reading story metadata, extracting acceptance criteria, and executing tasks in order. The workflow enforces test-driven development, validates changes, and updates story status to ensure complete story delivery.

What is the best way to track story status and dev notes during sprint execution?

Story status tracking during sprint execution is handled by automatically updating task checkboxes, dev notes, file lists, and change logs within the story markdown file. This synchronization keeps story progress visible and prepares the story for code review readiness.

How does test-driven development integrate with story implementation workflows?

Test-driven development integrates with story implementation by encouraging a red-green-refactor cycle. The workflow validates tests against acceptance criteria before marking story tasks complete, ensuring that implementation satisfies the required dev notes and validation steps.

How do I handle code review follow-ups when completing a sprint story?

Code review follow-ups are handled by processing review feedback directly within the story file. The workflow reads review notes, executes required implementation changes, runs validation checks, and updates the change log to track the resolution of story review items.

Do I need structured story markdown files to automate sprint execution?

Structured story markdown files are required to automate sprint execution. The workflow relies on parsing story metadata, acceptance criteria, task checkboxes, dev notes, and change logs from the file to guide implementation and synchronize sprint status accurately.

Can I use story-driven development for tracking story completion in existing repositories?

Story-driven development supports tracking story completion in existing repositories by reading structured story markdown files. It applies to sprint execution and code review follow-ups, updating file lists and sprint status directly within the repository's existing workflow.