Recovery tool. Re-enters the audit step in `ace/workflow.md` when a diff landed without passing through it. TRIGGER when: user invokes `/ace-audit` or asks to review, audit, or check work against skill compliance.
Local agent-to-agent bridge over unix sockets. TRIGGER on `/ace-connect`, "start the bridge", "listen for messages", "tell/send to <agent>", or "what agents are running". DO NOT TRIGGER for intra-session, MCP, or cross-machine messaging.
Scaffold a durable-docs directory with three peers: spec/, decisions/, notes/. TRIGGER on `/ace-docs`, "set up docs", "scaffold docs", "where should ADRs/specs go", or before creating the first spec/decision/notes file in a repo with no `docs/`. DO NOT TRIGGER for editing existing docs or writing user-facing product/API docs.
Two-mode realignment protocol. TRIGGER on "realign" (force re-attention by repeating a broken rule at start or end of every message) or "realign fix" (trace the prompt-chain cause and edit the right context surface — project CLAUDE.md, user CLAUDE.md, memory, in-repo docs, or a skill — so the failure doesn't recur for future sessions or other agents).
Persist session state to durable storage so the next `/ace` resumes cleanly. TRIGGER when the user says "save session", "save state", "checkpoint", "before I clear", "wrap up", "end of session", or otherwise signals they're about to `/clear`, exit, or context-switch. Also trigger when joining a session not started with `/ace`. DO NOT TRIGGER for committing code or saving files — this skill writes session notes only.
ACE school management — proposing skill changes, creating PRs to the school repo, and understanding school structure. TRIGGER when: user wants to propose changes to skills, create a school PR, run `ace diff`, or asks about school structure/workflow. DO NOT TRIGGER for: normal coding tasks or project-specific work.
Start or resume the ACE workflow — surface pending tasks and execute the next step. TRIGGER at session start, after `/clear`, between tasks, or when the user signals continuation at a session boundary ("go", "continue", "next", "what's next", "resume", "ok proceed") with no task currently in progress. DO NOT TRIGGER when the cue refers to the current in-flight edit, command, or step (e.g. "go ahead and apply that", "continue with step 3").