handoffplan

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 captures data. The plan defines work. Beads track phases. Then you commit, close, and give the user a paste prompt that tells the next session to start executing Phase 1 immediately — no onboarding, no exploration, just code. The next session gets full clean context because it's a fresh session.

Arguments: $ARGUMENTS

Compact mode. If $ARGUMENTS contains the word compact-mode, the compact-handoff mod started this run and will replace the conversation with the plan when your turn ends. Follow the handoff skill's compact-mode rules: ask nothing in this turn, and take stated defaults. Run Steps 1-6 as normal, but keep Step 5's report to one line (the compaction replaces it seconds later) and skip Step 6 item 3. Print Step 6's paste prompt block exactly as the template has it (header, dashed rules, every line): the mod sends it as the next prompt word for word. End your turn with this exact last line, paths relative to the repo root: COMPACT-HANDOFF-READY: {handoff path} | {plan path} If either file could not be written, end with COMPACT-HANDOFF-FAILED: {reason} instead.

---

CHECKPOINT before Step 2: Count the handoff's lines. Check its mining-pass minimum (Quick: 150/250, Deep: 300, Chunked: 500 — see handoff skill's Line Budget table). If the handoff is under its pass minimum, STOP. Run the handoff's Phase 2 gap research pass now — read back what you wrote, scan the conversation for uncaptured data, and Edit to expand. Do not proceed to the plan with a thin handoff. The plan's quality is bounded by the handoff's quality.

---

Step 2: Write the plan file.

Once the handoff file exists, write the plan. The plan lives in the same directory as the handoff, with the same slug:

• Handoff: HANDOFF_{chain_tag}_{slug}_{date}.md (already written — or HANDOFF_{slug}_{date}.md if no beads)
• Plan: PLAN_{chain_tag}_{slug}_{date}.md (write this now — mirror the handoff's naming)