resurrect-projectlisted

# resurrect-project Help the user revive a dormant code project — *with intention*. The risk in resurrection is migrating yesterday's assumptions into today's rewrite; this skill's job is to interrupt that, force a fresh architectural conversation, and only then scaffold. ## Quick start Four phases, run in order. Each phase has a dedicated flow file with full detail; pull the file in only when entering that phase. 1. **Survey** ([flows/1-survey.md](flows/1-survey.md)) — read READMEs, package.json/pyproject.toml/Gemfile, last commits, deploy configs. Treat all of this as **historical signal**, not current fact. Surface what the project *was*, then explicitly question whether any of it still applies. 2. **Reflect** ([flows/2-reflect.md](flows/2-reflect.md)) — *before* the architecture conversation, ask the harder questions: what was the original intent, did it ever work, why did it stall, what would you change, why pick it up now, and crucially **time-capsule vs ongoing use** (motion check). This phase determines whether Phase 3 happens in full, in part, or at all. 3. **Architect** ([flows/3-architect.md](flows/3-architect.md)) — *only if* Phase 2 lands on "ongoing use" (or stronger). Today's stack decisions. Use the stack-specific question file under [references/stack-questions/](references/stack-questions/); for unknown stacks fall back to [_generic.md](references/stack-questions/_generic.md). If Phase 2 landed on "time capsule," skip to the minimal "what's the least ch