Outline-Driven Development - opinionated methodology between vibes and specs. AST tooling + context engineering + loop engineering on your hands. Plugins for Claude / Codex / Gemini / Cursor.
Use when the user wants to classify abstractions as useful, bad, or busy and keep one shallow level. Classifies each by whether its cooked form is easier than its raw form, and selects one shallow level. Don't use for tasks that require source or remote-system changes.
Use when building or running native code under AddressSanitizer, or when interpreting an existing ASan report. Instruments C/C++ or Rust unsafe/FFI targets, sets ASANOPTIONS for fuzzer integration, and classifies each reported error with its faulting and allocation sites. Not for remote, credential, publish, deploy…
Use when the user needs to set up and run an AFL++ fuzzing campaign for a C/C++ target. Compiles with LTO, LLVM, or GCC instrumentation, runs single or multi-core campaigns, triages crashes, and minimizes the corpus. Requests explicit approval before system-level changes. Not for libFuzzer harness campaigns — use…
Use when a completed session needs an agent-environment retrospective: a severity-ranked list of environment improvement candidates, each backed by session evidence. Not for an engineering retrospective from telemetry — use engineering-retrospective.
Use when the user asks to audit or repair agent surfaces — plugin configs, agent definitions, skills, CLAUDE.md/AGENTS.md, docs, prompts, commands, or hooks. Produces a certainty-graded breadth report and applies only HIGH auto-fixable findings with --apply. Not for deep one-skill improvement — use skill-improver.
Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body with human approval and preview. Not for automated or model-initiated insertion without explicit human review.
Use when setting up a repo for agents, adding AGENTS.md, auditing CLAUDE.md, scoring instructions, or pruning long/stale files via a three-check gate. Also handles lean pointer-only AGENTS.md under 100 lines. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user describes an AI workflow gap or uses an ambiguous cross-session reference such as 'the PR Bob mentioned'. Resolves each to a stable handle and surfaces collaboration anti-patterns when reached. Don't use for tasks that require source or remote-system changes.
Use when a user wants to enumerate plausible designs, configurations, scenarios, and paths and diagram the field before choosing. Produces an exhaustive enumerated field and a diagram before any choice. Don't use for remote, credential, publish, deploy, or irreversible changes.
Use when the user requests a deep dive, exploratory analysis, or data analysis on BigQuery. Produces a dated analyses dir with an approved plan, cohorts, linked SQL and visualization artifacts, and TLDR. Read-only BigQuery warehouse queries are within authority; not for credential, publish, deploy, or irreversible…
Use when asked to design or change a public API, route, CLI flag, or module boundary. It documents the contract with semantics and errors, then migrates every consumer so no legacy path remains. Don't use for remote, credential, publish, deploy, or irreversible changes.
Use when a completed agent run must be recorded as durable, queryable evidence. Appends one entry to the JSONL run log under an ISO date guard, prunes expired entries, and updates the last-run pointer. Don't use for remote, credential, publish, deploy, or irreversible changes.
Use when non-trivial code needs designing before implementation, or an existing codebase needs its architecture improved: surveying for shallow modules, locating a seam, deepening a structure, hardening with guardrails, or making code testable. Also handles surveying for shallow modules, locating seams, deepening…
Use when the user asks to visualize an architecture as a self-contained HTML artifact with a hash-bound receipt. Also handles delta mode: comparing two snapshots, rendering what changed when both are supplied. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user knows what they mean but cannot express it completely or clearly. Turns a vague intended thought into a faithful, audience-ready statement, preserving scope and identity, surfacing unsupported choices, and inventing no goals or facts. Not for discovery, ideation, or style-only editing — use unslop…
Use when asked to run /artifact-arena to generate and judge competing artifact implementations. Produce one verified synthesis with provenance and rejection reasons. Don't use for remote, credential, publish, deploy, or irreversible changes.
Use when a task is ambiguous, maximum clarification is needed before planning, or the user requests exhaustive, collaborative, or adversarial askme mode. Runs Verbalized Sampling, fires batched clarifying questions, and confirms intent before planning proceeds. Not for source or remote-system changes; not for a single…
Use when asked to run AST-based structural search, lint, or rewrite of code when regex is too fragile. Pattern is validated, blast radius reviewed, and rewrite landed at the correct scope. Don't use for remote, credential, publish, deploy, or irreversible changes.
Use when a user needs coverage-guided fuzzing for Python code or a Python native extension using Atheris. Sets up an instrumented harness, configures sanitizer flags for native extensions, and reproduces saved crash artifacts. Not for remote, credential, publish, deploy, or irreversible changes.
Use when a user wants adversarial stress-testing of a proposed architecture, structure, or shape. The agent attacks while the human defends, or the agent proposes while the human attacks, until the shape survives or breaks. Records the surviving shape as a decision. Not for tasks that require source or remote-system…
Use when loop scaffold files have drifted from their provenance-pinned templates. Converges exactly four auto-fixable files (STATE.md, gate.yaml, loop-budget.md, loop-run-log.md) to template content with pre-write backup and rollback, and reports other drift. Not for remote, credential, publish, deploy, or…
Use when the user says "audit my code", "find all the bugs", "review until clean", or "grill my changes". Runs an iterative multi-agent review that resolves every finding at or above a configurable severity floor to zero, or stops at a gate or cap. Not for remote, credential, or irreversible changes.
Use when a verified non-trivial fix lands. Automatically captures a durable learning doc to docs/solutions/ or a CONCEPTS.md entry, or determines nothing qualifies. Also handles refresh when solution docs may have drifted. Not for unverified fixes.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: