Outline-Driven Development - opinionated methodology between vibes and specs. AST tooling + context engineering + loop engineering on your hands. Plugins for Claude / Codex / Gemini / Cursor.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when asked to create or refresh a personal mode skill and open a reviewable PR. Not for shared repo skills or work that skips human approval.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user wants a cybernetic flow design document for an interactive system. Not for implementing or deploying the system.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants a looser conceptual graph for exploratory work. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when a human has an approved delivery plan and wants the full chain run under phase gates. Not for planning, open-ended debugging, or single-step execution: use work directly.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user runs /autoplan on a plan or idea. Reviews, amends, and derives task IDs with a final human approval gate. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user says release this, publish this package, or cut a release for a changesets-based npm package. Not for non-npm packages or releases without a changesets workflow.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to audit an agent or AI feature for agentic-experience quality (AX review, agent-native critique, trust question). Not for source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user requests axiom, axiom-mode, axiom-compact, formal-logic, or compact form. Not for changing code or remote state.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user faces multi-fork decisions or unresolved prerequisites. Maps a decision tree and asks its frontier as batched single-select questions until shared understanding is confirmed. Also handles "batch questions". Not for one-at-a-time interviews — use interview-me.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to validate a web app, CLI, API, or generated artifact against a source-blind behavior contract. Not for source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to determine what a change could break before it ships. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user names one book, course, paper, or source document and asks to distill it into a reusable skill. Not for a folder of sources: use map-corpus.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user begins knowledge work with notes, a transcript, or a brain dump, asks for divergent ideas (mode: ideate), or wants options shown in a local browser (mode: visual).
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks for branded or style-governed output. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when bloated code needs clean re-derivation, or the user says "this module is bloated" or "break it and rebuild". Not for untracked data or changes without VCS rollback.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user runs /browser-cookie-store to populate the session cookie store from installed browsers. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user runs /browser-qa for report-only QA results without entering a fix loop. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when building, debugging, or verifying browser-rendered code, or running browser tests for PR- or branch-affected pages. Not for source, remote-system, credential, publish, or deploy changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when a multi-language program graph is needed for call paths, entrypoints, blast radius, or taint reachability. Not for overview (trailmark-structural) or snapshot (trailmark-structural).
OutlineDriven/outline-driven-development
Skill Codex
Use when a human invokes the Burp search command with a required .burp project file and optional parser operation. Runs the Burp Suite project parser wrapper and returns JSON search results. Not for source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to analyze a Burp Suite .burp project for audit items, request/response metadata, or captured traffic. Modes: parsed (default) and stream. Not for source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when product copy needs buyer-objection evidence collected through approved, consented outreach. Not for unsolicited outreach or survey design.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user wants the current jargon weather of a domain described without advocacy. Not for choosing a positioning move: use buzzword-hijack.
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: