init-project

# Skill: init-project The greenfield front door. An idea arrives and there is no repo yet — no foundation recorded, no first slice built. The temptation is to *yolo* a throwaway prototype, get it sort-of working, then retrofit structure and lose the rationale. This skill gives that path a home: it turns an idea into a structured repo by **composing the skills the repo already owns**. It orchestrates; it does not reinvent, and it is **not** an autonomous code generator — the human stays in the loop and the existing skills do the work. It is the twin of `adapt-to-project` (the brownfield front door, for an *existing* repo). Both converge on the same downstream loop: `brief → reference.md → spec → low-level design → work-loop`. ## When to invoke Invoke when the unit of work is a **brand-new repo from an idea** and there are real **stack / structure / tooling decisions** ahead — a service, a library, a multi-component app someone will maintain. The tells: "start a new project", "bootstrap this idea into a repo", "we're greenfielding X". Do **not** use it when: - You are inside an existing codebase → `adapt-to-project` is the brownfield front door. - You want to author one feature from scratch → `new-spec`. - The thing ahead is a script, a spike, or a throwaway with no real structural decisions → the **trigger gate** (stage 1) sends it straight to scaffolding; don't force the flow onto it. ## The flow — five phases, fluid not waterfall The five stages below are **flu...