coordinator-claude

Rotational arch audit — scores systems, audits top-priority, packages spinoff candidates. Never edits code; updates Last-targeted-audit clock.

Use for new feature requests, vague/ambiguous requirements, or multi-subsystem decomposition before plan mode.

Systematic codebase bug hunt — find and fix all AI-fixable bugs in-session, defer blocked ones to backlog

Night-shift code health review — queries completion entries for today's surfaces, dispatches reviewer, applies findings, updates health tracking.

Run a Codex code review as a second-opinion gate. Returns structured result with findings or graceful skip. Used by /bug-sweep --codex-verify and /workweek-complete Step 7.4.

Cleans up branch sprawl. Triggers: consolidate branches, clean up branches, stale branches, merge all branches.

Check for a published coordinator update and advise a preserve-by-default migration path — never a blind overwrite.

EM-PM conversation to review and prioritize the technical debt backlog. Triggers on demand or when open item count exceeds 20.

Smoke-driven fix-through loop — invoke a newly-built thing (skill, script, pipeline, install process) and fix bugs until it works or gets replanned. Binary outcome only: converge or switch gears.

Run enrichment pipeline on chunk directories

Score a research output against the 5-criteria eval rubric. Dispatches a Sonnet evaluator.

Execute a PM-approved implementation plan end-to-end; default entry is a fresh execution session picked up from an execution handoff

Use when implementation is complete and tests pass — presents structured options for merge, PR, or cleanup to integrate the work.

PM-GATED ceremony that converts raw vision (UI sketches, feature wishlists, enthusiasm) into ratified OKRs plus scaffolded spinoff stubs. Dispatches the VP-Product Reviewer as full OKR critic before any artifact lands on disk. Exit: goal artifact(s) + spinoff-roadmap-creator stubs pre-tagged to the goal. Triggers — 'set goals for this quarter', 'I have a vision for X', 'let's OKR this'.

Involuntary mid-workstream save-state under context pressure. By definition a continuation, never a workstream ending — see Step 0.

Processes state/lessons/ YAML entries as doctrine change-requests. 3 modes: local, central, recheck. Triggers on triage/trim/process lessons, promote universals.

Use when a branch is ready to merge to main. Drafts release notes, creates PR, waits for CI, merges, cleans up.

Create + scaffold + onboard a greenfield repo from any cwd in one command. Creates the dir, git-inits, scaffolds a vendored stack template, delegates coordinator onboarding to repo-setup, optional remote. Sibling of repo-setup (create-new vs onboard-existing).

Pre-merge weekly code-review gate — N code-semantics chunk reviewers (Sonnet) + 3 mechanical specialist workers + no-rewrite synthesizer (BLOCKED/WARN/OK). The Staff Engineer runs a separate post-gate architecture pass, not the gate itself. Invoked only from /workweek-complete.

Dry-run then confirm publish of files from a working source tree to a named publish-repo target. Wraps publish.sh with gate + CI smoke.

Resume work from a handoff or action a cross-repo memo — grab the baton and run

Triangulate plan-claim / code-reality / review oracles to classify each plan into DELIVERED+REVIEWED / DELIVERED-UNREVIEWED / PARTIAL / IN-FLIGHT / ABANDONED. Run after any crash or 'did we actually finish what we think we finished?' moment.

Invoke on any planning trigger from the PM — "plan", "let's plan", "write a plan", "draft a plan", "break this down", "plan the implementation" — for decision-weight work (multi-file, abstraction, cross-system, agent scaffold, reversed prior). Triage lives inside the skill, not in EM pre-skill judgment; writing a plan to disk without invoking this skill is a doctrine violation.

First-time repo setup (default: single-repo), or `--batch` for fleet setup over working-repos.yaml. Consolidates /project-onboarding and /bootstrap-repos into one surface.

Use when a code change / diff / PR is ready for review or code-review findings have landed.

Use when a plan / design doc / RFC is ready for review or plan-review findings have landed.

PM-GATED. Roadmap shaping from research/deep-dive/peer-repo inputs via Synthesize → Substantiate → Plan → Dispatch pipeline producing kind:spinoff-roadmap stubs with deployment_state, blocks/blocked_by graph, machine-readable STUB-INDEX. Stubs cite PM-approved OVERVIEW + research corpus, not EM hand-waving. Triggers — "shape a roadmap", "plan a sprint sequence from this research".

coordinator-claude install-chain walker (chain step 5 of 5 — DAG root; no upstream deps to walk). Reads the install manifest, observes empty direct_deps, emits the DAG-root terminal banner, and exits 0. Not to be confused with coordinator:install (OSS plugin install of the coordinator package) or coordinator:repo-setup (consumer-project first-time setup of the coordinator integration). Trigger phrases: /coordinator:setup, set up coordinator-claude, run the install chain for coordinator.

Converge with the PM on the SHAPE of a problem (the PRD half) before any solutioning. Strategic, not tactical. Exit gate altitude-routes to plan/roadmap-planning/goal-setting based on work horizon.

PM-GATED. Fork a mid-session topic into its own pickup-able handoff (a spinoff). Never EM-initiated.

PM-GATED: ask first; never from subagent. Agent Teams collaborative planning/review for architectural decisions only. Modes: plan, review.

Root-cause discipline for ONE identified bug, test failure, or unexpected behavior — pin the premise, reproduce, trace to source, fix at source, verify. For a single known issue, not a codebase sweep.

Use at cadence gates or to validate repo state. Resolves and runs the project's configured fast-test command.

Wrap up finished work — capture lessons, update docs

Orient session — preflight, load context, choose work