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 asked to migrate a JavaScript or TypeScript project from ESLint, Prettier, Standard, or mixed legacy lint configuration to Biome 2.5. Biome owns linting and formatting, legacy configuration and dependencies are removed, and the project CI check passes without auto-fix.
OutlineDriven/outline-driven-development
Skill Codex
Use when reviewing an evaluation, benchmark, or scoring harness for leakage or contamination. Returns a read-only audit naming detected leakage patterns, where independent ground truth enters or fails to enter, and a fix for each finding.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to prove coverage, find missing cases, or enumerate a state, decision, requirement, or behavior space. Enumerates every cell as covered, gap, or deferred with an executed check per cell, and emits a coverage manifest with a tally. Not for round-based questioning — use askme; not for testing one property…
OutlineDriven/outline-driven-development
Skill Codex
Use when a concept needs making clear rather than practising: explain it simply, why does this exist, draw it, what is the difference, or simplify it for a beginner. Delivers a one-screen explanation from one chosen angle, grounded in sources. Not for scaffolded practice — use drill.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to create a durable local explainer document for a concept, diff reference, idea, or work recap. Classifies the input, gathers grounding material, offers a quiz, drafts and structurally verifies the artifact in a scratch directory, and presents it. Not for one-screen explanations — use explain-concept.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to explore the codebase to map structure, symbols, and dependencies. Produces a structured orientation report with architecture, pattern, tooling, dependency, and critical-file sections.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to run a performance campaign against a measured floor: rebuild hot paths from their floor, grade cold paths, and land each target as an atomic commit with a proven win. Not for hypothesis-only analysis without mutation — use fastopt.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when someone outside Warp wants to wire a third-party coding agent (Claude Code, Codex, or Cursor) to a Warp Factory MCP endpoint. Provisions a 30-day bearer credential, writes a bearer-token MCP registration in the target harness, reloads it, and verifies protocol-level tool and resource discovery. Not for…
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants to define failure states, recovery actions, bypasses, and degraded modes for a component during design. Produces a failure-state design document mapping every bounded failure state to its recovery, bypass, or degraded mode. Not for runtime recovery.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user needs to restore service from a specific known failure by applying a single prescribed recovery operation. Verifies the symptom, validates the prescription against its authority source, records the rollback path, applies the operation, and confirms restoration via a health signal. Not for design-time…
OutlineDriven/outline-driven-development
Skill Codex needs its repo
Use when asked to test Fastify applications without network sockets: auth, validation errors, uploads, streams, plugins, hooks. Tests exercise routes via inject() with no listener. Not for building the app — use fastify-schema-first-service.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to prepare a Fastify service for production load and exposure: timeouts and payload limits, overload shedding, rate limiting, CORS and security headers, proxy safety, SIGTERM drain, and a measured performance baseline. Not for building the app; use fastify-schema-first-service.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to build or extend a Fastify application: routes, plugins, JSON Schema validation/serialization, hooks/lifecycle, decorators, content types, and database wiring. Not for testing — use fastify-inject-testing; not for hardening — use fastify-production-hardening.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants to optimize estimated hot paths and complexity-neutral cold paths while refusing complexity theater. Emits hypotheses and benchmark designs. Not for measured-floor rebuilds — use extremely-optimize; not for hypothesis-only — use fastopt.
OutlineDriven/outline-driven-development
Skill Codex
Use when a user wants to optimize suspected hot paths without waiting for benchmarks: label every cost observation as a hypothesis and emit benchmark designs, with no mutation or speed claim. Not for measured-floor rebuild campaigns — use extremely-optimize.
OutlineDriven/outline-driven-development
Skill Codex
Use when recent resolved feedback may reveal a broader recurring defect pattern: sweep resolved feedback for shared root causes, search the project surface for generalized recurrence, and verify no recurrence remains. Not for source-level feedback collection; use feedback-sweep for that.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to /feedback-sweep [setup|reconfigure] [mode:non-interactive]: sweep configured sources, acknowledge user-approved items, verify fixes merged to default, and emit an autopilot-ready plan. Not for pattern discovery — use feedback-pattern-sweep.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to design a bespoke execution workflow when no playbook fits; verify a falsifiable predicate on the real product with a reviewable trail. Don't use for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to push an already-working artifact to finished composition, texture, and feel without confusing implementation completion with composition. Not for remote, credential, publish, deploy, or irreversible changes. Not for hygiene routing — use clean-and-true.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when implementation is complete and the full test suite is green and an integration decision is needed for a development branch or worktree. Don't use for branches with failing tests or for starting new work.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user says ship it now, no phases, or finish it now, or when in-scope work would otherwise be deferred to phases, rollouts, follow-up PRs, or TODOs. Implements every in-scope path in one change. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when an authorized user needs to assess mobile-backend exposure from compiled Android APKs. Extracts backend configuration from APK carriers, probes discovered endpoints for misconfiguration under written authorization, and returns a per-APK classification with evidence and verified cleanup. Covers Firebase…
OutlineDriven/outline-driven-development
Skill Codex
Use when a first screen needs lower transfer bytes without visual or behavioral change: measure compressed bytes, reduce assets and bundles to a budget, prove pixel identity, and pass the test suite. Not for visual redesign or behavioral changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user asks to fix P0s, address critical issues, or work on priorities from the weekly product briefing. Don't use for non-P0 issues or local bug 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: