Audit a repository's control-plane health and produce an actionable improvement report. Use when the user asks to "audit the repo", "check repo health", "assess control plane", "entropy audit for the control system", "check what's missing for agents", or wants to know what's missing in their instruction files, rules, and verification infrastructure. Do NOT use for code review (use review), dependency audit (use dependency-audit), general documentation work (use project-documentation), or reviewing a specific PR or diff (use review or entropy-review).
2026-05-24
Review code changes for entropy introduction: naming drift, error-model splits, dependency violations, doc staleness, and pattern duplication. Activate when the user asks for "entropy review", "consistency check", "drift check on this PR", "check if this change introduces new patterns", or wants a review focused on naming, error handling, or structural consistency rather than correctness. Do NOT activate for general code review (use review), full repo audit (use repo-entropy-audit), control-plane audit (use control-plane-auditor), brainstorming, or implementation tasks.
2026-05-24
Full-repository entropy scan across six axes: structure (dependency graph, layering, SCC), semantics (naming diversity, state model fragmentation), behavior (error model variants, boundary handling), context (doc freshness, instruction-file coverage), protocol (instruction-file consistency), and control (rule enforcement gaps). Produces a module-level heatmap, trend comparison, and prioritized cleanup targets. Activate when the user asks for "entropy audit", "repo health scan", "heatmap", "tech debt scan", or "full entropy report". Do NOT use for PR-level review (use entropy-review) or control-plane audit (use control-plane-auditor).
2026-05-24
REQUIRED for Claude Code or Codex CLI hook queries — has accurate cross-platform reference. Triggers on PreToolUse, PostToolUse, Stop, SessionStart hooks, .claude/settings.json or .codex/hooks.json config, prompt vs command hook types, hooks not firing, exit codes, stdin JSON, matchers, path blocking, or dual-platform hook setups. Skip for React hooks, webhooks, GitHub Actions.
2026-05-22
Analyze a coding project and design a tailored AI development environment: recommend agents, skills, instruction files, MCP servers, and workflow composition across Claude Code and Codex. Also audit an existing AI setup for gaps, overlap, or bloat. Use when setting up, overhauling, or auditing a project's AI tooling as a whole, not for individual agent edits or skill management.
2026-03-31
Manage the lifecycle of sub-agents: create or update agent packages, validate cross-surface agent contracts, evaluate routing behavior, tighten invocation boundaries, tune Codex runtime defaults, install or publish agents, or audit an agent library. Use only when the request is explicitly about agents or agent libraries, not for ordinary coding, implementation, or general project planning.
2026-03-31
Issue Agent OS controller loop. Pulls issues from a GitHub issue queue (priority + dependency resolved), fans out triage to parallel triager agents, dispatches coder / reviewer / splitter / planner / debugger workers based on verdicts, drives review loops, merges approved PRs, and repeats until the queue is empty. Use when the user asks to "process issues", "run the issue controller", "work through the queue", or similar. Do NOT use for single-issue ad-hoc work — this is the full automated loop.
2026-03-30
Manual-first workflow for designing, building, evaluating, and upgrading real agentic systems. Use when the job involves tool-using agents, agent orchestration, agent runtimes or platforms, multi-agent systems, framework selection, evals, or guardrails; do not use for prompt-only work or ordinary implementation planning.
2026-03-30