monaco-milestone
Names the Monaco command for each step of shipping a ticket or running a milestone. Use when writing, batching, dispatching, verifying, landing, restacking or promoting milestone tickets.
Install
npx skillscat add munyon-canyon/monaco/monaco-milestone Install via the SkillsCat registry.
Monaco milestone
The procedures are docs/how-to/ship-a-ticket.md for an owner and docs/how-to/run-a-milestone.md for the root. Read the one for your role first. This table names the command for each step.
Owners run stage 0 from apps/backend as go run ./cmd/monacoctl agents check. The root builds the tools once with just build backend and runs bin/monacoctl from a worktree at the staging tip, rebuilding after a merge that changes cmd/monacoctl/agents.
| Step | Command |
|---|---|
| ticket | the write-ticket format in .cursor/skills/write-ticket/SKILL.md, with Touches in backticks and Blocked by on the header line |
| batch | monacoctl agents batch <issue>... |
| dispatch | monacoctl agents dispatch <ticket> --model opus (--urgent outside the batch, --dry-run to preview), then monacoctl agents own <ticket> <agent-id> |
| stage 0 | monacoctl agents check |
| submit | gt submit --stack --no-interactive --draft, then scripts/pr-body.sh <pr> "<title>" <file> for each PR |
| owner finished | monacoctl agents done <ticket>, then monacoctl agents exited <ticket> once its process stopped |
| verify | monacoctl agents verify-plan <pr>; the stage 1 CI job e2e runs scripts/ci/e2e.sh, which runs monacoctl verify on the real binaries. The verifier runs no tests |
| verdict | monacoctl agents verdict pass <pr> <sha> --kind <kind> --model <model> --report <file> (or fail); monacoctl agents verdict carry <pr> after a restack that left the PR's own added and removed lines unchanged |
| landing | always, without asking, right after gt submit and scripts/pr-body.sh: monacoctl agents land-stack <top-pr> once, then monacoctl agents watch under Monitor. It labels every PR of the stack merge-queue for the Graphite queue. If stage 1 is still running, land-stack arms the stack, and agents watch lands it once stage 1 passes, or prints armed stack #<top> disarmed: ... when it fails. The verifier's verify status is advisory: landing does not wait on it. When a flow the stack touches changed on staging, land-stack arms the stack and starts flows-verify on just that flow, and agents watch lands it once that passes; a disarm that says flows-verify failed means restack with gt, rerun stage 1, then land-stack again; flow <id> is in queued stack #M means wait for #M to land, then land-stack again. Never gh pr merge, never a base change, never merge-queue or fast-track by hand. The queue squashes each PR into one commit on staging (title, (#N), body), so a landed PR shows closed, not merged, and its Closes #N closes the ticket. A stack that dropped out: gt modify, gt submit --stack --no-interactive --draft, then land-stack again. To change a queued stack, run monacoctl agents dequeue <top-pr> first, then gt modify and gt submit --stack --no-interactive --draft, then land-stack again. Removing the label by hand is not enough: Graphite re-adds it from its own state and may requeue unverified heads. dequeue removes the label from every PR, waits until it stays off and no open gtmq_ draft lists the stack, and prints safe to push. The agent guard hook blocks gt submit, gt modify, gt restack and git push on a stack while any of its PRs carries merge-queue. |
| watching | monacoctl agents watch under Monitor, right after land-stack: it streams queue, Graphite queue draft and failure events and settles landed stacks. Never sleep or poll. --once for cron. Also monacoctl agents forecast, monacoctl agents conflicts <pr> |
| status | monacoctl agents status --publish, after each batch, dispatch, merge and ejection |
| restack | root only: gt sync --no-interactive --no-restack, gt restack --upstack in the stack's worktree, then stage 0 on every branch |
| promotion | the CHANGELOG.md rename PR, then one PR from staging into main labeled integration; the operator merges it with a merge commit, and staging stays the trunk |
| handoff | monacoctl agents handoff; monacoctl agents resume <ticket> before reusing an owner |
| timeline | monacoctl agents timeline |
A dispatch prompt carries only the ticket number, the worktree, the parent SHA, and the brief path (docs/agents/owner.md or docs/agents/verifier.md). monacoctl agents dispatch prints the owner's spawn line and prompt, and monacoctl agents verify-plan the verifier's; pass them as printed.
The status comment on the tracking issue carries the batch, so CI keeps it current. A handoff is a tracking-issue comment from monacoctl agents handoff. Nothing goes on a side branch.
Install
npx skillscat add munyon-canyon/monaco/monaco-milestone Install via the SkillsCat registry.
Repository Stars
The star count shown is for the parent repository (Munyon-Canyon/monaco), not this specific skill.
.claude/skills/monaco-milestone