Outline Driven Development

Use when a protocol, concurrent algorithm, or design needs a model-checked TLA+ or Alloy spec, or a TLC or Apalache trace needs reading. Not for choosing when to model: use validation-first-driven.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Use when Rust code, especially unsafe or panic-critical paths, needs a Kani, Verus, or Creusot harness written, run, and its failure read. Not for choosing the proof policy: use proof-driven.

The English summary is being prepared. Showing the original description.

Use when a workflow, plan, diff, or completed work cycle must be checked for practices that punish the project later. Not for source, remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when a proof needs Isabelle/HOL, its Sledgehammer automation, or an AFP session. Not for Lean 4: use writing-lean-proofs.

The English summary is being prepared. Showing the original description.

Use when the user suspects no installed skill covers a task and wants proof. Names the owning skill or writes a missing-skill brief. Never routes or invokes the matched skill.

The English summary is being prepared. Showing the original description.

Use when an answer is wanted from one named seat only: breaking, business, career, codebase, human, impact, innovation, moat, rent-seeking, skeptic, or stability. Not for multi-lens synthesis: use prism. Not for rebuilding from primitives: use from-first-principle.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Use when the user asks for a council, second opinions, or parallel investigation. Not for cross-examination of existing proposals: use cross-critique.

The English summary is being prepared. Showing the original description.

Use when a task, feature, or fix is called done, complete, finished, or fixed, or before a commit, PR, or next task. Not for fact-checking: use verify-both-ways. Not for measuring: use verify-this.

The English summary is being prepared. Showing the original description.

Use when an artifact or skill has just changed and is about to be called done, committed, or handed off. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when an abstraction leak must be sealed as a module seam, configuration option, or explicit override, or exposed as a named boundary. Not for detecting concealment patterns: use no-hide.

The English summary is being prepared. Showing the original description.

Use when the user invokes /ios-visual-review to audit an iOS app's visuals on a real device. Not for remote, credential, publish, deploy, or irreversible changes.

The English summary is being prepared. Showing the original description.

Use when a user builds or styles a web frontend or asks to make it not look AI-generated. Not for component-level UI work without the token system: use frontend-ui-engineering.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Use when any bounded workflow starts or reaches an action, path, proposal, or merge boundary. Refuses rather than default-allow on an unreadable constraint set.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Use when work is about to grow past the ask, the task may already be done, or the user requests only the minimum. Not for executing the work: use tdd to build or strike-the-root to fix.

The English summary is being prepared. Showing the original description.

Use when the user requests axiom, axiom-mode, axiom-compact, formal-logic, or compact form. Not for changing code or remote state.

The English summary is being prepared. Showing the original description.

Use when /polished-web-prototype runs or a user builds an artifact from a mockup, design plan, or brief. Not for variant galleries: use design-variants. Not for live audits: use web-design-review.

The English summary is being prepared. Showing the original description.

Use when a human invokes this skill to build a webhook UI that wakes a bot. Not for unpreviewed or unapproved credential, host, Tailscale, deployment, remote, paid, or irreversible changes.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Use when a current decision needs pressure-testing until the rationale is clear to a skeptic. Not for tasks requiring source or remote-system changes.

The English summary is being prepared. Showing the original description.

Use when the user asks why a plan is wrong or says "poke holes in this". Not for tasks that require source or remote-system changes.

The English summary is being prepared. Showing the original description.