phase-project-initlisted

# Phase Project Init This skill prepares an empty or new project so the rest of the phase workflow has the structure it expects. Run it once, at the very start of a project. > **Empty repo only.** If the project already has code and git history, use `phase-adopt` instead — it lands the same scaffolding through a docs-lane PR rather than the direct bootstrap commit below. It is **not itself a phase** — bootstrapping needs no phase plan or log. In a git-tracked project it is the one time it is acceptable to make a direct commit to the default branch (the initial scaffold commit), because there is nothing yet to branch from. Every commit after this one goes through the branch + worktree + PR cycle. ## What "set up" means By the end, the project has: 1. A decision about git — and, if the user wants it, a repository with an initial commit and a known default branch. **Git is optional**; the workflow runs without it. 2. A **knowledge bundle** at `development/` — a `design/` layer, a `phase_log/` layer with the three templates and a seeded `phase_index.md`, and the reserved root files. 3. The conventions the phase skills rely on, optionally documented at the project root. 4. A clear answer to "what's the first phase?" — handed off to `phase-tracker` (single effort) or `phase-loop` (large umbrella plan). ## Procedure ### Step 1: Confirm the project root and intent Confirm the directory to initialize and that it is meant to be a new phase-workflow project. If it already has a