What problem does it solve? Decision cards with vague "Pending:" tails rot instead of resolving because they lack a typed question and a typed output. This Skill turns each card into an explicit contract — one exact question in, one of three outcomes out — so decisions actually close instead of lingering. ## Core Features & Use Cases - Typed decision contracts: Every card gets a single answerable question (yes/no, a number, or a named choice) and exactly one output: a ruling, a spawned work item, or a partially unblocked card. - One-card-at-a-time sessions: Pulls candidates from a worklist's "Needs ruling" section or reconcile-flagged pending tails, then walks them individually with a recommendation rather than a menu of options. - Immediate outcome application: Rulings are written to a decisions log, spawned work items are opened and linked, and unblocked cards note which dependency was removed — all applied immediately, never batched. - Use Case: Your project worklist has five cards stuck under "## Needs ruling". Run a sequence session to state each question, get a decision, record the ruling in docs/decisions.md, and end with a summary of how many were ruled, spawned, unblocked, or left open. ## Quick Start Ask the assistant to walk the decision cards in the worklist's "Needs ruling" section and resolve each one to a ruling, a spawned work item, or an unblocked card.