handoff

Files (1)

• SKILL.md

SKILL.md (first lines)

# Handoff Command

## Purpose

Use `/handoff` when:

- The current session context is getting too long and quality is degrading
- You want to start fresh while preserving essential context from this session
- The context window is approaching capacity

This creates a detailed context summary that can be used to continue work in a new session.

---

## PHASE 0: VALIDATE REQUEST

Before proceeding, confirm:

- [ ] There is meaningful work or context in this session to preserve
- [ ] The user wants to create a handoff summary (not just asking about it)

If the session is nearly empty or has no meaningful context, inform the user there is nothing substantial to hand off.

---

## PHASE 1: GATHER PROGRAMMATIC CONTEXT

Execute these tools to gather concrete data:

1. **Session history** — use this conversation (Grok has no `session_read`; rely on the thread plus any artifacts you wrote)
2. **Todos** — current `TodoWrite` list; optionally Read `.omg/todos/<sessionId>.json` if it exists
3. **oh-my-grok state** — Read when present:
   - `.omg/boulder.json` and active `.omg/plans/*.md`
   - `.omg/ralph-loop.local.md` (active Ralph / ultrawork loop)
4. **Git** (when the workspace is a repo):
   ```bash
   git diff --stat HEAD~10..HEAD
   git status --porcelain
   ```
5. **AGENTS.md** — Read at workspace root if it exists (constraints only)

Suggested order: todos → `.omg/` files → git → AGENTS.md.

Analyze the gathered outputs to understand:

- What the user asked for (exact wording)
- What work was completed
- What tasks remain incomplete (include todo state)
- What decisions were made
- What files were modified or discussed (git diff/stat + status)
- What patterns, constraints, or preferences were established

---

## PHASE 2: EXTRACT CONTEXT

Write the context summary from first person perspective ("I did...", "I told you...").

Focus on:

- Capabilities and behavior, not file-by-file implementation details
- What matters for continuing the work
- Avoiding excessive implementation details (variable names, storage keys, constants) unless critical
- **USER REQUESTS (AS-IS)** must be verbatim (do not paraphrase)
- **EXPLICIT CONSTRAINTS** must be verbatim only (do not invent)

Questions to consider when extracting:

- What did I just do or implement?
- What instructions did I already give which are still relevant?
- What files did I tell you are important or that I am working on?
- Did I provide a plan or spec that should be included?
- What did I already tell you that is important (libraries, patterns, constraints, preferences)?
- What important technical details did I discover (APIs, methods, patterns)?
- What caveats, limitations, or open questions did I find?

---

## PHASE 3: FORMAT OUTPUT

Generate a handoff summary using this exact format:

```
HANDOFF CONTEXT
===============

USER REQUESTS (AS-IS)
---------------------
- [Exact verbatim user requests - NOT paraphrased]

GOAL
----
[One sentence describing what should be done next]

WORK COMPLETED
--------------
- [First person bullet points of what was done]
- [Include specific file paths when relevant]
- [Note key implementation decisions]

CURRENT STATE
-------------
- [Current state of the codebase or task]
- [Build/test status if applicable]
- [Any environment or configuration state]

PENDING TASKS
-------------
- [Tasks that were planned but not completed]
- [Next logical steps to take]
- [Any blockers or issues encountered]
- [Include current todo state]

KEY FILES
---------
- [path/to/file1] - [brief role description]
- [path/to/file2] - [brief role description]
(Maximum 10 files, prioritized by importance)
- (Include files from git diff/stat and git status)

From mihazs/oh-my-grok, MIT.

More from mihazs/oh-my-grok