run-dev-cycle

Orchestrate a multi-agent pipeline from user story creation to local commit.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/panitw/bmad-pipeline --skill run-dev-cycle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-dev-cycle
Source: https://github.com/panitw/bmad-pipeline/tree/main/skills/run-dev-cycle
Command: npx skills add https://github.com/panitw/bmad-pipeline --skill run-dev-cycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the fragmentation of the software development lifecycle by automating the hand-offs between story creation, implementation, code review, and final commit, ensuring consistent quality and decision-making across a team of specialized agents.

Core Features & Use Cases

  • Pipeline Orchestration: Drives stories through a four-phase pipeline (Creator, Developer, Reviewer, Finisher) while maintaining context and state.
  • Decision Management: Uses a persistent engineering lead agent to provide consistent rulings on technical trade-offs, with an escalation path to the owner for high-stakes decisions.
  • Use Case: When you need to implement a series of user stories, this skill manages the entire process, from generating the story file to running integration tests and committing the final code, pausing only when your human input is required for design decisions.

Quick Start

Use the run-dev-cycle skill to develop stories 26.1 through 26.3 from the current sprint status.

Frequently Asked Questions about run-dev-cycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How can I automate the software development lifecycle from story creation to local commit?

You can automate the software development lifecycle by orchestrating a multi-agent pipeline that drives user stories through sequential phases for creation, implementation, review, and finishing until reaching a local commit.

How does multi-agent pipeline orchestration handle code review and technical decisions?

Multi-agent pipeline orchestration handles code review by assigning specialized agents to evaluate code, while a persistent engineering lead agent provides consistent rulings on technical trade-offs and escalates high-stakes decisions to the owner.

What do I need to set up before orchestrating an automated agile development pipeline?

Before orchestrating an automated agile development pipeline, you need to integrate project-specific sprint tracking files and configure a shell-based test environment to enforce quality gates and architectural consistency.

When should I use automated story delivery orchestration instead of manual coding?

Automated story delivery orchestration is ideal when implementing a series of user stories that require consistent state management and quality enforcement across development, review, and commit phases without continuous manual intervention.

Does the development orchestration pipeline pause for human input during execution?

Yes, the development orchestration pipeline pauses execution specifically when human input is required for design decisions, allowing the automated agents to handle implementation while maintaining an escalation path for high-stakes choices.