Help the user author a well-specified Architecture Decision Record (ADR) — a single, well-scoped decision with context, consequences, and verifiable acceptance criteria. Use when the user wants to write / draft / scope an ADR, record an architecture or technical decision, turn a rough idea or issue into a decision record, or prepare a spec to feed the `orchestrate` planning skill. Discovers the repo's existing ADR convention and ledger, interviews only where the request is vague, grounds lightly in real code, and pre-validates the result against the same rubric `orchestrate`'s Phase 0 gate scores — so a code-change ADR hands off cleanly. Not for general documentation, multi-decision design docs, or writing the implementation plan itself (that is `orchestrate`'s job).
Drive interactive Codex sessions in WezTerm — to get a second opinion / review from Codex on ANY artifact (code, a design, an analysis, a document, a script), to validate a design or scope a phase with Codex BEFORE implementing, and to ask Codex ad-hoc questions. Use when the user asks Claude to have Codex review something (code OR a design/analysis/document/artifact), get a second opinion from Codex, run a Codex review gate/loop, codex-review a script before running it, validate/scope a design with Codex before building, ask Codex a question, relay a question to Codex, use WezTerm for Codex, or apply a Codex GO / FIXES_REQUIRED review workflow. A review is artifact-agnostic — never assume it is a "code review". Reviews run in a fresh interactive session that writes its review to a file and replies DONE; questions (incl. design consultations) run in one reusable interactive session.
Turn a well-specified change request (ADR / spec / issue / feature) into a dependency-ordered, test-first, code-grounded GOAP execution plan. Use when the user wants to plan a complex, multi-part or cross-cutting implementation before writing code; wants a TDD/test-first execution plan; wants work fanned out across code-grounded analysis agents and synthesized into a dependency-ordered plan; or asks to "orchestrate", "plan this ADR/feature", "structure this into workstreams", or "build a test-first plan". Derives its own workstreams from the spec + real code (does not assume fixed API/Data/UI lanes), grounds every step in cited source, and gates the plan through a perspective-diverse Codex critique panel before the human ratifies and writes the final plan of record.