the skill

Resume Project

Use when resuming work on a project after a break, a /clear, or a fresh session — when the user says "resume", "pick up", "where were we", "what's next on this project", or invokes /resume-project.

Overview

Rebuild working context from the project's own records and deliver a short briefing. The deliverable of this skill is the briefing itself, not resumed work.

Sources, in trust order

  1. .superpowers/sdd/progress.md — the ledger is authoritative when present.
  2. Git state: git log --oneline -10, git status, current branch. If the ledger and git disagree, say so explicitly; git reflects reality.
  3. The project's memory topic file (found via the MEMORY.md index) for gotchas and decisions. Index one-liners go stale; trust the dated topic file and the ledger over the index summary.
  4. Latest files in docs/superpowers/{specs,plans}/ when the ledger references them.

Briefing shape (this is the whole output)

  • Where we are: branch, tip, tasks done and remaining, one sentence.
  • Next: the single next task according to the ledger.
  • Gotchas: open landmines from the ledger or memory that bear on the next task.
  • Needs you: anything blocked on the user — keys, decisions, pending reviews.

Keep it under ten lines. No file dumps, no restated plan.

Then stop

"Resume the project" is a request for the briefing, not authorization to start the next task. Do not dispatch subagents, run task-brief scripts, or edit files until the user responds to the briefing. If the request names specific work ("resume and do Task 18"), that names the work: give the briefing, then proceed to it.