OutlineDriven
OrganizationOutline-Driven Development - opinionated methodology between vibes and specs. AST tooling + context engineering + loop engineering on your hands. Plugins for Claude / Codex / Gemini / Cursor.
Categories
Indexed Skills (208)
browser-cookie-store
Use when the user runs /browser-cookie-store to populate the session cookie store from installed browsers. Not for remote, credential, publish, deploy, or irreversible changes.
analysis-artifacts
Use when the user requests a deep dive, exploratory analysis, or data analysis on BigQuery. Not for credential, publish, deploy, or irreversible changes.
append-run-log
Use when a completed agent run must be recorded as durable, queryable evidence. Not for remote, credential, publish, deploy, or irreversible changes.
articulate
Use when the user knows what they mean but cannot express it completely or clearly. Not for discovery, ideation, or style-only editing: use unslop for style.
artifact-arena
Use when asked to run /artifact-arena to generate and judge competing artifact implementations. Not for remote, credential, publish, deploy, or irreversible changes.
atheris
Use when a user needs coverage-guided fuzzing for Python code or a Python native extension using Atheris. Not for remote, credential, publish, deploy, or irreversible changes.
automatic-cybernetic-flow-design
Use when the user wants a cybernetic flow design document for an interactive system. Not for implementing or deploying the system.
backlog
Use when asked to park an undecided idea without representing it as decided or active work. Not for decided or active work: use the project task system.
behavior-validator
Use when asked to validate a web app, CLI, API, or generated artifact against a source-blind behavior contract. Not for source or remote-system changes.
blast-radius
Use when asked to determine what a change could break before it ships. Not for remote, credential, publish, deploy, or irreversible changes.
brand-authority
Use when the user asks for branded or style-governed output. Not for remote, credential, publish, deploy, or irreversible changes.
adc-dac-baremetal
Use when configuring ADC sampling time, DMA-driven ADC, calibration, or DAC channel setup on bare-metal MCUs. Not for the DMA stream itself: use dma-baremetal.
apple-silicon
Use when tuning or profiling native code on Apple M-series Macs: unified memory, 16 KiB pages, Accelerate and Metal for matrix work, xctrace and leaks, Rosetta 2, or sysctl hardware queries.
arm-sve
Use when writing or porting AArch64 SIMD to SVE or SVE2: arm_sve.h intrinsics, predicates, vector-length-agnostic loops, auto-vectorization, or SVE registers in GDB. Not for NEON: use simd-intrinsics.
bazel
Use when writing Bazel BUILD files with cc_library or cc_binary rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox debugging, or bazel query and cquery graphs.
bounded-model-checking-c
Use when C or C++ code needs memory-safety or undefined-behavior guarantees proved with CBMC, or ACSL contracts checked with Frama-C Eva or WP. Not for choosing the proof policy: use proof-driven.
agent-transcript
Use when a redacted, trimmed agent transcript must be appended to a GitHub PR or issue body, with human approval and preview. Not for automated or model-initiated insertion.
autoship
Use when the user says release this, publish this package, or cut a release for a changesets-based npm package. Not for non-npm packages or releases without a changesets workflow.
ai-collab-protocols
Use when the user describes an AI workflow gap or uses an ambiguous cross-session reference such as 'the PR Bob mentioned'. Not for tasks that require source or remote-system changes.
ax-audit
Use when asked to audit an agent or AI feature for agentic-experience quality (AX review, agent-native critique, trust question). Not for source or remote-system changes.
axiom-mode
Use when the user requests axiom, axiom-mode, axiom-compact, formal-logic, or compact form. Not for changing code or remote state.
book-to-skill
Use when the user names one book, course, paper, or source document and asks to distill it into a reusable skill. Not for a folder of sources: use map-corpus.
atomic-issues-prs
Use when the user says "atomic PRs" or requests one issue or PR per logical change. Don't use for single-change pushes or uncommitted change-sets.
automate-me
Use when asked to create or refresh a personal mode skill and open a reviewable PR. Not for shared repo skills or work that skips human approval.
autopilot
Use when a human has an approved delivery plan and wants the full chain run under phase gates. Not for planning, open-ended debugging, or single-step execution: use work directly.
autopilot
Run a hands-off plan-to-ship pipeline by chaining existing skills. Use when the user says "autopilot", "take this from plan to shipped", "run the whole pipeline", "hands-off ship it", or "do the end-to-end build".
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
fix
Use when the user says "fix", "make it pass", or "apply the findings", or hands a verifier failure or bug description.
gh-fix-ci
Use when the user asks to debug or fix failing CI checks on a GitHub pull request.
ideate
Generate grounded, divergent ideas from the codebase. Use when the user says "let's brainstorm", "what should we build", or "any ideas for".
cascade-dedup
Use when prompt-doctrine is duplicated, drifted, or conflicting across output-style embeds and external harness AGENTS files. Strips duplicate directives from persona prefixes, repairs invariant-zone tail drift, classifies harness divergences, and records a divergence ledger before committing. Not for editing the canonical baseline itself.
improve-architecture
Surface deepening refactors that turn shallow modules into deep ones, raising testability and agent-navigability.
compound
Use when a verified non-trivial outcome should be written up as a docs/solutions/ entry or a CONCEPTS.md term, and the user asks for it explicitly. Fires only on request; for automatic capture after a verified fix, use autolearn.
can-i-help
Route contributors to data-backed contribution opportunities. Use when the user asks "where can I help", "what can I contribute", "find a good first issue", or "what should I work on".
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
enhance
Audit and tighten agent/plugin surfaces. Use when the user asks to enhance a plugin config, agent definition, skill, or CLAUDE.md.
handoff
Snapshot the current session into a resumable handoff artifact so a cold session, agent, or person continues without replaying context. Use when the user says "write a handoff", "hand off", "snapshot this session", "I'm running low on context", "pause and pack this up for the next session", or "resume this later".
loop-me
Use when the user wants to design a recurring personal or team workflow: capture loops, write specs in workflows/*.md, and run a stateful askme session until the spec is implementer-ready. Triggers: "loop me", "design a workflow", "automate this recurring task", morning routine, inbox processing.
diagram-contract
Use when a diagram is going into a document: pick the tool, write the text source, render it, and embed it with an accessible caption. Text DSL plus a committed SVG is the shape — nomnoml for structure and flow, D2 for architecture, the house palette on both.
drill
Use when a concept needs practising rather than explaining: run a scaffolded exercise from worked example to independent problem, quiz the learner, run spaced recall over what they cleared, or probe for the gaps blocking what they want next. For explanation, use explain-concept; for an end-to-end build, use capstone.
explain-concept
Use when a concept needs making clear rather than practising: build the intuition, explain why it exists and what it replaced, trace where it came from, draw it, or contrast it against what it gets confused with. For exercises and grading, use drill.
decide
Use when the user has a fork and wants it resolved and applied, not explored: "help me decide", "just decide this", "what should I do here", "decide and fix it". Frames each fork as one single-select with a recommended default, takes the pick, and applies it. Requirement exploration that ends in a document goes to askme; a verdict on adopting a technology goes to pov.
check-agent-compatibility
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.
claude-settings-audit
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.
harness-port-guide
Use when the user asks to make the skills framework work in a new harness, IDE, or CLI. Not for remote, credential, publish, deploy, or irreversible changes.
mcp-builder
Use when asked to create an MCP server to integrate an API or service in Python or TypeScript. Not for remote, credential, publish, deploy, or irreversible changes.
prohibit-bad-habits
Use when a user wants to define patterns the agent should not do. Don't use for remote, credential, publish, deploy, or irreversible changes.
multi-agent-tournament-scorecard
Use when agent strategies need a reproducible finite tournament under a frozen evaluation protocol. Not for open-ended or infinite matchups: use a continuous benchmark.
xcode-simulator-testing
Use when asked to run /xcode-simulator-testing with a scheme name or current to build and launch an iOS app in a simulator. Not for project regeneration: use ios-build-fix.
document-api-endpoint
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.
principles
Use when a request names a working principle (subtract before you add, idempotent operations, never block on the human) or asks which principle applies. Not for running a repair: use strike-the-root.
universal-invariant-baseline
Use when invoked to apply an invariant-first, fail-fast, special-case-eliminating baseline. Not for domain models in types: use type-driven. Not for design-by-contract: use contract-driven.
factory-mcp-bootstrap
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 unattended runs; credential minting requires explicit human invocation.
lockstep-version-guard
Use when a human invokes the release gate to prove all 28 ODIN plugins share one canonical version. Emits a per-file comparison and exits non-zero on mismatch. Don't use to edit release metadata or for remote, credential, publish, deploy, or irreversible changes.
reflect
Use when a completed task needs reflection on the invoked skills to propose and apply approved improvements, with explicit human approval before any edit. Not for remote, credential, publish, deploy, or irreversible changes.
setup-benny
Use when installing a third-party automation pack or template repository safely and deterministically. Fetches the source archive, verifies every file against an expected manifest of hashes, applies required transformations using strict unique anchors, checks for destination conflicts, and atomically moves files to the target with a saved rollback manifest. Not for unattended runs; requires explicit human invocation.
setup
Use when the user asks to set up the agent environment. Covers credentials, placeholders, tool access checks, a uv venv, a pack install, or a role-model mapping file. Not for unattended runs.
skill-benchmark-gate
Use when a skill change is about to ship and must pass a release gate. Validates gate inputs fail-closed, runs activation and regression cases against an explicit baseline, measures context cost against an explicit ceiling, and emits PASS or FAIL with one issue per failure. Not for scoring without gating — use skill-benchmark.
skill-benchmark
Use when the user runs /skill-benchmark to score agent skills via LLM judges with baseline comparison, regression detection, and trend analysis, or to compare candidate models on a shared task set in a ranked table with per-model spend tracking. Not for release gating — use skill-benchmark-gate.
workspace-unfreeze
Use when the user runs /workspace-unfreeze on a frozen path to make it editable again. Not for automated or unattended runs: requires explicit human invocation.
ios-build-cleanup
Use when the user wants a clean Xcode rebuild by deleting DerivedData and build artifacts. Do not use for diagnosing a specific build error: use ios-build-fix.
clean-clean-cut
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.
fromzero
Use when replacing a greenfield attempt with a clean pad of verified requirements. Not for rebuilding from primitives: use from-first-principle. Requires a committed, VCS-recoverable attempt.
refactor-break-compat
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly. Not for additive refactors that must preserve the old path.
reproduce-and-fix-issues
Use when a trusted bug or performance report needs reproduction and fix. Not for untrusted reports or scope beyond the named feature.
autolearn
Compound a solved problem into a durable in-repo learning doc. Use when a verified non-trivial fix lands, the user says "compound this", "document this fix", or "remember this". This is the automatic-capture entry point; for an explicitly requested one-off write-up, use compound.
atomic-issues-prs
Publish a change-set as atomic GitHub issues or PRs. Use when the user says "atomic PRs" or wants one issue/PR per logical change.
ai-collab-protocols
Surface in-task AI collaboration protocols one tactic at a time, replacing ambiguous references with durable, recoverable handles.
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or platform. For that verdict, use pov. For divergent option generation rather than scoping one idea, use ideate.
af-xdp
Use when creating AF_XDP sockets, configuring UMEM and XSK rings, writing an XDP redirect program, or choosing copy versus zero-copy mode. Not for full kernel bypass: use dpdk.
branch-prediction-and-speculation
Use when explaining branch predictors, mispredict penalties, speculative execution, Spectre or Meltdown mitigations, or branchless code. Not for pipeline stage theory: use cpu-pipelines-and-hazards.
abstract-well
Use when the user wants to classify abstractions as useful, bad, or busy and keep one shallow level. Not for tasks requiring source or remote-system changes.
address-sanitizer
Use when building or running native code under AddressSanitizer, interpreting an existing ASan report, or debugging a memory-corruption failure. Not for remote or irreversible changes.
aflpp
Use when the user needs to set up and run an AFL++ fuzzing campaign for a C/C++ target. Compiles with LTO, LLVM, or GCC instrumentation, runs single or multi-core campaigns, triages crashes, and minimizes the corpus. Requests explicit approval before system-level changes. Not for libFuzzer harness campaigns — use libfuzzer.
all-scenarios-storm
Use when a user wants to enumerate plausible designs, configurations, scenarios, and paths and diagram the field before choosing. Not for remote, credential, publish, deploy, or irreversible changes.
architecture-diagram
Use when the user asks to visualize an architecture as a self-contained HTML artifact, or compare two architecture snapshots. Not for remote, credential, publish, deploy, or irreversible changes.
attack-shape
Use when the user wants adversarial stress-testing of a proposed architecture, structure, or shape. Not for tasks that require source or remote-system changes.
automatic-freeform-graphs-design
Use when a user wants a looser conceptual graph for exploratory work. Not for remote, credential, publish, deploy, or irreversible changes.
autoplan
Use when the user runs /autoplan on a plan or idea. Reviews, amends, and derives task IDs with a final human approval gate. Not for remote, credential, publish, deploy, or irreversible changes.
browser-qa
Use when the user runs /browser-qa to run the QA verification pass and return report-only results without entering a fix loop. Runs configured build, test, and lint checks in order, collects findings, and writes one local report. Not for remote, credential, publish, deploy, or irreversible changes.
build-program-graph
Use when a multi-language program graph is needed for call paths, entrypoints, blast radius, coarse taint reachability, privilege boundaries, or declared cross-system links. Builds the full graph, runs preanalysis, and gates every version-specific query behind a capability probe with bounded security claims. Not for a quick overview; use trailmark-summary. Not for a fixed snapshot payload; use trailmark-structural.
burp-search-command
Use when a human invokes the Burp search command with a required .burp project file and optional parser operation. Runs the Burp Suite project parser wrapper and returns JSON search results. Not for source or remote-system changes.
burpsuite-project-parser
Use when asked to search or analyze a Burp Suite .burp project to extract audit items, inspect request or response metadata, or search captured traffic. Reads through Burp Suite Professional headless JAR, preflights result size, and returns size-checked JSON with truncated body fields. Findings are indicators requiring validation.
buyer-objection-research
Use when product copy needs buyer-objection evidence collected through approved outreach. Conducts structured interviews via approved channels with consent, then synthesizes a copy recommendation grounded in anonymized exact language. Not for unsolicited outreach or survey design.
buzzword-analysis
Use when the user wants the current jargon weather of a domain described without advocacy. Surveys circulating terms, their signaling freight, and their usage trajectory from verifiable external sources. Not for choosing a positioning move — use buzzword-hijack.
buzzword-hijack
Use when a user wants to choose and execute a bounded positioning move that rides a jargon wave without confusing trend with truth. Produces a written positioning artifact at a named output path. Not for describing the jargon landscape.
c-security-review
Use when the user requests a userspace C or C++ security review with an explicit threat model, severity filter, and model. Runs a partitioned read-only audit and writes report, SARIF, and findings to a .c-review-results run directory. Not for kernel drivers, managed languages, or embedded code.
abi-and-calling-conventions
Use when explaining System V AMD64, ARM AAPCS, RISC-V psABI, stack frames, variadic calls, or FFI register rules. Not for the Rust FFI binding layer: use rust-ffi.
assembly-arm
Use when reading or writing AArch64 or AArch32 Thumb assembly, inline asm in C, AAPCS64 register roles, or NEON and SVE vector code. Not for ABI detail across ISAs: use abi-and-calling-conventions.
assembly-riscv
Use when reading or writing RV32/RV64 assembly, inline asm in C, the RISC-V psABI, IMAFD extension naming, compressed instructions, or QEMU RISC-V debugging.
assembly-x86
Use when reading GCC or Clang x86-64 assembly, writing inline asm, decoding AT&T syntax, or applying System V AMD64 register rules. Not for SIMD intrinsic selection: use simd-intrinsics.
baremetal-startup
Use when writing reset-to-main startup code, vector tables, VTOR, .data/.bss init, stack setup, startup.s, or crt0 for Cortex-M/RISC-V. Not for the bootloader jump: use bootloaders-embedded.
binary-hardening
Use when enabling RELRO, PIE, stack canaries, FORTIFY_SOURCE, CET, CFI, or seccomp filters, or checking a binary with checksec. Not for runtime sanitizer builds: use sanitizers.
binutils
Use when building static archives with ar, stripping or converting binaries, mapping crash addresses with addr2line, or demangling C++ symbols. Not for ELF analysis: use elf-inspection.
bootloaders-embedded
Use when writing a custom bootloader, jumping to application code, relocating VTOR, or implementing DFU/USB firmware update on Cortex-M. Not for reset-to-main: use baremetal-startup.
architect
Use when non-trivial code needs a design, codebase design or architecture needs improving, or one module needs targeted interface narrowing, seams, or testability. Not for diagrams, deploy, or irreversible changes.
askme
Use when eliciting intent/scope/referents or gating long/bundled/high-stakes/hard-to-undo work: exhaustive/collaborative/adversarial/gate/batch/interview/scan/proposal. Not for one fork: use decide.
autolearn
Use when a verified non-trivial fix lands or existing solution docs need refresh. Not for unverified fixes.
brainstorm
Use when the user begins knowledge work with notes, a transcript, or a brain dump, asks for divergent ideas (mode: ideate), or wants options shown in a local browser (mode: visual).
breaking-driven
Use when bloated code needs clean re-derivation, or the user says "this module is bloated" or "break it and rebuild". Not for untracked data or changes without VCS rollback.
Showing top 100 of 208 skills by quality score. Browse the full catalog at /browse.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.