Always-on Conducty orchestration for Codex. Use by default for coding, debugging, refactoring, review, CI, deployment, production-change, multi-step planning, substantial research, agent coordination, tracer-first execution, vault memory, prompt logging, checkpoints, ship gates, or improvement loops. Prefer the conducty-codex MCP tools when available.
Dispatches Claude Code Task subagents to run prompts from a vault plan note. Tracer-first execution, time-budgeted work, calibrated review rigor. Use when the user says "execute the plan", "run group A", "dispatch", or is ready to run prompts from a `Plans/Plan YYYY-MM-DD HHmm` note in the vault.
Caveman-style compression for conducty orchestration artifacts — subagent prompt text, plan note prompt blocks, prompt log entries, checkpoint notes. Cuts token waste in the orchestration layer where "prompt quality is leverage" already demands tight signal-to-noise. Use when user says "conducty-terse", "terse mode", "compress prompts", "tight prompts", or invokes /conducty-terse. Does NOT change subagent output, code, commits, acceptance criteria, no-go zones, or verification commands — those stay verbatim.
First-run walkthrough for Conducty. Confirms vault location, seeds indexes if missing, ingests the user's primary project via [[conducty-context]], and produces a tiny scoped first plan so the user sees the cycle end-to-end. Use when the user says "set up Conducty", "first time", "get started", "bootstrap", "I just installed Conducty", or when no plans yet exist in the vault.
Quality gate between parallelization groups. Verifies every prompt at its assigned review level, computes health metrics, detects systemic failures, updates hill charts. Use when a group finishes, the user says "checkpoint" or "verify group", or between groups in a plan note.
Standalone post-implementation code review across a whole branch or PR. Goes beyond the in-cycle spec/quality reviewers (which check single prompts) to assess the diff holistically — security, correctness, perf, idioms, dead code, hidden coupling, test depth. Writes a `Code Reviews/Code Review YYYY-MM-DD HHmm.md` note to the vault linked back to the plan. Use when the user says "review my changes", "review this PR", "code review", "is this branch good", or after a plan finishes but before [[conducty-ship]].
Ingest a project directory into the Obsidian vault as a linked context sub-graph — Architecture, Conventions, Invariants, Hotspots, Tests, Glossary, plus per-bounded-context module notes. Tracks refresh deltas over time, flags stale context, and feeds prompt generation via backlinks. Use when the user says "load context", "refresh context", "ingest project", "update context for X", or provides a directory path to analyze.
Multi-persona decision analysis through structured dialectic. Six software-engineering archetypes debate a question to uncover the Design Truth. Use when the user says "analyze this decision", "dialectic", "decision analysis", "think this through", "debate this", or faces an architectural/design choice.