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 the user asks to simplify, clean, or refine code. Not for new abstractions or whole-codebase refactors.
OutlineDriven/outline-driven-development
Skill Codex
Use when designing or improving a module interface, locating a seam, or increasing testability; the chosen module ends up with a small interface that hides complexity and is testable through seams. Not for system-level architecture decisions — use architect.
OutlineDriven/outline-driven-development
Skill Codex
Use when building or reusing a CodeQL database, running CodeQL security analysis, or modeling project-specific sources and sinks. Not for manual vulnerability review: use confirmed-security-review.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks to clean up a finished commit message or bring it to handoff-ready form. Rewrites only messages of HEAD or a short unpushed range; the tree stays byte-identical and dates are preserved by position. Not for creating new commits — use commit.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to commit changes, create a typed branch, format history for a changelog, or rewrite messages of HEAD or an unpushed range. Not for pushing or a PR: use commit-push or commit-push-pr.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user asks to summarize competitor changelogs or analyze recent competitor releases into a deduplicated report opened as a PR. Not for researching a specific feature across competitors — use competitor-feature-research.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when asked to research a feature across competitor products or to analyze competitor release changelogs (mode: changelog), and publish a cited report.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks for direction and a compilable 3D workflow from an interview. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants to identify the true sources of complexity qualitatively before counting metrics. Not for source or remote mutation.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user explicitly asks to save, curate, or consolidate what was learned, or closes a meaningful knowledge-work session. Not for remote, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks for a security review, vulnerability audit, or review of injection, XSS, auth, or crypto. HIGH-confidence findings only. Not for CodeQL analysis: use codeql-security-analysis.
OutlineDriven/outline-driven-development
Skill Codex
Use when reviewing cryptographic code for timing side-channels, statically in compiled output or at runtime with statistical timing tests. Not for known-answer vectors: use wycheproof.
OutlineDriven/outline-driven-development
Skill Codex
Use when a cryptographic implementation must be checked at runtime for timing side-channel leakage. Runs dudect statistical testing and Timecop dynamic tracing, applies a Welch t-test threshold, and reports leakage or a bounded inconclusive result. Not for static assembly inspection — use constant-time-analysis.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to implement under non-negotiable constraints: performance budgets, platform limits, legal or API rules. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks to rank deployment platforms and stacks against their product with quantitative trade-offs. Not for source or remote mutation.
OutlineDriven/outline-driven-development
Skill Codex
Use when a long session has accumulated stale or conflicting context or the user asks to refresh it. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to mine prior chats on a scheduled or watcher tick and maintain project memory. Not for remote, credential, publish, deploy, or irreversible mutation.
OutlineDriven/outline-driven-development
Skill Codex
Use when crossing a public API boundary, guarding complex invariants, or hardening untrusted input or integration seams. Not for remote or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to reproduce, profile, or verify CLI/TUI behavior. Produces a deterministic transcript or profile proof with session cleanup. Not for CLI design advice, use cli-for-agents.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to verify or reproduce browser or Electron UI behavior with before-and-after evidence and no leftover processes. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user wants to collapse an open decision field to one decision and record its rationale locally. Not for multi-lens pressure testing. No remote or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user asks to design or review a bottom-of-article call-to-action. Maps article context, audience, and funnel stage to a CTA archetype with copy, form, mechanism, A/B test plan, and accessibility check. For general copywriting use copywriting; for hooks or ledes use copywriting-hooks.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user asks for a hook, lede, or accroche for long-form content. Not for CTA design, use copywriting-cta; not for general copywriting, use copywriting.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to codify, audit, or port measurable prose style rules (syntax, rhythm, mechanics) into a versioned PROSE.md, separate from emotional tone. Not for tone-of-voice guides — use copywriting-tone-of-voice-creator; not for general copywriting — use copywriting.
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: