decisionlisted

# Decision ## Why this skill exists After a long stretch of work — or when reading a GitHub issue full of open questions — the user is handed either a wall of prose ("I did X, Y, Z... let me know what you think about the auth approach") or nothing at all, and has to reconstruct the actual choice themselves. This skill's only job is to close that gap: take whatever decision is pending, strip it down to plain language, and hand it back as an **explicit numbered menu** — never as freeform prose the user has to parse and reply to in kind. The *menu* is the contract. The *mechanism* that renders it is a platform detail. ## Validation tier Tier 0 (edit-time). This skill runs no repository validation and makes no commits. ## Resolve the interaction mechanism (do this first) Read `core/capabilities/platforms.json` and look up `ask_user_question` for the current platform. | `ask_user_question` status | Mechanism | |---|---| | `native` / `native-experimental` | Call the **AskUserQuestion** tool. Preferred — it renders a real picker and captures a structured answer. | | `partial` / `emulated` / `adapter` | Use the tool if it is actually present in this session; otherwise fall back to the numbered-options block below. | | `unsupported` / `unknown` / registry unreadable | Use the **numbered-options fallback**. Do not announce a missing feature; just render the menu. | Cheap runtime check when the registry cannot be read: if the `AskUserQuestion` tool is listed in this session's t