orchestrating-milestones

Orchestrate GitHub milestone delivery through gated phases and chunked PRs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ahlerjam/mmp --skill orchestrating-milestones
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrating-milestones
Source: https://github.com/ahlerjam/mmp/tree/main/skills/orchestrating-milestones
Command: npx skills add https://github.com/ahlerjam/mmp --skill orchestrating-milestones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, yq, git, superpowers, code-simplifier, code-review, alembic, code-review, ci-wait (script usage), and includes references (resource) components.

What problem does it solve?

Orchestrating multi-chunk GitHub milestone delivery with strict sequencing, role boundaries, and verifiable gates—without the coordinator drifting, skipping verification, or creating merge conflicts.

Core Features & Use Cases

  • Phase-structured milestone execution (L0 → gated L1 worktrees): drives Phases 0.5–7 with explicit invariants and approval gates.
  • Decomposition into bounded implementation chunks: generates chunk plans within hard caps (files/LOC/hours) and waits for user approval before dispatch.
  • Reviewer-gated specifications and plans: enforces external Gate B (spec) and Gate C (plan) verification to prevent self-review bias.
  • Evidence-driven phase advancement: requires structured verification evidence and blocks phase transitions unless evidence conditions are satisfied.
  • CI-aware PR lifecycle with per-chunk PRs: opens one PR per chunk, ensures CI/coverage gates, and performs batched final merge with circuit-breaker behavior.

Quick Start

Run this skill by issuing /mmp:run and point it at the target GitHub milestone you want to orchestrate.

Frequently Asked Questions about orchestrating-milestones

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

FAQPage Schema
How do I orchestrate a multi-chunk GitHub milestone end-to-end without merge conflicts?

You orchestrate a GitHub milestone by decomposing it into bounded implementation chunks, dispatching work to isolated git worktrees, and enforcing evidence-gated phase transitions to prevent merge conflicts and skipped verification.

How does multi-agent milestone orchestration enforce strict sequencing and verification?

Multi-agent milestone orchestration enforces strict sequencing through hard invariants including decomposition approval gates, external reviewer verification for specs and plans, and evidence-driven phase advancement under the L0 coordinator.

Do I need git worktrees and gh CLI to coordinate multi-subagent milestone delivery?

Yes, coordinating multi-subagent milestone delivery requires git worktrees for isolated chunk implementation, the gh CLI for PR lifecycle management, and jq or yq for atomic status and audit updates.

What is the best way to manage gated reviews and CI checks for chunked GitHub milestone work?

The best way to manage gated reviews and CI checks is opening one PR per implementation chunk, requiring external reviewer verification at spec and plan gates, and applying circuit-breaker behavior during the batched final merge.

Why does milestone orchestration block phase transitions without evidence validation?

Milestone orchestration blocks phase transitions without evidence validation to prevent the coordinator from drifting, skipping verification, or advancing phases when structured verification evidence conditions are not satisfied.

When should I not use automated milestone orchestration for GitHub project delivery?

You should not use automated milestone orchestration if your project lacks strict sequencing requirements, cannot support isolated git worktrees, or needs to bypass external reviewer gates and CI/coverage verification for rapid prototyping.