skills.rest
AhmedKaram50
AhmedKaram50COMMUNITY
Explore all skills by this author →
GitHub

bmad-dev-story

Load the next ready story and execute its Dev Story Workflow steps.

Updated Mar 18, 2026
Search Tags:#automation#workflow#documentation#story#sprint#dev-workflow
One-click install
npx skills add https://github.com/AhmedKaram50/research --skill bmad-dev-story-ahmedkaram50
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bmad-dev-story
Source: https://github.com/AhmedKaram50/research/tree/main/shopify-builder/_bmad/bmm/workflows/4-implementation/bmad-dev-story
Command: npx skills add https://github.com/AhmedKaram50/research --skill bmad-dev-story-ahmedkaram50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines implementing a story by loading a fully context-rich guide and workflow, enabling rapid translation of story specs into concrete tasks.

Core Features & Use Cases

  • Context-driven story execution: loads Dev Notes, architecture guidance, and sprint context to guide implementation.
  • Deterministic workflow adherence: follows the Dev Story Workflow steps to ensure completeness and traceability.
  • Review-ready output: prepares status, change log, and documentation artifacts for handoff.

Quick Start

Load the next ready story, review its Dev Notes, and begin implementing the first task following the 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 implement the next ready story from sprint-status.yaml?▼

To implement the next ready story, the workflow reads sprint-status.yaml or scans local story files for a ready-for-dev item, extracts the story_key and developer guidance, and uses that context to drive implementation decisions.

What is context-driven story execution in a dev workflow?▼

Context-driven story execution loads Dev Notes, architecture guidance, and sprint context from story files to guide implementation. It translates story specs into concrete tasks by following deterministic workflow steps.

How do I maintain a change log and file list during story implementation?▼

You maintain a change log and file list by executing the Dev Story Workflow steps with strict adherence to Tasks and Validation gates, updating the story file and documentation artifacts as work progresses.

Do I need sprint-status.yaml to start implementing a story?▼

You do not need sprint-status.yaml strictly, as the workflow can scan local story files directly for a ready-for-dev item. However, sprint-status.yaml provides sprint context that drives implementation decisions.

What is the best way to ensure traceability when implementing development stories?▼

The best way to ensure traceability is following the deterministic Dev Story Workflow, which enforces strict adherence to Tasks, Subtasks, and Validation gates while preparing status and change log artifacts for handoff.

When should I not use an automated dev workflow for story implementation?▼

You should avoid automated dev workflows for story implementation when a story lacks defined Dev Notes, clear Tasks, or Validation gates, as the workflow depends on this context to drive implementation decisions.

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
Rinzler78Rinzler78
1

bmad-dev-story

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

Community
Advanced
ldk-hubldk-hub

bmad-dev-story

Executes story implementations from spec files across sprint workflows with built-in validation.

Community
Advanced
elihunter173elihunter173
4

create-jira-ticket

Automate Jira issue creation via CLI commands with customizable fields.

Community
Intermediate