bmad-dev-story

Execute story-based development workflows with testing and definition-of-done validation.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-dev-story-marcmontecalvo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/marcmontecalvo/kinward/tree/main/.agents/skills/bmad-dev-story
Command: npx skills add https://github.com/marcmontecalvo/kinward --skill bmad-dev-story-marcmontecalvo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the challenge of maintaining consistency and rigor during software development by automating the execution of story-based implementation workflows, ensuring every acceptance criterion is met and every task is validated.

Core Features & Use Cases

  • Strict Workflow Enforcement: Executes development steps in a precise, non-skippable order, including red-green-refactor cycles and definition-of-done validation.
  • Context-Aware Implementation: Automatically integrates project-wide standards, sprint status, and technical guidance from story files to inform coding decisions.
  • Use Case: When a developer needs to implement a new feature, this Skill reads the story specification, loads the project context, executes the implementation tasks, runs tests, and validates the final output against the definition of done.

Quick Start

Invoke the bmad-dev-story skill to implement the next story in the sprint plan by simply telling the agent to implement the next story in the sprint.

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-based development workflows and enforce the definition of done?

Automating story-based development workflows involves parsing story specifications and enforcing rigorous implementation, testing, and validation cycles. This ensures every acceptance criterion is met and every task is validated through non-skippable development steps.

What is a red-green-refactor cycle in automated software development?

A red-green-refactor cycle is a strict testing workflow where you write a failing test, implement code to pass it, then optimize the structure. Automated development enforces this sequence precisely to guarantee high-quality, validated code delivery.

How do I track sprint status and task completion within my project repository?

Tracking sprint status and task completion requires operating within project repositories to manage development cycles. Context-aware automation reads story specifications and loads project-wide standards to inform coding decisions and update sprint progress automatically.

Do I need Python to run automated development validation cycles?

Yes, Python is required for resolving configuration and adhering to predefined development steps. The automated workflow relies on Python-based resolution to maintain consistent, high-quality code delivery and strict definition-of-done compliance.

Can I skip implementation steps if my feature is simple?

No, the workflow executes development steps in a precise, non-skippable order. Strict enforcement guarantees that all acceptance criteria are met and every task undergoes complete testing and definition-of-done validation regardless of complexity.