Menu
Fleet mode — one control plane over many ContextDevKit repos (portfolio stats, cross-repo audit, AGENTS.md rule-drift).
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
Domain Engineering diagnostic — shows what the classifier decides for an objective (CMIS/DAS/profile/skills/mode). Observation-only; never mutates or blocks.
Business-driven methodology entry point — classify (intake), create/advance an Operation or Business work context, and drive the intake → operation → nested-workflow flow. Host-neutral; dry-run by default.
Workflow Navigator — shows the current phase, deliverables, and next commands for an ADR-0057 workflow. Read-only; never mutates state.
Start a focused session on one objective — locks scope, blocks opportunistic refactors.
Deterministic QA gate (ADR-0055) — run the project suite; green + complete acceptance criteria ⇒ qa-approve testing cards into conclusion; red ⇒ report (and qa-reject only attributable failures).
L6 — autonomous feature pipeline. Drives the full squad: design → implement → review → test → log. Checkpoints can be manual or automatic.
| name | source-command-fleet |
| description | Fleet mode — one control plane over many ContextDevKit repos (portfolio stats, cross-repo audit, AGENTS.md rule-drift). |
Use this skill when the user asks to run the migrated source command fleet.
Operate on a portfolio of ContextDevKit repos at once. The registry lives outside
any repo — ~/.contextdevkit/fleet.json (override CONTEXT_FLEET_FILE). Helper:
contextkit/tools/scripts/fleet.mjs.
Act on $ARGUMENTS:
node contextkit/tools/scripts/fleet.mjs add <path-to-repo>
node contextkit/tools/scripts/fleet.mjs list
Register the repos you want the fleet to cover (absolute paths are stored).
node contextkit/tools/scripts/fleet.mjs stats # or --json
Runs each repo's stats.mjs and aggregates: level, registered sessions, ADRs,
agents, drift rate per repo + totals. Call out the repos that look unhealthy
(high drift, no recent sessions, stuck at a low level).
node contextkit/tools/scripts/fleet.mjs audit # or --json
Runs each repo's deep-analysis.mjs and aggregates finding counts. Surface the
repos carrying the most debt/risk; suggest where to run /deep-analysis or
/deps-audit next.
node contextkit/tools/scripts/fleet.mjs propagate <rule-file>
Reports which repos' AGENTS.md lack a given rule block. Fleet does not
auto-edit — for each MISSING repo, add the rule with judgment (it may need
adapting per stack), ideally via that repo's own session + PR.
Summarize the portfolio: totals, the 1–3 repos needing attention, and the concrete next action per repo. Keep it advisory — the fleet informs, you decide.