mmp

Manually archive a completed milestone wave. Moves .orchestrator/<state> files into .orchestrator/archive/<milestone>-w<N>-<date>/. Refuses to archive if any chunk is not in merge-ready or merged state without an override flag.

Show security/integrity audit summary (hook blocks, env tampering, version drift)

Bootstrap mmp in the current repository. Verifies dependencies, copies templates from the plugin into .orchestrator/, and runs /mmp:check. Idempotent — refuses to overwrite existing config.yaml without explicit user confirmation.

Run mmp health checks: required upstream plugins, gh auth, repo state, config validity, status.yaml integrity. Reports a green-check matrix. Exit non-zero on hard problems.

Resume an in-progress mmp wave from .orchestrator/status.yaml. Sugar for `/mmp:run <milestone-from-status> --continue`. Fails fast if no status.yaml is present.

Use after PR is CI-green (Phase 6) to verify all acceptance criteria are covered by the implementation by matching AC keywords against the PR diff. Read-only on code; allowed to invoke gh/git/test commands for evidence gathering. Returns per-AC PASS|FAIL with evidence.

Use when L0 needs to verify AC coverage after CI green in Phase 6. Invokes code-review:code-review skill against the PR diff, then verifies each Acceptance Criterion is met. Reports PASS/FAIL per AC.

Use when the milestone orchestrator (L0) dispatches a chunk for implementation. Owns one chunk end-to-end inside an isolated git worktree: brainstorm → spec → plan → execute (TDD) → polish → request-review. Reports back to L0 via status.yaml signals. Never opens a PR — that's L0's job in Phase 5.

Use when L0 needs plan validation (Gate C). Read-only. Verifies plan tasks are bite-sized, TDD-ordered, files within boundary, verification steps present. Returns APPROVE or numbered REVISE list with severity.

Local trigger for the Reverse-Trace-Bot workflow. Use when you do not have access to GitHub Actions CI or want to generate and post the Reverse-Trace Report manually for a closed issue. Builds the AC->Symbol->Caller->Test->Run-ID trace chain and posts it as a GitHub Issue comment.

Use when L0 (Phase 1) needs to analyze cross-cutting concerns between chunks before dispatch, or when user triggers /mmp:cross-cut-analysis manually. Analyzes chunks.md + boundary.yaml (touches_domains, allow, produces, consumes) to produce a structured cross-cut report with severity ratings. Outputs YAML with cross_cuts[] entries and emits a cross_cut_analysis_run audit event.

Use when running mmp's milestone orchestration workflow — invoked by /mmp:run, /mmp:continue, /mmp:improve-tickets, /mmp:archive. Drives Phases 0.5–7 of the multi-subagent delivery methodology: ticket-improvement, decomposition into chunks, L1 dispatch in worktrees, gated reviews, polish, PR-per-chunk, batched final merge. Operates as L0 in the parent session — never writes production code itself, only orchestration artifacts under .orchestrator/.

Use when assessing and improving the quality of GitHub issues — invoked by /mmp:improve-tickets standalone or by orchestrating-milestones in Phase 0.5. Scores tickets via quality rubric, drafts structured rewrites, applies approved improvements via gh CLI (live mode) or local files.

Use when running post-wave retrospection — invoked by /mmp:wave-postmortem standalone or by orchestrating-milestones automatically at Phase 7 end. Reads .orchestrator/status.yaml, audit.jsonl, and per-agent reflexion.md to produce a structured wave-report markdown file with MAST-classified drifts, cap-bump analysis, lessons, and issue-recommendations.

56 hooks across 5 events