Menu
pan rollout <status|retry> <id> — inspect or re-run post-merge release coordination
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Add repositories to the current progressive polyrepo workspace
pan close <id> — close-out ceremony for a completed and merged issue
pan review <subcommand> — manage the code review lifecycle: list pending work, re-request review, heal status drift, reset/abort/restart review cycles
pan start <id> — spawn a work agent for an issue in its own tmux session and workspace
Maintain a project knowledge wiki in Open Knowledge Format with /okf init, open, author, convert, sync, study, retro, extract, validate, lint, and embed.
pan flywheel — start, pause, resume, complete, stop, inspect, emit, and report on the singleton Fix-All Flywheel orchestrator
| name | pan-rollout |
| description | pan rollout <status|retry> <id> — inspect or re-run post-merge release coordination |
| triggers | ["pan rollout","rollout status","rollout retry","release status","retry release"] |
| allowed-tools | ["Bash"] |
Post-merge release coordination for projects with a release: config section.
This is distinct from pan release, which publishes npm stable/canary packages.
pan rollout status <issue-id>
pan rollout retry <issue-id>
pan rollout status prints the issue's releaseStatus and each configured
component's key, release order, and current status.
pan rollout retry re-runs the release engine for the issue (health checks,
version checks, smoke tests, rollback if configured) and prints the resulting
status.
Projects opt in via projects.yaml:
projects:
- key: myn
release:
components:
api:
provider: kubernetes
trigger: auto
health_url: https://api.myn.example.com/health
version_check: scripts/check-version.sh api
smoke_test: scripts/smoke.sh api
rollback: scripts/rollback.sh api
frontend:
provider: vercel
trigger: auto
depends_on: [api]
health_url: https://myn.example.com/health
smoke_test: scripts/smoke.sh frontend
docs:
provider: vercel
trigger: skip
trigger: auto means Overdeck waits for the external deploy and verifies it;
it does not invoke the provider deploy itself. trigger: manual blocks and
requires an operator to release that component. trigger: skip excludes the
component from the plan.