"Use when the owner needs to rule on open decisions — asking what is waiting on them, returning from time away, or when undelivered calls have piled up. Sweeps the standing-proposals collector, open parks, and in-session pending items and delivers batch 1 (decisions blocking the advisor, never new-issue filings) as numbered chat prose. Not routing, vetting, or building."
Install
npx skillscat add zwrose/superheroes/discuss-open-decisions Install via the SkillsCat registry.
This skill speaks in host-neutral actions. Resolve them to your runtime's tools by reading the host tool map at ${CLAUDE_PLUGIN_ROOT}/hosts/<your-host>-tools.md (the leading variable is this plugin's root directory) — claude-tools.md on Claude Code, codex-tools.md on Codex.
discuss-open-decisions
Owner-invoked on-demand delivery of open owner decisions. Reach for /superheroes:discuss-open-decisions when returning from time away, when undelivered calls may have piled up, or when you want every open decision walked through now.
This skill is deliberately not the only path. The showrunner advisor delivers owner decisions as a standing duty without waiting for this invocation.
Invocation
| Form | Behavior |
|---|---|
/superheroes:discuss-open-decisions |
Read the owner-decisions contract from disk, sweep the three bounded sources, filter, deliver batch 1, pause for batch-1 rulings, deliver batch 2, execute what batch 1 unblocked alongside batch-2 rulings, then send batch 3 — one sheet per PR — and close with the recap. Three batches, always in that order. Works in a showrunner charter or any session where the owner explicitly invokes it. |
Step 1 — Read the contract
Read ${CLAUDE_PLUGIN_ROOT}/skills/showrunner/reference/owner-decisions.md from disk — first action, every invocation.
When this session is not already running the showrunner charter, also read duties 4 and 5 in skills/showrunner/SKILL.md — duty 4 for the collector this skill sweeps and strikes, duty 5 for the presentation call; whether an item is the owner's is sorted by the owner-vs-craft line, which the contract's filter cites.
This skill executes the contract at delivery time rather than carrying it.
If the file is missing, stop and report — never substitute prose from this skill or from memory.
Step 2 — Sweep
Gather candidate items per ## Where the items come from, and the bound on that sweep.
Refresh the collector preamble per ## The collector preamble — canonical snippet when it has drifted or is missing.
Read the project's revisit-trigger registry per ## The revisit-trigger registry before proposing a decline, so a decline already ruled on is cited rather than re-argued.
Resolve the collector's issue pointer from the advisor's durable memory (showrunner duty 4); when the pointer cannot be resolved, ask the owner for the issue number and never open a second collector; record the pointer once found.
Read the collector before searching parks — it is authoritative and may already subsume an in-session duplicate.
Step 3 — Filter
Apply ## The filter — what is the owner's, and on what grounds; present filtered items per that section before batch 1.
For each owner call that will be delivered in batch 1 or batch 2, apply ## The front door and ## The venue ladder and append it to the collector immediately, before it is proposed in this session's delivery message. This skill is owner-present by construction; the canonical append-always rule lives in skills/showrunner/reference/owner-decisions.md, and this skill applies it at delivery time rather than at vet time.
Step 4 — Deliver batch 1
Each batch-1 item has already been graded at the door and been appended per Step 3.
Deliver per ## Delivery mechanics, ## The per-item spine, and ## Formatting — one block per spine section; write the numbered batch-1 list to a durable artifact now — the collector entry where the item has one, otherwise a durable note on the issue or PR it belongs to — and resume from that record, not session memory.
Batch 1 goes in the chat with a link to the index, whose top carries the same questions. The first-answer rule and the disagreement rule are owner-decisions.md's, in ## Delivery mechanics.
Step 5 — Pause for rulings
Stop here and wait. Rulings may land in the chat or on the index; record each to the durable artifact as it lands, per the first-answer and disagreement rules in ## Delivery mechanics.
If batch 1 is empty after filtering, skip to Step 6 per ## Delivery mechanics.
When a ruling closes or declines a collector-backed item, strike it from the collector per showrunner duty 4.
Partial batch-1 answers still block batch-1 execution for the items left unanswered.
Step 6 — Deliver batch 2
Deliver batch 2 as soon as batch-1 rulings land — batch-1 execution runs alongside batch-2 rulings, not ahead of them. Each batch-2 item is graded at the door and is appended per Step 3 immediately before it is added to the durable numbered list and presented — per ## Delivery mechanics, ## The per-item spine, and ## Formatting — one block per spine section. No batch-2 item concerns one specific PR, per ## Delivery mechanics.
Step 7 — Execute what the rulings unblocked
Execute what batch 1 unblocked per ## What batch-1 execution may and may not do while the owner rules on batch 2; receipt what you executed, in plain language.
Record each batch-2 ruling to the durable artifact as it lands, then execute what that ruling unblocked — under the same section — before this step is done.
When a batch-2 ruling closes or declines a collector-backed item, strike it from the collector per showrunner duty 4.
Step 8 — Send batch 3, the PR sheets
Only once every batch-2 ruling has landed and what those rulings unblocked has been executed in Step 7 — a ruling routinely sends a vetted PR back, so a sheet built before that execution can describe a PR that is no longer mergeable. That is why this batch is built last rather than earlier.
Send one sheet per PR still mergeable, after walking each sheet's stops, per ## Delivery mechanics. Read a sheet's answers only after the owner says "done". What the answers commit, and the merge word, are ## Delivery mechanics' and showrunner duty 6's; merge, release, publish, and force-push stay outside what you execute on a ruling, per ## What batch-1 execution may and may not do.
Step 9 — Close with the recap
Close the sitting with the "what I decided for you" recap per ## Delivery mechanics — unless this sitting already opened with it.
When you're tempted
| Excuse | Reality |
|---|---|
| "I'll deliver everything in one batch" | see ## Delivery mechanics |
| "Structured questions will be clearer than chat prose" | see ## Delivery mechanics |
| "That item isn't really the owner's — I'll skip it" | see ## The filter — what is the owner's, and on what grounds |
| "I'll renumber for clarity in batch 2" | see ## Delivery mechanics |
| "The contract is long — I'll work from what I remember" | Step 1 reads the file every invocation. |
| "I'll deliver batch 2 after execution finishes" | see ## Delivery mechanics |
| "The numbers live in the chat — I'll remember" | see Step 4 |
| "I'll build the PR sheets up front so they're ready" | see ## Delivery mechanics — a batch-1 or batch-2 ruling routinely sends a PR back; batch 3 is built after Step 7. |
| "The owner saved Merge, so I can merge" | see ## Delivery mechanics and showrunner duty 6 — nothing on a sheet is acted on before "done", and the word is the saved "Merge" verdict plus "done". |
| "I decided those myself, so there's nothing to report" | see ## Craft calls and owner calls and ## Delivery mechanics |
| "I'll append follow-ups to the collector — the owner can review them later" | see ## The front door, ## The venue ladder, showrunner duty 4, and skills/showrunner/reference/owner-decisions.md — every owner call is appended before it is proposed in this session's delivery message and discussed now. |