← ClaudeAtlas

handoffplanlisted

Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.
REMvisual/claude-handoff · ★ 20 · AI & Automation · score 85
Install: claude install-skill REMvisual/claude-handoff
# Handoff Plan **IMPORTANT: This skill writes files. You MUST NOT be in Claude Code's built-in plan mode.** If you are currently in plan mode, **exit plan mode first** (use ExitPlanMode) before proceeding. This skill produces plan *files* — it does not use Claude Code's plan mode feature. They are different things. **Step 1: Run `/handoff` to create the data file — FULL TWO-PHASE PROCESS.** Execute the full `/handoff` skill first, including the **mandatory two-phase write process**: - **Phase 1:** Write the handoff file (all sections, narrative + evidence) - **Phase 2 (MANDATORY for Deep and Chunked passes):** Read it back, scan conversation for uncaptured data, use Edit to expand toward the ceiling (800 lines for 1M context) This is not optional. The handoff is the data store — a thin handoff produces a thin plan. Follow the handoff skill's mining-pass detection, line count checks, and gap research pass exactly as specified. **Do NOT skip or abbreviate the handoff.** Do NOT skip Phase 2. If the handoff is under 500 lines on a Chunked pass, you haven't mined deep enough — go back and expand before writing the plan. **Do NOT ask to close the session after the handoff.** Skip Step 8 of the handoff skill ��� the close prompt happens after the plan is written, not after the handoff. **Do NOT enter Claude Code plan mode at any point.** This skill writes files and commits. Plan mode is not used. **This skill creates a plan for the NEXT session to execute.** The handoff capt