Resurrect: AI Revival Reports for Side Projects

Every developer has a graveyard of side projects. A folder full of half-finished apps, abandoned six months ago when you hit a wall and didn't come back. The code is still there, but the story (what you were building, why you stopped, what to do next) is gone. So you start something new instead, and the graveyard grows. Resurrect uses IBM Bob's repo-wide context to bring abandoned projects back to life. Point Resurrect at any project directory and it produces a structured Revival Report with five sections: 1. A verdict (REVIVE, ARCHIVE, or REBUILD) with reasoning and time-to-MVP 2. What this project actually is, reconstructed from the code (not the stale README) 3. Where you left off (last commit, unmerged branches, half-built features, blockers) 4. What's broken, stale, or risky (outdated dependencies, security issues, dead code) 5. A prioritized P0/P1/P2 action plan with effort estimates This is the structured re-onboarding document every indie hacker hand-writes for themselves, but no tool has ever shipped. Resurrect is only possible because of IBM Bob. Traditional AI tools see one file at a time. Bob reads the entire codebase, traces relationships between files, follows git history, and connects code to comments. When Bob analyzes an abandoned project, it doesn't just grep for TODO. It understands why a TODO exists, what it's blocking, and how it relates to the rest of the system. The proof-of-concept demonstrates Resurrect on two real abandoned projects: AlbumLog (a Letterboxd-for-music app, verdict: REVIVE, 1-2 weekends to MVP) and TaskTower-v3 (yet another AI to-do app, verdict: ARCHIVE, competitors shipped the same feature 12 months ago). Production architecture spans two deployment modes: a Web App for sharing reports publicly and a VS Code Extension that runs locally and offline use. Future v2: an MCP server so any IDE can call Resurrect directly. Built solo by Syed Arfan Hussain.