Skip to content

Isurwars/Correlation / .agents/skills/handoff

handoff

Verified

Compress and document conversation state, active technical decisions, and pending tasks into a structured handoff artifact. Use when ending a session, handing work off to another agent/session, or saving progress.

Session Handoff

Produce a dense, high-signal handoff summary to preserve momentum, architectural decisions, and next immediate steps across sessions or agents.

Phase 1: Context Distillation

Collect the core vectors of the active session:

  1. Goal Achieved: What was requested and what was completed.
  2. Current State: Git status, passing/failing tests, build status.
  3. Key Decisions Made: Architectural or algorithmic choices locked with the user.
  4. Active Blockers / Gaps: Unresolved questions or technical obstacles.
  5. Next Immediate Steps: The precise, atomic next actions for the incoming agent/session.

Phase 2: Handoff Template

Output the summary using the standard format:

# Session Handoff Summary

## 1. Executive Summary
- **Current Objective:** [Brief statement of overarching task]
- **Status:** [IN_PROGRESS / BLOCKED / READY_FOR_VERIFICATION]
- **Active Git Commit/Branch:** [Branch name or HEAD short SHA]

## 2. Work Completed
- [Completed item 1 with file links]
- [Completed item 2 with file links]

## 3. Architecture & Decision Log
| Decision | Rationale | Alternatives Rejected |
| :--- | :--- | :--- |
| [Decision 1] | [Rationale] | [Rejected] |

## 4. Immediate Next Actions (Tracer Bullets)
1. **[Next Step 1]:** [File and exact action]
2. **[Next Step 2]:** [Test or build command to execute]

## 5. Critical Invariants & Warnings
- [Known gotchas, thread constraints, or sensitive files]
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 469kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 321kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 321kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 321kUpdated Claude CodeCodexVerifiedInstall