reconstructlisted

# Reconstruct: any repo — or any idea — → a buildable PRD suite For engine evidence and coverage limits, read [engine-evidence](references/engine-evidence.md). A dependency-free Node script does the **deterministic** scaffold (facts + candidate *hints*); **you** supply the framework-aware understanding — the interface surface, the data model, the real features — for any stack. The output is a folder of PRDs an agent can rebuild the project from, with no access to the original and no access to this conversation. **The markdown is the program.** The engine never reasons; every judgement in this skill is yours. ## Route the request | The user wants | Path | Start with | Then read | | --- | --- | --- | --- | | Rebuild / clone / reverse-engineer a repo; turn code into specs | **code** | `node scripts/analyze.mjs --repo <REPO> --out <OUT>` | [procedure.md](references/procedure.md) §Path A | | Turn an idea into PRDs / a build plan (no code yet) | **greenfield** | **interview first** — no command | [scratch-playbook.md](references/scratch-playbook.md), [procedure.md](references/procedure.md) §Path B | | Decide *what* to build; explore concepts | **brainstorm** | `node scripts/analyze.mjs --brainstorm --out <DIR>` | [brainstorm-playbook.md](references/brainstorm-playbook.md) | | Continue / refresh a reconstruction that already exists | **resume** | `node scripts/analyze.mjs --check --out <OUT>` | [procedure.md](references/procedure.md) §Path D | | One file to hand an agent to imp