Stats
Actions
Tags
From brandtam-skills
Investigate and revive a dormant code project — survey existing code as historical signal, interview the user on today's architectural intent, capture decisions, then scaffold a project page and a rewrite plan. Use when the user says "resurrect", "revive", "bring back", "rebuild", or "modernize" an old or dormant code project, references picking up an abandoned codebase, or asks to plan a rewrite of something that already exists. Adapts to host project — conforms to a wiki schema if one is present (CLAUDE.md + projects/ folder + log.md), otherwise emits portable markdown.
How this skill is triggered — by the user, by Claude, or both
Slash command
/brandtam-skills:resurrect-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
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.
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.
Four phases, run in order. Each phase has a dedicated flow file with full detail; pull the file in only when entering that phase.
Survey (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.
Reflect (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.
Architect (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/; for unknown stacks fall back to _generic.md. If Phase 2 landed on "time capsule," skip to the minimal "what's the least change to unblock it?" question only.
Scaffold (flows/4-scaffold.md) — write a project page (in the host wiki if one exists, otherwise standalone), cross-link to repos/domains/related work, append a log.md entry if the host has one, and end with a clear "next concrete step."
The motion check happens in Phase 2 (Reflect), but the vocabulary is the skill's foundation — see references/vocabulary.md. These are not synonyms:
Primary spectrum (set during Phase 2):
Fine-grained variants (relevant once "ongoing" is chosen):
The interview depth, the scaffolding, and the project page's status: value differ across these. Confirm before proceeding past Phase 2.
Detect once, at the start of the survey phase. Run this check from the user's current working directory:
ls CLAUDE.md projects/ log.md 2>/dev/null
Interpret:
./RESURRECTION-<slug>.md or similar) and tell the user where.Do not hardcode any specific wiki's schema. The reference wiki this was built against is at /Users/brandt/codes/brandtam/mybot-dev but the skill must not assume it.
resurrect-old-repo skill — they're peers with different emphases; use whichever the user reaches for.npx claudepluginhub brandtam/skills --plugin brandtam-skillsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.