briefs-healthlisted

# Briefs: Health Check Run this when a project feels muddled, stalled, or you've lost the thread. It reads the briefs and gives you an honest picture of the state — then helps you reorder, not just report. ## Step 1: Find the briefs folder Check these in order: - Read `.claude/briefs-path` for a saved path - Check if `.briefs/` exists in the project root - If neither works, ask the user for the path ## Step 2: Read all four files in parallel CURRENT.md, BACKLOG.md, PROGRESS.md, NOTES.md — plus any staged plans in `queue/`. 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. ## Step 3: Audit each file ### CURRENT.md - Is there an active task? If empty or vague, flag it. - Does it look stale? Signs: no concrete next move, multiple tasks crammed in, "TODO" or "TBD" with no follow-up, `# Log` silent while the task claims to be in flight. - **All task-list boxes ticked but the task still active?** It's awaiting review — suggest the user review, commit, and run `/briefs-done` so it gets archived instead of rotting here. - **Non-trivial task with an empty `# Approach`?** Flag it — suggest `/briefs-plan` before more work happens ad hoc. - Is the active task actually reflected in BACKLOG.md's `## Up next` or `## Blocked`? ### BACKLOG.md - **`## Up next`**: More than 3 items? Flag it — needs pruning. Items that are actually blocked but not labeled as such? - **`## Blocked`**: Any items missing a reason or da