Use this skill after /slo-spike has filled §7, to fill §8 Curation Decision — decide honestly. Mode is convergent. Classify confidence as exploratory, confirmatory, or engineering_ready from the evidence; require ablation and failure analysis before an engineering route; and give every candidate exactly one frozen disposition citing evidence. No vague maybes survive; dead ends route to §11 compost. Hands off a RecommendationPacket readiness block to /slo-demo.
Use this skill after /slo-curate has filled §8, to fill §9 Demo Pack + §10 Handoff Contract — make the discovery communicable and emit a method-complete RecommendationPacket. Mode is communication. Preserve confidence, ablation, failures, replication, limitations, and the exact next question, then fill the ONE promotion-seed table matching the disposition. Promotion is a SUGGESTION the human accepts — never an auto-invocation. Closes the Innovation Sandbox loop.
Use this skill after /slo-pattern has filled §5, to fill §6 Precision Model — make the invisible measurable. Mode is measurement. Convert each promising pattern into a falsifiable claim with a measurement handle, an accept threshold AND a kill threshold, resource bounds, security invariants, and a versioned Protocol Freeze before confirmatory work. Do NOT accept "feels better" without a handle. This is the OK-Go "math" move for engineering. Hands off to /slo-spike.
Use this skill after /slo-precision has filled §6, to fill §7 with a bounded DiscoveryRecord and/or ValidationRecord. Discovery is exploratory and may refine a mechanism; validation cites one complete active ProtocolFreeze, uses held-out frozen arms with no tuning, and records exact commands, environment, repetitions, stability, deviations, and per-arm results. This is the ONLY phase that may run code, scratch-only under experiments/<slug>/<spike-id>/. Every spike has a finite budget and delete-or-promote decision. NOTHING becomes production without the normal SLO Sprint or Ticket loop. Hands off to /slo-curate.
Use this skill to drive one milestone of a v3 runbook. Invoke with the milestone number or identifier, e.g. "/slo-execute M3" or "execute milestone 3 of the runbook". Restates milestone constraints, writes BDD tests first, implements the smallest safe change, fills the evidence log. REFUSES to touch files outside the milestone's allow-list without pausing and surfacing the conflict. Replaces the inner loop of the legacy sldo-run binary.
Use this skill when a product repo needs graph-backed codebase understanding, fast troubleshooting, or security triage. It combines Graphify knowledge graphs with semantic-provider facts from rust-analyzer / TypeScript language service and analysis-provider findings from OpenGrep or Semgrep-compatible rule packs. It is designed for private repos: raw evidence stays out of git; only anonymized summaries may be committed.
Use this skill to wire threat-model-driven SAST scanning into a target product repo. Reads docs/slo/design/<slug>-threat-model.md for CWE references, picks tuned Semgrep rule packs for the detected stack, emits a safe GitHub Actions workflow plus a baselined config plus an audit-defense manifest, and re-derives the ruleset on threat-model edit. Pure Markdown skill; no Rust binary dependency. Pair with /slo-rulegen for project-specific rules.
Use this skill when the user wants to pull or claim a bite-sized ticket from GitHub Issues before implementation. It normalizes issue context, applies the ticket sizing gate, creates or updates one persistent issue workpad comment, and hands off to /slo-ticket-plan. It does not write code.