---
description: Generate an objective work handoff document (TRANSFER.md) so a new agent or fresh context can continue the task without inheriting subjective reasoning or strategy.
allowed-tools:
  [
    Bash(pwd),
    Bash(ls:*),
    Bash(find:*),
    Bash(git status:*),
    Bash(git diff:*),
    Bash(git diff --cached:*),
    Bash(cat:*),
    Bash(date)
  ]
---

# /handoff — context transfer (objective only)

You are preparing a **context handoff** for a new agent or fresh session.

This command is for **state transfer only**, not reasoning transfer.

## Hard rules (STRICT)

- Be objective and factual.
- Do NOT include reasoning, decision rationale, or strategy.
- Do NOT tell the next agent what to do.
- Do NOT evaluate code quality or suggest improvements.
- Do NOT include secrets, tokens, passwords, or private keys.
- If something is uncertain, label it explicitly as *potential* or *suspected*.

---

## Output requirements

- Write the **full handoff content** to a file named `TRANSFER.md` in the project root.
- In chat, provide **only a short summary** of what was written (high-level bullets).
- Do NOT duplicate the full content in chat.

---

## TRANSFER.md structure (must follow)

### 1. Overall Goal

Describe the current task goal in neutral terms.
What the work is about, without justification or opinion.

---

### 2. Completed Work (Objective)

List completed actions or changes as facts:
- Files created / modified
- Features added or removed
- Refactors performed

No evaluation, no “why”.

---

### 3. Work in Progress

Describe what is currently being worked on:
- Active files
- Active modules
- Partial implementations

---

### 4. Potential Blockers / Open Issues

List **possible** blockers or unresolved items.

- Clearly mark them as *potential* or *suspected*
- Avoid conclusions or recommendations

Example phrasing:
- “Potential issue: …”
- “Suspected blocker: …”

---

### 5. Code & File Locations

Document where relevant code and materials are located:

- Primary working directory
- Key source files
- Related helper files
- Documentation files (if any)

Use explicit paths.

---

### 6. How to Run / Test / Reproduce

Document how to interact with the project:

- How to run the program
- How to run tests
- Important commands
- Entry points or scripts

Keep this factual and reproducible.

---

### 7. Environment, Config, and Logs

Document environment-related facts:

- Configuration files (paths + purpose)
- Required environment variable names (names only, no values)
- Log file locations
- What the logs are used for

---

## Execution steps

1) Gather the necessary information using allowed tools.
2) Generate `TRANSFER.md` following the exact structure above.
3) After writing the file, return to chat and provide:
   - A brief summary (5–10 bullets max)
   - The path to `TRANSFER.md`