skills.rest
Mission42-ai
Mission42-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

orchestrating-sprints

Automate sprint planning and execution with hierarchical phases and PROGRESS.yaml generation.

Updated Jan 14, 2026
Search Tags:#workflow#orchestration#sprint#CLAUDE#progress-tracking#for-each#gate-tracking
One-click install
npx skills add https://github.com/Mission42-ai/m42-claude-plugins --skill orchestrating-sprints
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrating-sprints
Source: https://github.com/Mission42-ai/m42-claude-plugins/tree/main/plugins/m42-sprint/skills/orchestrating-sprints
Command: npx skills add https://github.com/Mission42-ai/m42-claude-plugins --skill orchestrating-sprints

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill streamlines sprint planning and execution by automating the orchestration of workflow phases, for-each expansions, and progress tracking across sprints.

Core Features & Use Cases

  • End-to-end sprint orchestration with hierarchical phases (prepare → development → QA → deploy).
  • For-each expansion of steps into per-item workflows with separate contexts.
  • Generated PROGRESS.yaml and integrated gate-tracking for quality gates and breakpoints.

Quick Start

Use the orchestrating-sprints skill to initialize and run a sprint orchestration workflow, define a sprint with a .claude/workflows directory, and execute the sprint compiler to produce a PROGRESS.yaml. For example:

  • Create a sprint directory structure
  • Define SPRINT.yaml with a workflow reference
  • Run the sprint to compile and execute

Frequently Asked Questions about orchestrating-sprints

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

FAQPage Schema
How do I automate sprint planning and execution orchestration for software development teams?▼

Sprint orchestration is automated by defining a SPRINT.yaml with a workflow reference in a .claude/workflows directory and executing the sprint compiler to produce a PROGRESS.yaml. It streamlines planning by automating hierarchical phases, for-each expansions, and progress tracking across sprints.

How does for-each expansion work when orchestrating sprints with CLAUDE-powered workflows?▼

For-each expansion in sprint orchestration breaks down steps into per-item workflows with separate contexts. It enables deterministic processing of individual work items within hierarchical phases like prepare, development, QA, and deploy, ensuring isolated execution and contextual task tracking.

Can I track quality gates and breakpoints during sprint execution using PROGRESS.yaml?▼

Yes, quality gate tracking and breakpoints are integrated into sprint execution via the compiled PROGRESS.yaml. The sprint compiler generates this file to provide deterministic progress tracking, contextual fresh-task execution, and visibility into quality gate status across all workflow phases.

Do I need a specific directory structure to run sprint orchestration workflows?▼

Sprint orchestration requires a sprint directory structure containing a .claude/workflows directory. You define a SPRINT.yaml referencing a workflow, then run the sprint to compile and execute it, generating the PROGRESS.yaml file for deterministic tracking across all phases.

What's the best way to structure hierarchical phases for end-to-end sprint orchestration?▼

End-to-end sprint orchestration structures hierarchical phases sequentially: prepare, development, QA, and deploy. This deterministic workflow model allows for-each item expansion and progress tracking within each phase, ensuring comprehensive coverage from initial preparation through final deployment.

Why should I use a sprint compiler for workflow orchestration instead of manual progress tracking?▼

A sprint compiler automates deterministic workflow generation, creating a PROGRESS.yaml that tracks gates, breakpoints, and contextual fresh-task execution. Unlike manual tracking, it ensures consistent orchestration across hierarchical phases and for-each expansions, reducing errors in complex software development sprints.

Related Skills

Explore More Software Engineering Skills→
Mission42-aiMission42-ai

creating-sprints

Create and organize SPRINT.yaml definitions under .claude/sprints with workflow overrides.

Official
Basic
jamiegrandjamiegrand

feature

Coordinate feature development through a structured seven-phase workflow.

Community
Advanced
Mission42-aiMission42-ai

executing-tasks

Execute project tasks through a standardized six-phase workflow.

Official
Advanced
widnyanawidnyana
4

bmad-sprint-run

Automate BMad sprint execution with story creation, quality gates, and code review.

Community
Advanced