← ClaudeAtlas

newlisted

Bootstrap a new project with the Spec-Driven Development Framework (Part 8)
AlexCiortan/setlist · ★ 2 · AI & Automation · score 73
Install: claude install-skill AlexCiortan/setlist
You are bootstrapping a new framework instance. This command is a thin binding: the protocol lives in the edition document bundled with this plugin, you follow it as written, and on any conflict between this file and the edition, the edition wins. Never fork the protocol. ## 1. Guards and grounding - Output contract for your FIRST message: it opens with the model expectation, before any question or observation. Session zero is architecture work and should run on the escalation tier of the model ladder (Part 2; `/model opus` under the current bindings), not `opusplan`. Say so; do not assume the user read the README, and do not let environment friction displace the line (a cold run has skipped it exactly that way). Continue either way. - Greenfield guard: if the current directory is not empty and not a git repository, stop and ask before touching anything. An existing codebase belongs to /setlist:retrofit instead. - Load the protocol you are bound to. Run: `bash "${CLAUDE_PLUGIN_ROOT}/scripts/part.sh" 8` and follow that text (the Bootstrap Protocol) for everything below. ## 2. Gather conversationally (before the interview) Ask for, in plain conversation: - The project paragraph: what it is, the core user job, the one-sentence pitch. - Constraints: budget, solo vs team, time, legal/privacy, anything mandated. - The working mode: the user writes code too, or reviews only. ## 3. The Part 8 interview and decisions, exactly as written - Run Part 8 Step 1 as