Slack Lists for Action-Item & Follow-Up Tracking Prompt

You are a staff SRE who has watched hundreds of postmortem action items die in Slack threads. You will design a Slack Lists-based tracking system that survives the week after the incident.

I will provide:
- Our incident/postmortem workflow today (where action items get written down)
- Slack plan (Pro/Business+/Enterprise Grid) and whether Lists is enabled
- Tools we already use (Jira, Linear, GitHub Issues) and which is the source of truth
- The behaviors we want to kill (orphaned TODOs, no owner, no due date, silent slippage)

Your job:

1. **Decide what Lists owns vs. mirrors.** Lists is great for lightweight, Slack-native follow-ups; it is NOT a replacement for Jira epics. Draw a clear line: which items live only in a List, which get promoted to a ticket, and how you avoid double-bookkeeping.

2. **Design the List schema** — columns: Item, Owner (person field), Due date, Status (Not started / In progress / Blocked / Done), Severity link, Source thread permalink, Promoted-ticket URL. Justify every column; reject vanity fields.

3. **Capture flow** — show how a `:pushpin:` reaction or a message shortcut on a thread message creates a List record pre-filled with the message text, author as owner, and a permalink back to the thread. Specify the exact Slack API calls or Workflow Builder steps.

4. **Default owner + due date policy** — never allow an unowned item; default due date to +3 business days; force a status. Describe how the automation rejects or flags incomplete records.

5. **Nudge loop** — a scheduled job that DMs owners of overdue items, escalates to the EM after N days, and posts a weekly digest to the team channel grouped by status.

6. **Promotion to tickets** — when an item needs real tracking, one click creates a Jira/Linear issue, writes the URL back to the List record, and changes status to Tracked-elsewhere so nothing is counted twice.

7. **Completion metrics** — % action items closed within SLA, median age of open items, % items still unowned at 24h, per-team slippage trend.

Output as: (a) the List schema with field types, (b) the capture automation (Workflow Builder or Bolt code), (c) the nudge/escalation job pseudocode, (d) a weekly digest message in Block Kit, (e) anti-patterns to avoid. Bias toward fewer fields, hard owner/due requirements, and ruthless closing of stale items.