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 wants to expand a decision field with additional options and dimensions. Not for selecting or applying an option: use decide. No source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when reviewing Django or DRF access control, IDOR, authorization, permissions, or tenant isolation. Not for Django query performance: use django-perf-review. No source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when reviewing Django performance, N+1 queries, or queryset behavior. Not for authorization or IDOR review: use django-access-review. No source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when drafting a doc, proposal, spec, RFC, design doc, decision doc, or PRD in chat. Not for reviewing an existing plan: use doc-review. No source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when reviewing a prose plan, spec, PRD, requirements doc, design doc, or brainstorm, or invoking /doc-review. Not for collaborative drafting: use doc-coauthoring.
OutlineDriven/outline-driven-development
Skill Codex
Use when making an architectural decision, changing a public API, shipping a feature, or recording a codebase term. Not for domain language: use domain-modeling. Not for docs: use docs-writing.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to render documentation as an interactive, navigable HTML canvas. Not for writing or restructuring docs.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when documentation has drifted from code changes and the user asks to synchronize. Not for ADRs or architectural rationale (docs-and-adrs). Not for writing an isolated document (docs-writing).
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to write, restructure, or audit documentation with Diataxis types, or to draft a feature docs page or diagram source. Not for ADRs or architectural rationale.
OutlineDriven/outline-driven-development
Skill Codex
Use when reconciling an API endpoint's generated OpenAPI schema and declared response types with its actual runtime response. Not for general API documentation: use docs-and-adrs.
OutlineDriven/outline-driven-development
Skill Codex
Use when pinning down domain terminology, maintaining the domain model, or when a term conflicts or needs sharpening.
OutlineDriven/outline-driven-development
Skill Codex
Use when a non-trivial decision sits under uncertainty and correctness matters more than speed. Not for patch review: use review. Not for plan attacks: use load-bearing-assumption-test.
OutlineDriven/outline-driven-development
Skill Codex
Use when roadmap, plans, or docs may have drifted from code, or when restarting a stalled project. Not for PR doc sync: use docs-update.
OutlineDriven/outline-driven-development
Skill Codex
Use when a concept needs practising: the user asks for an exercise, quiz, recall, or gap probe. Not for explanations: use explain-concept.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user invokes /duet, says pair on this, or faces aesthetic, architectural, or irreversible decisions. Not for one-shot fork resolution: use decide.
OutlineDriven/outline-driven-development
Skill Codex
Use when inspecting, searching, verifying, or parsing DWARF debug info: DIEs, DWTAG/DWAT entries, .debug sections, line tables, or llvm-dwarfdump/readelf output.
OutlineDriven/outline-driven-development
Skill Codex
Use when auditing the developer-facing surface of a CLI, SDK, library, or package: API contracts, errors, public types, onboarding, and config.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user runs /embed-diagram to render a Mermaid diagram offline and embed the SVG or PNG into a target document. Uses a local CLI renderer, not a remote page. Not for code-derived diagrams. No remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when any bounded workflow starts or reaches an action, path, proposal, or merge boundary. Loads constraints before the first action, re-evaluates them at every boundary, and refuses rather than default-allow on an unreadable constraint set.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to write, review, or improve an engineering blog post, technical architecture deep dive, postmortem, or technical launch announcement. Produces evidence-grounded engineering copy with verified metrics, working code, and clear trade-off analysis.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user requests an engineering retrospective for a named period. Discovers repository and tracker telemetry, establishes source precedence, derives team breakdowns and evidence-backed habits, and writes a single report file. Not for an agent-environment retrospective — use agent-environment-retrospective…
OutlineDriven/outline-driven-development
Skill Codex
Use when the user explicitly requests a Tarot draw or casually delegates an ambiguous choice among multiple valid approaches. Runs a cryptographically random 12-house Tarot draw and interprets the spread to state one planning or investigation direction.
OutlineDriven/outline-driven-development
Skill Codex
Use when mapping state-changing external entry points in a smart-contract codebase by access level. Returns signatures, access classification, restriction evidence, and callbacks. A human-invoked entry-points command with an optional directory is a supported invocation form.
OutlineDriven/outline-driven-development
Skill Codex
Use when environment-dependent code, templates, or deployment configuration changes, or when runtime configuration is missing. Produces a bidirectionally reconciled environment-variable contract.
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: