Menu
Pace control. Show current pace, evaluate readiness for promotion/demotion, apply pace changes.
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
Behavioral floor management. Propose changes, review proposals, apply approved changes, view status. Routes to COO as behavioral floor guardian.
Compliance program management. Propose changes, review proposals, apply approved changes, audit conformance, view change log.
Generic floor management. Routes to the declared guardian for any governance floor. Use /floor propose <floor-name> <change> to propose changes to any active floor.
Structured agent-to-agent handoff. Validates artifact, logs metrics event, dispatches receiving agent.
Run a retrospective for the last completed work item. Pulls DORA metrics, summarizes flow, captures keep/stop/start.
Interactive project setup: copy templates, configure fleet, define compliance floor, add first specialist agent.
| name | pace |
| description | Pace control. Show current pace, evaluate readiness for promotion/demotion, apply pace changes. |
| argument-hint | [status|evaluate|change <pace>] |
Manage fleet pace as defined in .claude/COLLABORATION.md § Pace Control.
/pace -- Show current pace and quick health summary/pace evaluate -- Full evaluation with DORA + flow signals and SM recommendation/pace change walk -- Apply a pace change (with confirmation)Read current pace. Parse from .claude/COLLABORATION.md (the Current Pace: **X** line).
Quick health check. Run ops/dora.sh --sm and extract the key signals:
Report. One-screen summary:
## Pace Status
Current: Walk
CFR: 8% (threshold: <=10% for Walk, <=5% for Run)
FPY: 92% (threshold: >=80% for Run)
Recommendation: Advance to Run
Run full metrics. Execute ops/dora.sh (full dashboard) to get DORA + flow quality data.
Dispatch SM agent. The scrum-master evaluates pace readiness using Opus model:
fleet-config.jsonPresent evaluation. Show the SM's full analysis and recommendation. Include the evidence that supports or argues against a pace change.
Parse target pace. Must be one of: Crawl, Walk, Run, Fly.
Validate the change.
Confirm with user. Show current pace, target pace, and the SM's most recent evaluation. Wait for explicit confirmation.
Apply the change. Update the Current Pace: **X** line in .claude/COLLABORATION.md.
Log the event. Record the pace change in the findings register as a "learning" category finding with the rationale. Also log via ops/metrics-log.sh if a pace-changed event type is available; otherwise, note this gap as a finding for the platform-ops agent to address.
Announce. Confirm the pace change and summarize what autonomy behaviors change at the new pace.
| Subcommand | Model | Rationale |
|---|---|---|
/pace (status) | Sonnet | Data lookup, structured reporting |
/pace evaluate | Opus | Judgment: interpreting signals, qualitative assessment |
/pace change | Sonnet | Validation and file update |
Implementers can override to add custom pace signals (e.g., test coverage thresholds, deployment success rates from CI/CD). The thresholds themselves are already configurable in fleet-config.json.