# Defer File Template

Use this structure when creating defer files.

---

```markdown
# Deferred: <Brief Title>

Created: YYYY-MM-DD
Status: In Progress | Blocked | Ready to Resume

## Context

<2-3 sentences: What were we doing? What triggered this deferral?>

## Original Intent

<What is the user trying to accomplish? Capture the goal, not the implementation.>

## Findings

<What did the critique/check surface? List issues, trade-offs, or open questions.>

### Trade-offs Requiring Decision

- [ ] **<Trade-off 1>**: <Option A> vs <Option B>
  - A: <pros/cons>
  - B: <pros/cons>
  - Recommendation: <if any>

- [ ] **<Trade-off 2>**: ...

### Issues Found

- [ ] <Issue 1>: <brief description>
- [ ] <Issue 2>: ...

## Tasks

<Concrete tasks to complete this work. Check off as completed.>

- [ ] Resolve trade-off decisions with user
- [ ] <Task based on findings>
- [ ] <Implementation task>
- [ ] Verify work meets original intent
- [ ] Delete this file when complete

## Resumption Notes

<Any context that would help a fresh session pick this up:>
- Key files: <paths>
- Related docs: <paths>
- Commands to run: <if any>

## Implementation Guidance

When resuming this work:
1. Read this file completely before starting
2. Use subagents (Task tool) for individual tasks - keeps context focused
3. Have subagents check off tasks in this file as they complete
4. Coordinate from main thread, delegate execution to subagents
```

---

## Usage Notes

**Keep it conceptual.** Capture decisions and constraints, not implementation details. The implementing AI has patterns and context to decide HOW.

**Tasks should be actionable.** Each task should be completable by a subagent with access to the file and codebase. Avoid vague tasks like "figure out the approach."

**Trade-offs need options.** Don't just flag a trade-off - present the options and your recommendation. User should be able to decide quickly.

**Include cleanup task.** Always end with "Delete this file when complete" so defer files don't accumulate.