resurrect
npx machina-cli add skill sivang/sivan-claude-plugins/resurrect --openclawSession Resurrection & Context Reload
Role: Lead Architect returning to a project with wiped memory. Reconstruct project state immediately from documentation.
Objective: Ingest project context, identify the critical path, and prepare for immediate coding.
Phase 1: Context Ingestion
Read and analyze the following files in order (if they exist):
README.md- High-level architectural understandingPROJECT_STATUS.md- What is finished and what is broken- Most recent
SESSION_HANDOFF_*.mdorCHANGELOG.md- Brain dump and reasoning from last session package.json/requirements.txt/Cargo.toml/pyproject.toml- Verify the stack
Phase 2: State Reconstruction
Based on the files above, answer immediately:
- Current Status: Dev, Debugging, or Refactoring mode?
- The "Active Wound": What exact problem or feature was being worked on when the session ended?
- The "Gotchas": Complex logic or bugs noted in the Handoff file to avoid breaking again.
Phase 3: Ready State
- Dependency Check: Based on config files, what install commands need to run? (
npm install,pip install, etc.) - Next Action: The single highest priority task from the Handoff file.
- Command Line: The exact command to start the dev server or run tests.
Execution Style
- Do not lecture. Read the files.
- Summarize the mission concisely.
- Provide the start command.
- Execute.
Source
git clone https://github.com/sivang/sivan-claude-plugins/blob/main/session-workflow/skills/resurrect/SKILL.mdView on GitHub Overview
Resurrects a project state by ingesting key docs to refine memory. It reads README.md, PROJECT_STATUS.md, the latest SESSION_HANDOFF_*.md or CHANGELOG.md, and dependency files to map status, active work, and gotchas. This gives you a ready-state with install steps and the next action.
How This Skill Works
Phase 1 ingests context from the listed files in order. Phase 2 reconstructs the current status, active wound, and gotchas. Phase 3 outputs the Ready State with dependency commands, the highest-priority next action, and the exact startup command.
When to Use It
- You need to resurrect a wiped memory and reload project state from docs.
- Starting a new session and want an accurate current status and plan.
- You want to know the exact dependency commands to install.
- You need the single highest-priority task from the handoff to continue.
- You want the exact command to start the dev server or run tests.
Quick Start
- Step 1: Read README.md, PROJECT_STATUS.md, SESSION_HANDOFF_*.md (or CHANGELOG.md), and dependency files.
- Step 2: Determine Current Status, Active Wound, and Gotchas; assemble Ready State.
- Step 3: Output Next Action, install commands, and the exact Start Command.
Best Practices
- Read files in the prescribed order: README.md, PROJECT_STATUS.md, SESSION_HANDOFF_*.md (or CHANGELOG.md), then dependency files.
- Clearly capture Current Status, Active Wound, and Gotchas to avoid repeating mistakes.
- Verify install commands (npm install, pip install, etc.) before execution.
- Use the Next Action as the immediate coding goal, not a broad list.
- Always provide the exact Start Command to bootstrap the project.
Example Use Cases
- Resurrect a React app after memory wipe; run npm install, then npm start.
- Python service after a long break; run pip install -r requirements.txt, then pytest or run the app.
- Go project with go.mod; run go mod download, then go run main.go.
- Node backend with package.json and CHANGELOG; install deps and start with npm run dev.
- Monorepo with multiple configs; identify active wound and present a single highest-priority action.
