Write Will

Overview

Write a WILL.md file that captures everything a future Claude instance needs to continue the current work. This is your "last will and testament" - make it complete enough that your successor can pick up exactly where you left off.

Phase 0: Brivlo

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

The Process

Phase 1: Gather State

Collect from the current session:

1. •What we were working on - The original request/goal
2. •Current status - Where we are in the work
3. •What's been done - Completed steps, files changed
4. •What's next - Immediate next steps
5. •Key context - File paths, decisions made, gotchas discovered
6. •Blockers/Questions - Anything unresolved

Phase 2: Write WILL.md

Create WILL.md in the project root with this structure:

# Session Handoff

> Written: [timestamp]
> Original request: [brief summary of what user asked for]

## Current Status

[One paragraph describing where we are - what's done, what's in progress]

## What Was Done

- [Completed item 1]
- [Completed item 2]
- ...

## Next Steps

1. [Immediate next action - be specific]
2. [Following action]
3. ...

## Key Files

- `path/to/file.rb` - [why it's relevant]
- `path/to/other.rb` - [why it's relevant]

## Context & Decisions

[Important context the next instance needs to know - architectural decisions, constraints discovered, approaches tried/rejected]

## Open Questions

- [Any unresolved questions for the user]
- [Any blockers that need resolution]

## Prompt to Continue

[A ready-to-use prompt the user can give to the next Claude instance to resume work]

Phase 3: Confirm

Report: "Will written to WILL.md - ready for handoff"

Optionally show the "Prompt to Continue" section so user can copy it.

Red Flags

If you catch yourself doing these, STOP:

• •Being vague - Be specific about files, line numbers, exact state
• •Assuming context - The next instance knows NOTHING about this session
• •Skipping the prompt - The continuation prompt is the most important part
• •Including conversation transcript - Summarize, don't dump
• •Forgetting timestamps - The next instance needs to know how stale this is

Quick Reference