run-milestone

Orchestrates autonomous milestone execution by dispatching issues to parallel agents and merging reviewed PRs.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/sagittaras/agentic-workflow --skill run-milestone-sagittaras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-milestone
Source: https://github.com/sagittaras/agentic-workflow/tree/main/skills/run-milestone
Command: npx skills add https://github.com/sagittaras/agentic-workflow --skill run-milestone-sagittaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating a planned milestone by hand means tracking issue dependencies, dispatching work, reviewing every PR, resolving integration conflicts, and merging in the right order — a long, error-prone process. This Skill automates that entire loop: it builds the dependency graph from tracker issues, verifies the plan passed review, dispatches unblocked issues to parallel agents, enforces dual-role PR review, runs an integration gate, and merges into an integration branch. ## Core Features & Use Cases - Dependency-aware dispatch: Builds a dependency graph from issue bodies, dispatches only unblocked issues to parallel worktree-isolated agents matched by area:* labels, and never re-dispatches a running issue. - Two-role PR review: Every PR is reviewed by a strictly scoped acceptance-criteria role and a code-quality role, with retry budgets, escalation on disagreement, and an integration gate that catches semantic conflicts before merge. - Wave-aware execution: Detects new issues added to the milestone mid-run, re-verifies the review evidence, resumes interrupted runs from existing PRs, and finishes with a single integration PR to the default branch. - Use Case: After planning and reviewing a milestone with plan-milestone and review-milestone, invoke this Skill to have all issues implemented, reviewed, and merged autonomously while you only handle escalations. ## Quick Start Ask the assistant to run the milestone by saying: run the milestone named 'Q3 billing rework' and let it implement all its issues.

Frequently Asked Questions about run-milestone

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

FAQPage Schema
How do I run a milestone autonomously with AI agents?

Invoke the run-milestone skill with the milestone name, number, or slug. It builds the dependency graph from tracker issues, dispatches unblocked issues to parallel agents, reviews each PR with two roles, and merges into an integration branch.

What must exist before running a milestone?

The milestone must be planned with issues created and reviewed — the skill checks for a review report comment on the lowest-numbered issue. The project also needs a CONTRIBUTING.md workflow section defining the forge, branching strategy, and verification commands.

Does run-milestone work with GitHub and Gitea?

Yes, it supports both forges. Gitea operations use MCP tools loaded via ToolSearch, while GitHub operations use bundled gh-based shell scripts that require an authenticated gh CLI and the owner/repo argument.

What happens when a pull request fails review?

The skill sends the PR back for one retry with the reviewers' concrete findings and a mandatory mutation-testing verification. If it fails a second time, the PR stays open, the issue is escalated, and dependent issues remain blocked.

Can run-milestone resume an interrupted run?

Yes. On startup it classifies every issue by existing PR state — no PR, open PR, or merged PR — and resumes from the correct step instead of re-dispatching completed work or re-creating the integration branch.

When should I not use run-milestone?

Do not use it to create the plan or issues (use plan-milestone), to assess plan quality (use review-milestone), or to implement a single issue (use implement-issue directly). It only executes an already planned and reviewed milestone.