next-stepslisted

# Next Steps List every open end for the current work: next actions, open tickets, and decisions still blocking progress. ## Step 1: Build the list Scan the current session for: - Concrete next actions (code not yet written, tests not yet run, PR not yet opened). - Open tickets (Linear/GitHub issues referenced but not resolved). - Pending decisions: questions already asked and unanswered, forks/tradeoffs a subagent flagged instead of deciding, anything you were about to ask before this skill ran. - Anything else genuinely open: a running background task, a flagged risk, a leftover TODO. Exclude: - Anything already done or already answered. - Calls you can reasonably make yourself per existing conventions (CLAUDE.md, an ADR, an established pattern). - Pure physical actions only the user can do (click, type a card number, approve OAuth) — that's `human-action-needed`, not this list. Order: anything blocking a running subagent, CI, or a deploy goes first. Cosmetic/low-stakes goes last. If there are truly no open ends, say so in one line instead of forcing a list. ## Step 2: Write each item short, numbered Under one heading "Open Ends", number every item (1, 2, 3…). Each item gets exactly, on as few lines as possible: - **Title** — a few words naming it. - One-line description — the concrete file, ticket, or step. - One-line explanation of why it's open — blocked on what, or what breaks if skipped. - A short recommendation — the default to take if the user just says "go".