OutlineDriven/outline-driven-development
Skill Codex
Use when the user wants to classify abstractions as useful, bad, or busy and keep one shallow level. Not for tasks requiring source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when building or running native code under AddressSanitizer, interpreting an existing ASan report, or debugging a memory-corruption failure. Not for remote or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
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…
OutlineDriven/outline-driven-development
Skill Codex
Use when a completed session needs an agent-environment retrospective. Not for an engineering retrospective from telemetry: use engineering-retrospective.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to audit or repair agent surfaces (plugins, agents, skills, CLAUDE.md/AGENTS.md, docs, prompts, commands, hooks) or improve one skill at depth. Not for agent grading: use skill-doctor.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
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.
OutlineDriven/outline-driven-development
Skill Codex
Use when a repo needs agent setup, AGENTS.md added or made lean, CLAUDE.md audited, or agent instructions scored or pruned. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user describes an AI workflow gap or uses an ambiguous cross-session reference such as 'the PR Bob mentioned'. Not for tasks that require source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants to enumerate plausible designs, configurations, scenarios, and paths and diagram the field before choosing. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user requests a deep dive, exploratory analysis, or data analysis on BigQuery. Not for credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to design or change a public API, route, CLI flag, or module boundary. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when a completed agent run must be recorded as durable, queryable evidence. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when non-trivial code needs a design, codebase design or architecture needs improving, or one module needs targeted interface narrowing, seams, or testability. Not for diagrams, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks to visualize an architecture as a self-contained HTML artifact, or compare two architecture snapshots. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user knows what they mean but cannot express it completely or clearly. Not for discovery, ideation, or style-only editing: use unslop for style.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when asked to run /artifact-arena to generate and judge competing artifact implementations. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when eliciting intent/scope/referents or gating long/bundled/high-stakes/hard-to-undo work: exhaustive/collaborative/adversarial/gate/batch/interview/scan/proposal. Not for one fork: use decide.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to run AST-based structural search, lint, or rewrite of code when regex is too fragile. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when a user needs to run coverage-guided fuzzing with Atheris against Python code or a Python native extension. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user wants adversarial stress-testing of a proposed architecture, structure, or shape. Not for tasks that require source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when loop scaffold files have drifted from their provenance-pinned templates. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user says "audit my code", "find all the bugs", "review until clean", or "grill my changes". Not for remote, credential, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when a verified non-trivial fix lands or existing solution docs need refresh. 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: