quickstartlisted

# Quickstart Run the foundational project setup in the right order. This skill coordinates other skills; it should not skip their safety checks. ## Pipeline ```text domain-to-spec -> scaffold-frontend -> scaffold-backend, only if PRD says Yes ``` ## Preflight Check for existing project artifacts: ```bash test -f AGENTS.md && echo AGENTS_EXISTS || true test -f PRD.md && echo PRD_EXISTS || true test -d client && echo CLIENT_EXISTS || true test -d server && echo SERVER_EXISTS || true ``` If any exist, stop and show what was found. Ask whether to skip existing steps, update the existing specs, or cancel. Do not overwrite silently. Treat overwrite as an exceptional recovery path, not a normal quickstart option. If the user asks to start fresh, explain exactly which files or folders would be replaced and ask for explicit confirmation before any destructive action. ## Step 1: Run `domain-to-spec` Use the `domain-to-spec` workflow end to end. Capture the user's domain, MVP flow, backend decision, pages, routes, constraints, and success criteria. Verify: ```bash test -f AGENTS.md && test -f PRD.md && echo STEP_1_OK || echo STEP_1_FAILED ``` If this fails, stop. The scaffold skills need the docs. ## Step 2: Confirm The PRD Before scaffolding, show the user: - `Pages / Screens` - `Backend Needed?` - `Backend Routes`, if any - `Core Features (MVP)` Ask the user to confirm or provide corrections. Update `PRD.md` if they correct it, then show the sections again. Only conti