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 Codex
Use when a human-curated dbt model index must guide BigQuery SQL for a warehouse question. Not for discovering undocumented models or executing warehouse changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user asks to tighten verbose-but-correct prose without a full rewrite. Cuts in place to load-bearing density, preserving every load-bearing claim.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user has a fork and wants it resolved and applied, not explored: "decide this", "choose the path", or "decide and fix it".
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants to record why one world won over the others, as a decision-diary entry. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when a current decision needs pressure-testing until the rationale is clear to a skeptic. Not for tasks requiring source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when asked to deduplicate a skill tree, fold overlapping skills, or cut the skill count: analyze, gate per family, then fold. Not for prompt-doctrine cascades: use cascade-dedup.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks to research a topic and produce a thorough sourced report. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user wants the finished-system contract for a piece of work: behavior, protocols, allowed, forbidden, and impossible states with a state-space proof. Not for runtime verification.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to remove old code, migrate consumers, or decide whether to maintain or sunset a system. Not for untracked data or changes without VCS rollback.
OutlineDriven/outline-driven-development
Skill Codex
Use when dependency upgrades need batching for CVEs, a major release, forced compatibility, a scheduled or vulnerability-triggered sweep. Not for PR queue triage: use github-backlog-triage.
OutlineDriven/outline-driven-development
Skill Codex
Use when /design-consultation proposes a design system with mockups or HTML and persists the approved system in DESIGN.md. Not for in-chat direction picking — use design. No remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when creative work is requested with no approved design, or a raw idea or repository must be developed into an approved design document. Not for work with an approved design in context.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to design a module interface, seam, or testable boundary. Not for UI direction picking: use design. No source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when /design-variants generates distinct design directions and a gallery for selection. Not for one polished artifact: use polished-web-prototype. Not for token-system picking: use design.
OutlineDriven/outline-driven-development
Skill Codex
Use when starting UI work, defining palettes or tokens, fixing AI-generic UI, or persisting a design system to DESIGN.md (modes: implement, persist). Not for live URLs: use web-design-review.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user says deslop, debloat, tidy, simplify, clean a diff, or deslop branch diff, or remove dead code or config. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when adding a devcontainer or isolated dev environment to a repo that lacks one, for Python, Node/TypeScript, Rust, Go, or a combination. Not for editing an existing devcontainer.
OutlineDriven/outline-driven-development
Skill Codex
Use when dogfooding a developer-facing product or workflow to produce an evidence-backed DX scorecard. Not for visual UI audit: use web-design-review.
OutlineDriven/outline-driven-development
Skill Codex
Use when a configured loop misbehaves, produces unexpected results, or its setup soundness is questioned. Not for tasks that require source or remote-system changes, not for loop design.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked for a call graph, class hierarchy, dependency map, containment or complexity view, or data-flow view. Not for embedding: use embed-diagram. Not for architecture: use visual-diagram.
OutlineDriven/outline-driven-development
Skill Codex
Use when one issue or PR is too large for a worker and partitions into disjoint write sets. Not for independent parallel tasks: use parallel-launch. No remote or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to run branch-diff browser QA against a PR or branch. Not for live-URL visual audit: use web-design-review. No remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when given a PR, commit, diff, or baseline and asked for security regressions, blast radius, test gaps, or adversarial review. Risk-classifies changes and writes an evidence-backed report. Not for whole-codebase audit — use security-review. No remote or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when code mixes units, fixed-point precisions, scaling factors, rates, prices, shares, or conversions. Not for type-level unit modeling: use type-driven.
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: