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 create, refresh, or port a brand tone of voice guide (TONE.md) or measurable prose style rules (PROSE.md). Not for general copywriting: use copywriting.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to write or fix product/marketing copy, landing pages, UI strings, brand voice, AI tells, an end-of-article CTA, or a hook/lede. Not for whole articles: use technical-article-writer.
OutlineDriven/outline-driven-development
Skill Codex
Use when a candidate patch or answer needs independent corroboration before it is trusted. Not for multi-stance investigation: use council.
OutlineDriven/outline-driven-development
Skill Codex
Use when a measured cost surface needs one-change-at-a-time reduction under frozen guardrails. Not for speed-only optimization: use optimize.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks for a council, second opinions, or parallel investigation. Not for cross-examination of existing proposals: use cross-critique.
OutlineDriven/outline-driven-development
Skill Codex
Use when the user asks to create a new branch or start work on one. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to create a multi-session learning plan. Returns a milestoned plan, practice, and review rubric. Don't use for tasks that require source or remote-system changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when asked to create a local agent-plugin directory tree or marketplace package. Not for remote, credential, publish, deploy, or irreversible changes.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.
OutlineDriven/outline-driven-development
Skill Codex
Use when independent proposals on a contested decision need cross-critique before choosing, reusing the original authors. Not for parallel multi-stance investigation: use council.
OutlineDriven/outline-driven-development
Skill Codex
Use when one reviewer is not enough because failure modes are heterogeneous, or a claim needs cross-lens pressure before it ships. Not for collapsing a decision field: use converge.
OutlineDriven/outline-driven-development
Skill Codex
Use when a long agentic project needs each cycle to end in a learning memo and a keep/iterate/restart decision. Not for single-pass builds.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked for a sequence diagram of cryptographic protocol semantics from code, prose, RFCs, papers, ProVerif, or Tamarin, or for code/spec divergence. Not for architecture: use embed-diagram.
OutlineDriven/outline-driven-development
Skill Codex
Use when Survey and Job Culture Index profiles need analysis for stress, burnout, disengagement, or flight-risk signals. Not for clinical diagnosis: use a qualified clinician.
OutlineDriven/outline-driven-development
Skill Codex
Use when two colleagues' working friction needs trait-based explanation, accommodations, process changes, and escalation boundaries, or for manager-report friction. Not for performance adjudication.
OutlineDriven/outline-driven-development
Skill Codex
Use when a Culture Index profile needs comparison with role requirements, team composition, and manager profile for hiring. Not for transcript prediction: use culture-interview-profile-prediction.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to predict Culture Index traits from an interview transcript before a survey exists, including sparse or contradictory evidence. Not for interpreting completed survey results.
OutlineDriven/outline-driven-development
Skill Codex
Use when a manager needs profile-specific communication, one-on-one, motivation, and energy guidance for a direct report. Not for general pair or team compatibility analysis.
OutlineDriven/outline-driven-development
Skill Codex
Use when a signed new hire's Culture Index profile and team profiles need a first-90-days plan. Not for manager coaching: use culture-manager-coaching.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when customer feedback, NPS, churn, email feedback, call transcripts, or voice-of-the-customer analysis needs a report over a time window.
OutlineDriven/outline-driven-development
Skill Claude CodeCodex
Use when the user asks to cut, trigger, or start a release candidate for a release branch. Not for full releases, hotfixes, or non-release-candidate workflow dispatches.
OutlineDriven/outline-driven-development
Skill Codex
Use when the caller supplies a falsifiable out-of-happy-path invariant and a finite budget. Restores via bounded patches or reverts. Not for normal feature delivery or universal retries.
OutlineDriven/outline-driven-development
Skill Codex
Use when a build, QA pass, demo, user complaint, or abandoned attempt leaves the next pass needing lessons rather than code. Not for changelog extraction. Not for session handoff: use handoff.
OutlineDriven/outline-driven-development
Skill Codex
Use when asked to visualize data movement, ETL or ELT, lineage, transformations, custody, governance, stores, sources, or consumers.
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: