Read Will

Overview

Read WILL.md and resume work from where the previous Claude instance left off. You're inheriting a session - honor the handoff by understanding context before acting.

Phase 0: Brivlo

If brivlo:send_event is available, use brivlo:send_event will:read as your first step.

The Process

Phase 1: Read WILL.md

# Check if WILL.md exists

Use Read tool on WILL.md in project root.

If it doesn't exist, tell the user: "No WILL.md found - nothing to hand off."

Phase 2: Understand Context

Read and internalize:

1. •Original request - What was the user trying to accomplish?
2. •Current status - Where did the previous instance stop?
3. •What was done - Don't redo completed work
4. •Next steps - What's the immediate action?
5. •Key files - Read these to understand current state
6. •Decisions made - Respect previous architectural choices
7. •Open questions - These may need user input

Phase 3: Verify State

Check that the codebase matches what the will describes:

• •Do the mentioned files exist?
• •Are changes described actually present?
• •Is anything out of sync?

If state doesn't match, flag it: "WILL.md mentions X but I see Y - which is current?"

Phase 4: Summarize & Confirm

Tell the user:

1. •Brief summary of inherited work
2. •What was already completed
3. •What the next step is
4. •Any open questions that need answers

Then ask: "Ready to continue with [next step]?"

Phase 5: Continue Work

Once confirmed, proceed with the next steps from the will. You now own this work.

Red Flags

If you catch yourself doing these, STOP:

• •Starting fresh - You have context, use it
• •Redoing completed work - Check "What Was Done" first
• •Ignoring decisions - The previous instance made choices for reasons
• •Skipping verification - State may have changed since the will was written
• •Acting without confirmation - Let user confirm before continuing

Quick Reference