conductor-initlisted

Initialize a repo for the Conductor Method loop: write init.sh, seed FEATURES.json from the spec, create CONTEXT.md and MEMORY_BANK.md, verify a one-command test and a one-command lint actually pass, and land the baseline commit `loop(0): baseline green + criteria defined`. Use whenever someone is standing up a builder/verifier loop on a repo that doesn't have one yet, or says "set up the conductor loop here", "initialize this repo for the loop", "do Phase 0", "get this repo loop-ready", "seed FEATURES.json", or asks why the verifier keeps returning BLOCKED on a fresh project (the answer is almost always missing acceptance criteria, which is what this skill installs). Also use on an existing repo to audit and repair a half-done Phase 0. Do NOT trigger to design the loop itself or write its prompts — that is `loop-creator`; this skill only prepares the ground the loop runs on.
scoobydrew83/skills · ★ 0 · AI & Automation · score 78

Install: claude install-skill scoobydrew83/skills

# Conductor Init CONDUCTOR-LOOP-GUIDE Phase 0 as an agent instead of a human checklist. You run once per repo, before any builder or verifier does, and you leave behind the portable state, policy, and evidence artifacts every later phase assumes. Everything downstream is graded against what you write here. A verifier with no acceptance criteria returns `BLOCKED`; a loop with no green baseline can't tell its own breakage from the code's. Get this wrong and every phase after it is measuring nothing. ## The non-negotiables 1. **Criteria before code.** You produce checkable criteria, not a plan and not an implementation. If the spec is too vague to yield a runnable check, that's the finding — say so and stop. Do not invent criteria to fill the file. 2. **Green baseline or no baseline.** The commit is `loop(0): baseline green + criteria defined`. If test or lint doesn't pass, the baseline isn't green and you don't make that commit. Report what fails instead. 3. **One command each.** Test and lint must each be a single command a cold agent can run without reading the README. If they aren't, make them so (a script, an npm script, a Makefile target) — that IS part of the job. 4. **Evidence, not assertion.** Every criterion names a command and its observable outcome. "Works correctly" is not a criterion. 5. **You initialize; you don't build.** Nothing you write implements the project's features. Resist it. ## Workflow ### 1. Read the ground Before writin