briefs-donelisted

# Briefs: Close Out a Task (or Checkpoint It) The completion ceremony. `/briefs-work` sessions may tick every checkbox, but a task only *finishes* here — deliberately, after the user has reviewed the work. This skill is the **only** writer of PROGRESS.md. Two modes: - **Close-out** (default): the whole task is done — review, archive, reset. - **Checkpoint**: a reviewed-and-committed slice mid-task (e.g. the backend half before the frontend starts). Same review + PROGRESS entry, but CURRENT.md stays active and nothing is reset. Worth running on a strong model: step 2 is a review pass where plan-aware intelligence catches what the executing model missed. ## Step 1: Preconditions and mode Find the briefs folder (`.claude/briefs-path` → `.briefs/` → ask). Read CURRENT.md. If the folder has a PLAN.md but no BACKLOG.md, it predates the rename — treat PLAN.md as BACKLOG.md and offer to `mv` it. - No active task → say so, done. - If code was written, ask for the commit SHA(s) — or offer to read them from `git log` and confirm with the user. **If the work isn't committed yet, stop:** "Review and commit first, then rerun `/briefs-done`." The commit is the proof the user actually looked at it; no SHA, no archive. (Non-code tasks — docs, research, ops — skip this gate; instead confirm the user has seen the result.) - **Pick the mode.** If the user said "checkpoint" (or gave a SHA for a subtask), it's a checkpoint. If `# Task list` still has unchecked items, ask: "Ta