Implementation Tracker

---
name: implementation-tracker
disable-model-invocation: true
source: superpowers-plus
triggers: ["start implementation", "track implementation", "resume work on issue", "update progress", "implementation complete", "archive progress"]
description: Use when implementing large issues across multiple sessions. Creates and maintains a living progress document that tracks completed work, decisions, refinements, and findings.
summary: "Use when: implementing large issues across multiple sessions. Maintains progress doc."
coordination:
  group: engineering
  order: 1
  requires: []
  enables: []
  escalates_to: []
  internal: false
anti_triggers: ['investigate bug', 'debug issue', 'systematic debugging']
composition:
  consumes: [implementation, todo-items]
  produces: [progress-report]
  capabilities: [tracks-progress, persists-state]
  priority: 15
---

# Implementation Tracker

> **Purpose:** Maintain implementation context across sessions
> **Path:** `docs/plans/{PREFIX}-XXXX-progress.md` (git-ignored during active work)

**Announce at start:** "Using implementation-tracker to maintain progress across sessions."

## When to Use

- Implementing a large issue that will span multiple sessions
- Resuming work after a context break and needing to reload prior state
- Tracking decisions, refinements, and open questions during a multi-phase refactor
- Auditing completeness of a feature (what was planned vs. what was actually done)

---

## Triggers

| Trigger | Action |
|---------|--------|
| `writing-plans` completes | Auto-create progress doc |
| "Track implementation for {PREFIX}-XXX" | Manual creation |
| "Update progress" / milestone | Update doc + verify |
| "Resume work on {PREFIX}-XXX" | Load existing context |
| "Implementation complete" | Archive prompt |

---

## Session Resume

When existing progress doc found:

```
I found: docs/plans/{PREFIX}-1234-progress.md
Last session: aug_abc123 (2026-03-05)
Status: 3/7 tasks, 2 decisions, 1 open question
[Yes / No / Show summary first]
```

### What Carries Forward

| Facts (persist) | Fresh Each Session |
|--------------------|----------------------|
| Completed tasks, files modified | Reasoning/approach |
| Blockers, decisions, refinements | Tool call sequences |
| Open questions, key insights | Error messages |
| Wiki context | Debugging hypotheses |

---

## Verification (After Every Update)

| Order | Method | Purpose |
|-------|--------|---------|
| 1 | `git diff --name-only` | What actually changed |
| 2 | `test -f path/to/file.ts` | Files exist |
| 3 | `grep -rn "symbol" --include="*.ts"` | Symbols present |
| 4 | `tsc --noEmit` | Type errors |
| 5 | `npm test -- --filter=relevant` | Tests pass |

---

## Auto-Condense

Target: **~1,500 words**. When exceeded: move completed tasks to summary table, condense session summaries, archive resolved questions.

---

## Red Flags

- Progress doc says complete but git shows no changes
- Verification fails after update
- Doc >2,000 words without condensing
- Wiki context stale (>7 days)

---

## Companion Skills

| Skill | Relationship |
|-------|--------------|
| `writing-plans` | Chains into this skill |


## Failure Modes

| Mode | Symptom | Recovery |
|------|---------|----------|
| Scope drift | Tracking items not in original plan | Compare against plan regularly |
| False completion | Marking done without verifying behavior | Run verification after each update |
| Missing downstream | Tracking primary changes only | Check tests and docs too |