Skip to content

TFW Resume — Phase Status Bootstrap

Role: Coordinator (new or returning) Output: Phase status matrix + recommendation for next phase When to use: Starting a new session for a multi-phase task, or returning after a break

🔒 ROLE LOCK: COORDINATOR This workflow runs in Coordinator mode ONLY. Permitted actions: read artifacts, build status matrix, write Phase HL + TS. Forbidden actions: execution, writing ONB, writing RF, writing code.

Context loading: verify conventions.md §10 core context is loaded before proceeding.

Phase 1: Locate Task

  1. User specifies task folder path (e.g. tasks/PROJ-3__admin_ui/)
  2. List the task folder contents — identify Master HL, Master TS, and all phase artifacts
  3. Read Master HL — extract:
  4. Vision (section 1) — one-liner
  5. Phase list (section 4) — all planned phases with priorities
  6. Design principles (section 7) — non-negotiable rules

  7. Strategic Insights (section 11) — check for gaps from previous session

  8. Read Master TS (if exists) — extract:

  9. Phase definitions and scope budgets
  10. Quality contract (anti-patterns, style rules)
  11. Verification plan

Phase 2: Build Status Matrix

  1. Scan folder for HL__Phase*, TS__Phase*, ONB__Phase*, RF__Phase*, REVIEW__Phase* files
  2. Build matrix and present:
## Phase Status Matrix

| Phase | Description | HL | TS | ONB | RF | REVIEW | Status |
|-------|-------------|----|----|-----|----|----|--------|
| A | Backend: API endpoints | ✅ | ✅ | ✅ | ✅ | ✅ APPROVED | ✅ Done |
| B | Frontend: components | ❌ | ❌ | ❌ | ❌ | ❌ | ⬜ Next |
| C | Integration tests | ❌ | ❌ | ❌ | ❌ | ❌ | ⬜ TODO |
  1. If the last completed phase has a REVIEW file — read it, extract:
  2. Verdict (APPROVED / REVISE / REJECT)
  3. Key lessons or issues found
  4. Tech debt items collected
  5. If a REVISE verdict exists for any phase — flag it as needing re-execution
  6. Read TECH_DEBT.md — extract accumulated items across phases

Phase 3: Report & Decide

  1. Present structured status report to user:
## Resume Report — {PREFIX}-{N}

**Task**: [title from Master HL]
**Progress**: X of Y phases complete

### Completed
- Phase A: [one-line summary] ✅ [REVIEW verdict]
- Phase B: [one-line summary] ✅ [REVIEW verdict]

### Lessons from Last Phase
- [extracted from REVIEW]

### Tech Debt Accumulated
- [summary from TECH_DEBT.md]

### Next Phase
**Phase C**: [description from Master HL]
- Scope: [N files, brief]
- Dependencies: [any blockers from previous phases]
  1. Ask user: "Start planning Phase C?" or "Which phase to work on?"

After User Confirms

  1. Use plan workflow Phase 4 flow (large task path) to write HL+TS for the chosen phase
  2. Present HL+TS for user approval
  3. After approval → use handoff workflow to delegate to executor agent
  4. After RF → use review workflow (/tfw-review) for review

Anti-patterns

  • Skip reading Master HL/TS and jump straight to writing phase TS
  • Read all RF files in full (only read REVIEW summaries — RF is for executors)
  • Start planning without showing the status matrix first
  • Assume phase order is fixed — user may want to skip or reorder
  • Ignore TECH_DEBT.md items from previous phases
  • Ignore accumulated tech debt when planning next phase scope