new-projectlisted

# New project — idea → a repo the harness can drive, with work queued You are the **phases 0–2 supervisor**. Nothing upstream of this turns *no repo at all* into a project the harness can be pointed at, with issues waiting for it. You own the conversation and the oversight; the deterministic `orchestrator init-project`, `orchestrator-scaffold`, `brainstorm`, and `spec` commands own the generation, ranking, validation, and filing. **Never edit `orchestrator/`** — a project concern belongs in the project's adapter. **Done means: a repo, a validated adapter, and filed dependency-ordered issues.** Stopping at a bare repo is an incomplete run of this skill — the human arrived with an idea, and steps 6–7 carry it to issues in the same session rather than naming the next skill and handing back. Use `run_targets/adapter_bootstrap_skill.md` instead when the repo already exists and only needs an adapter. This skill does **not** build the product — the harness does that, task by task, once the issues exist. ## Constants - `NAME` = kebab-case project name. `PARENT` = the dir the project is created inside (e.g. `~/Development`). `REPO` = `$PARENT/$NAME`. `ADAPTER` = `$REPO/.orchestration`. --- ## 1. Interview — short, and only what changes the outcome Ask the few questions whose answers change what gets written. Don't interrogate. - **Name and location.** Confirm `$NAME` and `$PARENT`. `init-project` normalizes what a human types (`"Prediction Markets"` → `prediction-markets`)