skills.rest
josemariafs
josemariafsCOMMUNITY
Explore all skills by this author →
GitHub

bmad-dev-story

Automate story implementation from context loading to Definition of Done validation.

3|2|Updated Mar 29, 2024
Search Tags:#code-review#test-driven-development#task-tracking#story-workflow#dev-automation#sprint-management
One-click install
npx skills add https://github.com/josemariafs/MVTools --skill bmad-dev-story-josemariafs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/josemariafs/MVTools/tree/main/.cursor/skills/bmad-dev-story
Command: npx skills add https://github.com/josemariafs/MVTools --skill bmad-dev-story-josemariafs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill standardizes and automates the end-to-end workflow of implementing user stories, bringing context, validation, and documentation into a repeatable process.

Core Features & Use Cases

  • Context-driven story implementation guided by Dev Notes, sprint status, and task lists
  • Automated lifecycle: load context, execute steps, track changes, and prepare DoD-ready results
  • Supports review follow-ups and artifacts tracking to ensure traceability

Quick Start

Provide the full path to the story file to start the development workflow.

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 story implementation from a predefined story file?▼

Loading the full path to your story file initiates the workflow, which applies Dev Notes and tracks status in sprint-status.yaml. It validates the Definition of Done and manages artifacts to ensure traceability before marking the story complete.

What is the best way to track sprint status during story implementation?▼

Managing sprint status involves updating sprint-status.yaml throughout the development lifecycle. The workflow automates status tracking and task list management, ensuring progress is validated against the Definition of Done before completion.

Does guided story workflow support test-driven development and code review?▼

Test-driven development and code review are supported through automated test scaffolding and structured task tracking. The workflow standardizes execution, applies Dev Notes, and manages review follow-ups to ensure traceability and quality.

Can I use this for sprint-based development with existing task lists?▼

Sprint-based development is supported by loading your existing story file context. The workflow integrates your predefined task lists, applies Dev Notes, and tracks execution changes to prepare Definition of Done-ready results.

How do I validate the Definition of Done before marking a story complete?▼

Validating the Definition of Done requires the workflow to check task completion, test scaffolding, and documentation integration. It ensures all DoD requirements are satisfied and review follow-ups are managed before marking the story complete.

Why do I need to provide the full path to the story file?▼

The full path to the story file is required to load context, Dev Notes, and task lists for the workflow. This initializes the automated execution process, which tracks changes in sprint-status.yaml and validates the Definition of Done.

Related Skills

Explore More Software Engineering Skills→
bmad-code-orgbmad-code-org
212

gds-dev-story

Automate end-to-end development story execution with DoD validation.

Official
Advanced
diegosanchespereira1diegosanchespereira1

bmad-dev-story

Execute story implementation workflows with test-first validation and status updates.

Community
Advanced
EthansuttorEthansuttor

agent-implementer-sparc-coder

Transform specifications into code with SPARC-driven TDD workflows.

Community
Advanced
skyoxuskyoxu

gds-create-story

Generate a complete Story Context file from epics, architecture, and project context.

Community
Advanced