bmad-dev-story

Automate software story implementation from context-filled spec files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers automate the implementation of software stories by following a context-filled story spec, reducing back-and-forth and ensuring alignment with project guidance.

Core Features & Use Cases

  • Context-driven Story Implementation: Executes story steps using the embedded Dev Notes and sprint context to deliver deterministic results.
  • Sprint-ready Workflow: Integrates with sprint-status, File List, and Change Log to keep progress tracked and auditable.
  • Real-world Use Case: A developer runs "dev this story 1-2-user-auth" to implement the next ready-for-dev story with architecture guidance and acceptance criteria.

Quick Start

Provide a ready story file path and initiate the development workflow following the context notes.

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 software story implementation from a spec file?

Automating story implementation requires a context-filled spec file containing architecture guidance and acceptance criteria. The workflow executes story steps using embedded Dev Notes and sprint context to deliver deterministic results, coordinating with sprint-status and DoD validations.

Can I use sprint-based development workflows with standalone story files?

Sprint-based development workflows support both sprint-integrated and standalone story files. The process tracks progress using sprint-status, File List, and Change Log components to keep development auditable and aligned with project guidance.

What is context-driven story implementation in software engineering?

Context-driven story implementation executes development tasks using embedded Dev Notes and sprint context to produce deterministic results. It ensures architectural guidance, technical specifications, and validation rules described in the story context are satisfied.

How do I validate Definition of Done criteria during automated dev workflows?

Validating Definition of Done criteria happens automatically during story implementation by applying DoD validations described in the story context and Dev Notes. This ensures the automated workflow satisfies architectural guidance and technical specifications.

Do I need a specific project structure to implement stories from context-filled specs?

Implementing stories from context-filled specs requires a ready story file path and associated Dev Notes. The workflow integrates with sprint-status, File List, and Change Log to keep progress tracked, so these elements should exist in your project structure.

What's the best way to reduce back-and-forth when implementing sprint stories?

Reducing back-and-forth during sprint story implementation is achieved by following a context-filled story spec that embeds architecture guidance and acceptance criteria. This ensures alignment with project guidance and delivers deterministic development results.