next-stepslisted

# Next Steps — Stakeholder Alignment Checklist ## What it does Reads the current conversation (and optional connected context: Linear, Slack thread, Notion doc, git/PR state) and produces **one consolidated checklist of next steps grouped by owner**, ranked by priority, with explicit dependencies and open questions. Designed to be pasted into a Slack thread, a Linear comment, or a Notion update so everyone sees the same picture. The point isn't to enumerate every possible task — it's to surface what *unblocks the next move forward*, so multiple stakeholders can self-serve. ## When to use - After a working session, before posting a status update. - When a Slack/Linear thread has multiple unresolved threads — you need to consolidate. - When the user says things like *"so what are next steps"*, *"align everyone on next items"*, *"summarise what each person owes"*. Do NOT use this for: timesheet recaps (use `/workday-summary`), retrospective status posts (use `/project-updates`), or commit-by-commit breakdowns. ## Inputs Required: - **The current Claude conversation** — the primary signal. The model already has this in context. Optional (from the `scope-hint` arg or follow-up questions): - A **Linear ticket ID** (e.g. `ENG-1234`) — fetch via `mcp__linear-server__get_issue` to anchor scope and check current state/assignee. - A **PR number** (e.g. `#822`) — fetch via `gh pr view` for state, reviewers, blocking checks. - A **Slack thread permalink** — read via Slack M