exarchos

Toggle autocompact on/off or set threshold percentage

Save workflow state and prepare for session handoff

Resolve merged workflow to completed state

Start debug workflow for bugs and regressions

Dispatch tasks to subagents

Use this agent when dispatching TDD implementation tasks to a subagent in an isolated worktree. <example> Context: Orchestrator is dispatching a task from an implementation plan user: "Implement the agent spec handler (task-003)" assistant: "I'll dispatch the exarchos-implementer agent to implement this task using TDD in an isolated worktree." <commentary> Implementation task requiring test-first development triggers the implementer agent. </commentary> </example>

Use this agent when a task has failed and needs diagnosis and repair with adversarial verification. <example> Context: A delegated task failed its quality gates or tests user: "Task-005 failed TDD compliance — fix it" assistant: "I'll dispatch the exarchos-fixer agent to diagnose and repair the failure." <commentary> Failed task requiring root cause analysis and targeted fix triggers the fixer agent. </commentary> </example>

Use this agent when performing read-only code review for quality, design compliance, and test coverage. <example> Context: Feature implementation is complete and needs review user: "Review the agent spec handler for code quality" assistant: "I'll dispatch the exarchos-reviewer agent to analyze code quality and design compliance." <commentary> Code review request triggers the reviewer agent for read-only analysis. </commentary> </example>

Use this agent for low-complexity scaffolding tasks — file creation, boilerplate generation, and structural setup. <example> Context: Orchestrator needs new files or boilerplate created user: "Create the directory structure and stub files for the new feature" assistant: "I'll dispatch the exarchos-scaffolder agent to generate the scaffolding in an isolated worktree." <commentary> Simple file creation and boilerplate generation triggers the scaffolder agent with concise output. </commentary> </example>

Guided authoring of an architectural invariant catalog entry through a 6-step interview (elicit, locate, weight, enforce, number, commit). Drives the invariants_scaffold and invariants_add orchestrate verbs — the agent supplies judgment and natural-language elicitation; the verbs own schema validation, file writing, and event emission. Defaults to mode: audit; mode: check is an advanced opt-in. Triggers: 'add an invariant', 'author an invariant', 'enforce an architectural rule', or /exarchos:invariants. Do NOT use for: editing workflow state, running a review, or hand-writing YAML (the verbs write it — never emit catalog YAML yourself).

Collaborative design exploration for new features and architecture decisions. Triggers: 'brainstorm', 'ideate', 'explore options', or /ideate. Presents 2-3 approaches with trade-offs, documents chosen approach. Do NOT use for implementation planning or code review. Requires no existing design document — use /plan if one exists.

Post-merge workflow resolution. Verifies PR merge status, backfills synthesis metadata, force-resolves review statuses, transitions to completed, and cleans up worktrees/branches. Use when the user says 'cleanup', 'resolve workflow', 'mark as done', or runs /cleanup. Do NOT use before PRs are merged.

Bug investigation and fix workflow. Triggers: 'debug', 'fix bug', 'investigate issue', 'something is broken', or /debug. Hotfix track for quick fixes, thorough track for root cause analysis. Do NOT use for feature development or refactoring. Do NOT escalate to /ideate unless the fix requires architectural redesign.

Dispatch implementation tasks to agent teammates in git worktrees. Triggers: 'delegate', 'dispatch tasks', 'assign work', or /delegate. Spawns teammates, creates worktrees, monitors progress. Supports --fixes flag. Do NOT use for single-file changes or polish-track refactors.

2 hooks across 2 events