spec-kickofflisted

Guides you through a spec-first kickoff before building anything substantial — Andrej Karpathy's three layers (spec → verifier → environment), expressed through Claude Code's own primitives, not a new framework. Phase 1 interviews you down to a self-contained SPEC.md with EARS requirements (you own the goal, the agent does the thinking). Phase 2 builds a verification plan: maps every acceptance criterion to the strongest available check (deterministic > external signal > judge), picks a gate strength, and optionally adds a fresh-subagent or Codex adversarial review. Phase 3 wires it into the environment you already have (CLAUDE.md, skills, hooks, guardrails) instead of rebuilding it. Output is ONE SPEC.md that ends in an end-to-end verification step, then a handoff to the build. Use when STARTING a new build/feature/project and you want to begin it right — NOT for trivial changes you can describe in one sentence. Trigger phrases — EN: "spec-kickoff", "kickoff", "spec this", "spec first", "before we build", "h
bks-lab/open-bridge · ★ 8 · AI & Automation · score 74

Install: claude install-skill bks-lab/open-bridge

# Spec-Kickoff A phased, checkpointed kickoff for **starting a new build the right way** — Andrej Karpathy's three layers (**spec → verifier → environment**), expressed through Claude Code's own primitives. You produce **one self-contained `SPEC.md` that ends in an end-to-end verification step**, then hand off to the build. This is **not** a new framework. It is spec-kit's discipline + Kiro's EARS/gates, expressed through Anthropic's native *"interview → SPEC.md → verify-loop"* pattern, wired into the environment the user already has. Conceptual depth, the verified Karpathy sources, and the EARS / ladder / gate cheat-sheets live in [`references/method.md`](references/method.md). The artifact you fill is [`assets/SPEC.md`](assets/SPEC.md). A one-page visual explainer for humans (open in a browser) ships at [`assets/spec-kickoff-explainer.html`](assets/spec-kickoff-explainer.html). > Talk to the user in their conversation language. Keep the interview **sharp and > short** — a handful of load-bearing questions, not a survey. This skill is opt-in: > when invoked the structure is wanted, but never let it become a ceremony tax. --- ## Phase 0 — Frame & skip-check (≈30 seconds) 1. **Skip-gate first.** If any of these holds, say so and do NOT run the kickoff: - you could describe the whole change in one sentence (Anthropic: skip the plan); - it's a quick fix (≲10 min, <3 files); - you're mid-build, not starting something new. → Point at the normal build flow. The m