fredhead88

drop

Drop an advisory memo into the orchestrator's inbox — a 'this might affect how you're thinking' note that is context, never a work item. Use when the user says 'drop', '/drop', 'leave a memo for the orchestrator', 'note this for orc', or when a thinker session realizes something relevant to other in-flight work mid-brainstorm. A memo is updatable in place and is structurally NOT a spec — the orchestrator never builds from it. An ADVANCED add-on to the DO-IT pipeline; read DO-IT.md for the shared protocol.

handover

Drop a finished spec into the orchestrator's inbox so a separate orchestrator session can pick it up by reading a file path. Use when the user says 'handover', '/handover', 'hand this spec over', 'ship the spec', 'send this to the orchestrator', or any time a spec written in this session needs to reach the orchestrator on the same machine. Validates the spec header (refuses to drop without an intent: and acceptance criteria) and places the file atomically. NO git, NO commit — the orchestrator owns git. Part of the DO-IT pipeline; read DO-IT.md for the shared protocol.

orc

Boot a session into the ORCHESTRATOR role for your repo. Use when the user says 'orc', '/orc', 'be the orchestrator', 'start as orchestrator', 'boot the orchestrator', 'this is the orchestrator session', or opens a session whose job is to take specs written by thinker sessions, write the execution plan, dispatch sub-agents to build it, verify their work, integrate it cleanly, and deploy. The orchestrator is the SINGLE session that touches the real working tree and the only one that commits. It runs on Opus, stays lean and interactive, dispatches Sonnet workers in the background, grades their output with a fresh blind sub-session, deploys and confirms the deploy landed, keeps the git tree + INTENT/architecture/health docs pristine, mirrors the ledger to a harness task list, and hands off to the next orchestrator via a relay baton. Invoke at the START of an orchestrator session.

planner

Boot an intake/triage session that turns a raw dump — scattered ideas, meeting notes, transcripts, pasted fragments — into discrete, structured briefs for thinker sessions, plus a roadmap memo for the orchestrator. Use when the user says 'planner', '/planner', 'triage this', 'sort these ideas into topics', or hands over a pile of unorganized input. The planner ORGANIZES; it does not brainstorm, recommend approaches, or write specs. An ADVANCED add-on to the DO-IT pipeline; read DO-IT.md for the shared protocol.

think

Boot a session into the THINKER role for your repo. Use when the user says 'think', '/think', 'thinker session', 'let's spec something out', 'brainstorm X', 'triage these ideas', 'sort this dump', or 'collect some bugs' — any session whose job is discovery, intake, or capture that ends in a spec, not code. A thinker is READ-ONLY on code: never edits files, never touches git. It has three shapes (brainstorm / intake-triage / collect) and performs its own handoffs (hand a spec to the orchestrator, send a memo). Stage 2 of the DO-IT pipeline. Invoke at the START of a thinking session.

aaaudit

Use when you want a vicious, cross-vendor adversarial audit of a spec, an execution plan, or code — before committing to it. Routes critique to Codex (a different vendor model) so blind spots aren't shared, applies a production-sacred severity discipline, and is critique-only (never edits). Trigger on "adversarially audit / red-team / tear apart this spec|plan|code", or "audit uncommitted".

spec-handover

Hand a finished spec over to the orchestrator. Use when the user says 'spec handover', '/spec-handover', 'hand this spec over', 'ship the spec', 'send this to the orchestrator', 'get this spec across', or any time a spec doc written this session needs to reach the orchestrator session. One atomic, self-verifying action — places the numbered spec in the bus AND writes its ledger record, or errors loudly. NO git. If the spec isn't written yet, this is the wrong skill.

verification-loop

Use when verifying shipped work on prod, standing up the autonomous verifier, running the verification loop, confirming a spec is actually done end-to-end, or checking whether shipped criteria are hollow. Trigger phrases include 'verify shipped work', 'stand up the verifier', 'run the verification loop', 'is this actually done on prod', 'check for hollow specs', 'autonomous post-ship review'.

rev

Boot a session into the REVIEWER role for your repo. Use when the user says 'rev', '/rev', 'be the reviewer', 'start the review session', 'this is the rev session', or opens a session whose job is to drive the verification loop, watch what's awaiting prod-verification, spot-check the rendered product, write per-criterion verdicts, and file correctives back to the orchestrator. rev is the standing review twin of orc — one builds, one reviews. It runs on Opus, self-relays on a context ceiling exactly like orc (its OWN relay, never orc's), never touches the build tree, never commits, never authors specs. Invoke at the START of a reviewer session.