init-projectlisted

# Skill: init-project **What it does.** Bootstraps a new book from the p10t template: interviews the author for the essentials, populates `project.yaml`, resets project-specific files to blank templates, and verifies the generic machinery is intact. The first skill run in any new project. **Triggers** - "init the project" - "/init-project" - "set up this book" - "start a new book here" - Equivalent phrasing in any language **Input.** None — everything is gathered by interview. **Output.** A configured `.project/`, a filled `project.yaml`, an adjusted root `CLAUDE.md`, and a suggested first-steps plan. --- ## Core principle > **Ask only what cannot be defaulted. Configure everything the answers imply.** A bootstrap that asks twenty questions never gets finished. The interview is seven questions or fewer; everything else is derived or left at sensible defaults, explicitly listed at the end so the author knows what to adjust later. --- ## Execution protocol ### Step 1 — Detect the starting state Check what exists: - **Fresh clone** (config files still contain `{placeholders}`) → full bootstrap - **Existing manuscript present** (files in `manuscript/` or elsewhere) → bootstrap + offer the extraction path (Step 5) - **Already initialized** (`project.yaml` has a real title) → stop; offer to update settings instead of re-initializing. **Never reset an active project.** ### Step 2 — The interview Seven questions, one message: 1. **Title** (working title is fine) 2. **