---
name: 8_gofer_resume
description: Resume a previous Gofer session from a saved checkpoint file.
agent: copilot-workspace
tools:
  - Read
  - Grep
  - Glob
  - Bash
  - WebSearch
argument-hint: feature-name-or-description
gofer:
  workflowProfile: standard
  canonicalSource: .specify/commands/8_gofer_resume.md
  canonicalChecksum: 2325722f9d9d2d97a83849b36b8d2e450c9d1a89cc061739435e4457886d5878
  metadataSource: scripts/generate-commands.ts
---

## Workspace Preflight

Before doing stage/helper work:

1. Resolve the repository root.
2. Check the core Gofer sentinels:
   - `.specify/.gofer-version`
   - `.specify/commands/0_business_scenario.md`
   - `.specify/templates/spec-template.md`
   - `.specify/scripts/bash/create-new-feature.sh`
   - `.specify/scripts/node/parse-stage-command.mjs`
   - `.specify/scripts/hooks/post-tool-use.mjs`
   - `.specify/scripts/powershell/install-optional-tools.ps1`
   - `.specify/templates/gofer-model-policy.yaml`
   - `.specify/memory/gofer-model-policy.yaml`
   - `.specify/specs/`
   - `.specify/memory/`
3. Check host-specific repo-owned files when relevant:
   - Claude: `AGENTS.md`, `CLAUDE.md`, `.claude/settings.json`
   - Codex: `AGENTS.md`
   - Copilot: `.github/copilot-instructions.md`
   - VS Code extension mirrors Claude/Copilot/Gemini resources itself and should still keep the core scaffold healthy
4. If the repo already has the workspace checker script, prefer running:
   - `node .specify/scripts/node/gofer-workspace-check.mjs --host copilot --json`
5. If the workspace is missing or stale, ask exactly:
   - **"This repo is missing or stale for Gofer. Initialize/update it now?"**
6. If the user says yes, run the Gofer workspace bootstrap helper and then resume this command from the top.
7. If the user says no, stop and explain that Gofer stage/helper work depends on the repo-owned scaffold.


# Gofer Resume

## Token And Cost Policy
<!-- gofer:token-cost-policy:start -->

Before spawning agents, calling tools, or loading large files:

1. Treat `.specify/memory/gofer-model-policy.yaml` as the repo-owned source of truth for simple, medium, hard, and arbiter model routing. If it is missing, run `/gofer:bootstrap-workspace` before continuing.
2. Use the cheapest capable model first.
   - Claude: Haiku for scouting/extraction; Sonnet for normal implementation, synthesis, validation, and security; Opus for high-risk arbitration or release-critical failures.
   - Codex/OpenAI: GPT mini for simple coding; GPT nano only for locate/classify/summarize/mechanical work; GPT-5.3-Codex or flagship GPT for tool-heavy coding, architecture, and release-critical validation.
   - Gemini: Flash-Lite for cheap large-context scan/summarize; Flash for default research synthesis; Pro for large-context architecture or high-risk arbitration.
   - Copilot: prefer Auto for simple and default work; ask the user before choosing a paid/high-tier picker model for hard security, architecture, or release gates.
3. Keep raw tool output out of the main conversation context. Save stable findings to `.specify/specs/{feature}/context-bundle.md`, then work from summaries.
4. Use provider prompt/context caching only for stable, non-secret prefixes: Gofer scaffold, AGENTS/CLAUDE/Copilot instructions, constitution, repo map, stage contracts, and validation rubric.
5. Before continuing after large research, planning, implementation, or validation bursts, checkpoint the durable artifacts and compact/clear/resume context when the host supports it.
6. Escalate model tier only when a cheaper pass is low-confidence, contradictory, security-sensitive, or blocking release quality.
<!-- gofer:token-cost-policy:end -->

## User Input

```text
$ARGUMENTS
```

You **MUST** consider the user input before proceeding (if not empty).

---

## When to Use This Command

- Returning to a previously paused feature
- Starting a new session on existing work
- Switching back to a saved task
- Recovering from an interrupted session
- After context window compaction

---

## Step 1: Discover Saved State

### 1.1 Check for Session Checkpoints

```bash
# Find all session checkpoints
find .specify/specs -name "session-checkpoint.md" -type f 2>/dev/null

# List features with their status
for dir in .specify/specs/*/; do
  if [ -f "$dir/session-checkpoint.md" ]; then
    echo "PAUSED: $dir"
  elif [ -f "$dir/tasks.md" ]; then
    echo "IN_PROGRESS: $dir"
  fi
done
```

### 1.2 Present Options to User

If multiple sessions found:

```markdown
## Saved Sessions Found

| Feature     | Stage       | Last Saved       | Tasks Done |
| ----------- | ----------- | ---------------- | ---------- |
| [feature-1] | 5_implement | 2026-01-13 14:30 | 12/25      |
| [feature-2] | 3_plan      | 2026-01-12 09:15 | 0/0        |

Which feature would you like to resume?
```

Use AskUserQuestion tool if needed.

### 1.3 If No Checkpoint Found

Check for features with uncompleted tasks:

```bash
# Find tasks.md files with unchecked items
grep -l "\- \[ \]" .specify/specs/*/tasks.md 2>/dev/null
```

If found, offer to resume from tasks.md directly.

---

## Step 2: Load Session Context

Once feature is identified, read in this order:

### 2.1 Session Checkpoint (Primary)

```bash
Read: {FEATURE_DIR}/session-checkpoint.md
```

Extract from YAML frontmatter:

- `stage`: Which pipeline stage was active
- `last_commit`: Where code was at save time
- `context_usage`: How much context was used

### 2.2 Feature Artifacts

```bash
Read: {FEATURE_DIR}/tasks.md      # Current task list
Read: {FEATURE_DIR}/plan.md       # Architecture context
Read: {FEATURE_DIR}/spec.md       # Requirements (if needed)
Read: {FEATURE_DIR}/research.md   # Technical context (if needed)
```

### 2.3 Git State

```bash
# Verify we're on the right branch
git branch --show-current

# Check for changes since checkpoint
git log --oneline [last_commit]..HEAD

# Check for uncommitted changes
git status
```

---

## Step 3: Validate Resumption State

### 3.1 Check Code State

```bash
# Verify build still works
npm run build 2>&1 | tail -20

# Check if tests pass
npm test 2>&1 | tail -20
```

### 3.2 Check for Conflicts

If codebase changed since checkpoint:

1. **Review changes** to files we were modifying
2. **Check for conflicts** with our work
3. **Update plan** if architecture evolved
4. **Warn user** of any impacts

```markdown
## Changes Since Last Session

- **New commits**: [list commits since checkpoint]
- **Modified files**: [files that affect our work]
- **Potential conflicts**: [any issues detected]
```

### 3.3 Restore Working State

```bash
# Apply any stashed changes (if mentioned in checkpoint)
git stash list
git stash pop stash@{n}  # if applicable
```

---

## Step 4: Rebuild Mental Model

Create a context summary for the conversation:

```markdown
## Resuming: [Feature Name]

### Where We Left Off

- **Stage**: [Pipeline stage from checkpoint]
- **Current Task**: [Task ID] - [Description]
- **File**: `path/to/file.ts:line`
- **What was happening**: [From checkpoint notes]

### Key Context

From checkpoint:

- [Key decision 1]
- [Key decision 2]
- [Gotcha to remember]

### Protected Files (Do Not Modify)

- [List from checkpoint]

### Immediate Next Steps

1. [Continue task X at line Y]
2. [Then task Z]
3. [Phase completion verification]
```

---

## Step 5: Restore Todo List

Load the task state into TodoWrite:

```
Based on tasks.md and checkpoint:
- Mark completed tasks
- Set current task as in_progress
- Queue remaining tasks as pending
```

---

## Step 6: Signal Ready to Continue

```markdown
================================================================ CONTEXT
RESTORED: [Feature Name]
================================================================

Resuming from: [checkpoint timestamp] Branch: [branch name] Stage: [pipeline
stage]

Progress:

- Tasks completed: [X]/[Total]
- Current phase: [Phase name]
- Current task: [Task ID] - [Description]

Files to focus on:

- [Current file from checkpoint]
- [Next file in task list]

Code Status:

- Build: [passing/failing]
- Tests: [passing/failing/skipped]
- Changes since save: [N commits]

Ready to continue with: #5_gofer_implement

Or I can pick up exactly where we left off...

================================================================
```

---

## Step 7: Continue Implementation

Based on checkpoint state, either:

### Option A: Auto-Continue

If user says "continue" or similar:

1. Load the current task details
2. Open the file at the saved location
3. Continue implementing from that point
4. Follow normal `#5_gofer_implement` flow

### Option B: Manual Navigation

If user wants to review first:

1. Show task list with current position
2. Let user choose where to start
3. Proceed with their selection

---

## Resume Patterns

### Pattern 1: Quick Resume (Same Day)

```
#8_gofer_resume

> Continue the user management feature from this morning

# Claude:
1. Finds most recent checkpoint
2. Loads task context
3. Continues from exact stopping point
```

### Pattern 2: Full Context Restore (Days Later)

```
#8_gofer_resume .specify/specs/auth-feature/

# Claude:
1. Reads full checkpoint
2. Reviews git history since then
3. Checks for conflicts
4. Rebuilds complete context
5. Presents summary before continuing
```

### Pattern 3: Recovery Mode (No Checkpoint)

```
#8_gofer_resume

# Claude:
1. No checkpoint found
2. Finds features with incomplete tasks
3. Presents options to user
4. Resumes from tasks.md state
```

---

## Error Handling

### Checkpoint Not Found

```markdown
No session checkpoint found.

I found these features with incomplete tasks:

- `.specify/specs/feature-a/` - 5/20 tasks done
- `.specify/specs/feature-b/` - 15/30 tasks done

Which would you like to continue?
```

### Git State Mismatch

```markdown
Warning: Code has changed since checkpoint.

- Checkpoint commit: [hash]
- Current HEAD: [hash]
- Changes: [N commits]

Files we were working on have been modified:

- `src/service.ts` - [changed by commit X]

Options:

1. Review changes and continue
2. Reset to checkpoint state
3. Start fresh with current code
```

### Build Broken

```markdown
Warning: Build is currently failing.

Error:
```

[build error output]

```

This may have been caused by:
1. Changes since checkpoint
2. Missing dependencies
3. Incomplete work at save time

Would you like me to:
1. Try to fix the build issues first
2. Continue anyway and fix as we go
3. Roll back to last working state
```

---

## Observability Logging

```bash
.specify/scripts/bash/log-stage.sh 8_resume --complete --tokens [N] --compactions [N]
```

---

## Integration

This command works with:

- `#7_gofer_save` - Paired save command
- `#5_gofer_implement` - Continues implementation
- `#0_business_scenario` - Can route to resume
- All other Gofer commands - Can be invoked after resume

---

## Best Practices

### Before Resuming

- Always check git state first
- Verify build/tests pass
- Review any changes since checkpoint

### After Resuming

- Verify context is complete
- Run a quick validation
- Update checkpoint if state changed

### For Long-Running Features

- Save checkpoints frequently
- Include mental model notes
- Document non-obvious decisions
