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 user wants to choose and execute a bounded positioning move that rides a jargon wave. Not for describing the jargon weather of a domain: use buzzword-analysis.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user requests a userspace C or C++ security review with a threat model and severity filter and wants validated findings. Not for kernel or bare-metal code: use kernel-security.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks "where to help", "contribution opportunities", or "find a good first issue". Returns data-backed first steps. Not for PR review queues: use gh-review-requests.
OutlineDriven/outline-driven-development
Skill Codex
Use when the learner is ready to apply cleared concepts in a real project. Not for exercises or quizzes: use drill.
OutlineDriven/outline-driven-development
Skill Codex
Use when a candidate change must be produced without touching the working tree. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when initializing, running, measuring coverage, or triaging a cargo-fuzz target in a Rust crate. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when prompt-doctrine is duplicated, drifted, or conflicting across output-style embeds and external harness AGENTS files. Not for editing the canonical baseline itself.
OutlineDriven/outline-driven-development
Skill Codex
Use when the human returns after a gap, cannot follow the project, asks what happened, or wants a visual HTML recap page. Not for onboarding: use onboard. Not for handoff: use handoff.
OutlineDriven/outline-driven-development
Skill Codex
Use when an Algorand, Cairo, Cosmos SDK, Solana, Substrate, or TON codebase needs vulnerability scanning with reachability-backed findings. Not for non-chain review: use security-review.
OutlineDriven/outline-driven-development
Skill Codex
Use when a release or a since-tag window needs user-facing release notes drafted. Not for publishing the release.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when a human explicitly asks for a full repository agent-compatibility pass returning a scored report with prioritized fixes. Not for tasks that require source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user asks to cherry-pick, backport, or apply a hotfix to a release branch. Not for merging feature branches or cutting new release branches.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user explicitly asks to build, modify, or publish a Manifest V3 Chrome extension. Not for store submission without human-gated credentials.
OutlineDriven/outline-driven-development
Skill Codex
Use when setting up or modifying CI/CD pipelines, quality gates, test runners, or deployment pipeline configuration through workflow files. Not for triggering a deployment.
OutlineDriven/outline-driven-development
Skill Codex
Use when "CI is red", "fix the checks", or "make CI green", one check needs classifying, or a bounded sweep runs. Not for deploys, credentials, or rerun-as-fix. Non-CI bugs: use strike-the-root.
OutlineDriven/outline-driven-development
Skill Codex
Use when a requested sweep monitors CI failures over a bounded attempt window. Returns each root cause reproduced or classified non-actionable with any minimal verified patch as a proposal. Not for classifying one failure without patching — use classify-ci-failure.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user says "clarify", "what is ambiguous here", or when a prompt or spec reads as under-specified before planning. Surfaces ambiguities as a certainty-tiered findings report with recommended defaults. Not for exploring intent with questions — use askme.
OutlineDriven/outline-driven-development
Skill Codex
Use when a CI check is failed, absent, pending too long, unstable, or reported unexpectedly. Classify it into a deterministic failure class with the next owner, then emit a reviewable fix plan, without patching. Not for sweeping and patching — use ci-sweeper.
OutlineDriven/outline-driven-development
Skill Codex
Use when setting up a project, auditing agent command permissions, or asking which read-only bash commands and domains to allow. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user just edited a durable artifact, or says \"clean and true\", \"run the hygiene pass\", or \"taste the output\". Routes the artifact through the hygiene passes it earned.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when asked to run /clean-clean-cut to cut accumulated records and residue. Not for untracked or non-VCS changes, or branch/worktree cleanup: use git-cleanup.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to build or review a CLI intended for coding agents and return flag-driven, pipeline-safe, idempotent design advice. Not for running or profiling a CLI: use control-cli.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user wants to batch-close resolved or outdated tracker items. The agent never closes tracker items itself. Not for individual closure or items still under active work.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when a human explicitly runs /cloud-task-orchestrator for a large task across cloud agents to drain a verified task graph. Not for local subagent coordination: use orchestration-patterns.
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: