initiatelisted

# Initiate — project cold start Execute in order, no skipped steps. Setup and alignment only — no feature code until the first task is started. ## 1. PRD Read `PRD.md` fully — scope, goals, features, technical requirements, integrations, and the **full tech stack** (the PRD always specifies it). If missing, stop and ask for it. If the PRD names the stack, that IS the stack — do not substitute or "improve" it. ## 2. Scaffold Stand up the project skeleton so the repo is real and runnable before docs/tasks: 1. **Read the stack from the PRD** (framework, language, package manager, backend, hosting, key libs). Echo it back in one line and confirm y/n before scaffolding. Never impose a default stack — the PRD is the source of truth; only ask if the PRD genuinely omits a piece. 2. **Init** the project (framework CLI / template), pin the **package manager** (bun/npm/pnpm — one, never mixed), install deps. 3. **Baseline files**: `.gitignore` (env, build, `.docs/*.local` if any), `.env.example` (keys only, NO values), `README.md` stub, `tsconfig`/lint/format config, editor config. 4. **Git**: `git init`, first commit `chore: scaffold <project>` on a branch — do NOT push, do NOT create remote (green-light rules from /ship apply). 5. **Verify it runs**: dev server boots / build passes / typecheck green — capture the one command that proves it (feeds `verification.md`). A scaffold that doesn't run isn't done. 6. **Secrets**: any real key goes to env/Keychain with a pointer in `integrat