project-guidelisted

# project-guide — the whole-project brief, history, and interview lens Produce one document that lets me (a) understand a project end-to-end in its current state, (b) tell the story of how and why it was built the way it was, (c) build the vocabulary and mental models to discuss it fluently, and (d) walk into a conversation with a recruiter or hiring manager who has the repo open and hold my own — knowing both what looks good and what doesn't, and how to talk about each honestly. **Project-agnostic. Stage-agnostic.** Works on a 2-day-old scaffold or a 2-year-old codebase; scale the depth to what's actually there (see Scaling). Work only from observable state — the repo, its git/PR history, its docs. Never invent decisions or capabilities; an honest "not yet built" beats a confident fiction (a hiring manager will run the code). ## Relationship to sibling specs - `/wrap` — recaps **one session**; this recaps the **whole project**. - `kickoff` — briefs a project at its **start**; this briefs it at **any point**. - [[narrate]] — the audio engine; `--audio` here narrates the talking-points section so I can rehearse the pitch by ear. ## Parse `$ARGUMENTS` - `--quick` → lighter pass: Snapshot + Capabilities + Architecture + a short recruiter lens. Skip the deep history mining. Good for small/early projects or a fast refresher. - `--update` → a guide already exists for this project (find the latest in the save dir): refresh it, focusing on what changed since its date, and