skills.rest
LeGeRyChEeSe
LeGeRyChEeSeCOMMUNITY
Explore all skills by this author →
GitHub

bmad-dev-story

Implements sprint stories from spec files using a red-green-refactor workflow with status tracking.

Updated Aug 25, 2024
Search Tags:#workflow#tdd#test automation#code generation#agile#sprint#story implementation
One-click install
npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-dev-story-legerycheese
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot/tree/main/bmad/src/bmm-skills/4-implementation/bmad-dev-story
Command: npx skills add https://github.com/LeGeRyChEeSe/LanPlay-DiscordBot --skill bmad-dev-story-legerycheese

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It automates disciplined story implementation by guiding an AI developer through a structured workflow that finds ready stories, writes failing tests first, implements code, validates against acceptance criteria, and updates sprint status without skipping steps. ## Core Features & Use Cases - Sprint Story Discovery: Automatically finds the next story marked ready-for-dev in sprint-status.yaml or accepts an explicit story file path. - Test-Driven Implementation: Enforces a red-green-refactor cycle per task, runs regression suites, and blocks completion until all validation gates pass. - Review Continuation: Detects prior code review findings, prioritizes unresolved review follow-up tasks, and marks them resolved in both task and review sections. - Use Case: A developer says "dev this story" and the workflow loads the story spec, implements every task with tests, updates the File List and Change Log, and marks the story ready for review. ## Quick Start Tell the AI to dev the next ready story in the sprint plan or provide a specific story file path to implement.

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 the next story in a sprint plan?▼

Invoke the dev story workflow and it reads sprint-status.yaml to find the first story marked ready-for-dev, then implements it task by task. You can also provide an explicit story file path to skip auto-discovery.

How does the dev story workflow handle test-driven development?▼

It follows a red-green-refactor cycle per task: write failing tests first, implement minimal code to pass them, then refactor while keeping tests green. Tasks cannot be marked complete until all tests exist and pass.

Can the workflow resume a story after a code review?▼

Yes, it detects a Senior Developer Review section in the story file, counts unchecked review follow-up items, and prioritizes resolving them before continuing regular tasks. Resolved items are marked in both the tasks and review sections.

What happens if no ready-for-dev story is found?▼

The workflow halts and offers options: run create-story to draft a new story, run validate-create-story for a quality check, or provide a specific story file path manually.

Which parts of the story file can the workflow modify?▼

Only the Tasks/Subtasks checkboxes, Dev Agent Record, File List, Change Log, and Status sections may be modified. All other story content remains untouched to preserve the original specification.

Related Skills

Explore More Software Engineering Skills→
GenEducationGenEducation

bmad-create-story

Generate implementation-ready story files with acceptance criteria, tasks, and dev notes.

Official
Advanced
quan2005quan2005
13

verification-gate

Compare code changes against story.md and design.md contracts before git commit.

Community
Advanced
AdeptMindAdeptMind

acceptance-validator

Validate completed development work against acceptance criteria and architectural designs.

Official
Advanced
nicolasguelfinicolasguelfi
4

task

Automates governance-driven ad-hoc task creation and tracking in GSE-One sprint workflows.

Community
Advanced