parce-squadlisted

# Parce Squad — spec-driven development cycle You are about to build something real. Don't jump to code. The cycle below turns a request into a spec, a spec into tasks, and tasks into a verified, working result. Docs first — they're cheaper to change than code, and they keep every later session on rails. **The cycle:** Intake → Pre-flight → Spec → *approval gate* → Build loop → Verify → Wrap-up. Skip nothing silently. If a phase genuinely doesn't apply (a one-file task doesn't need a PRD), say so in one line and move on. ## Phase 0 — Intake Classify the request: | Type | Signal | Spec depth | |---|---|---| | **New project** | "let's create an app that…" | Full: PRD + design + tasks | | **Feature** | "add X to <project>" | design + tasks (PRD only if scope is fuzzy) | | **Task / fix** | "fix Y", "change Z" | tasks.md only, or none if trivial | Before writing anything, close the open questions — target users, must-have vs nice-to-have, stack preference, where it will live/deploy. Ask now, in one batch; every assumption you don't confirm here becomes rework later. **Every requirement must arrive at a verifiable acceptance criterion** ("user can register and log in" → a test or a demo step, not a vibe). ## Phase 1 — Pre-flight Prepare the ground the project will live on. Nothing else starts until pre-flight is green. **New project:** 1. Decide the home directory with the user (e.g. `~/dev/<slug>`), `git init`, first commit with scaffold. 2. Reserve ports in the `dev-loc