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 menu via the built-in **AskUserQuestion** tool — never as freeform prose the user has to parse and reply to in kind. ## Resolve the input 1. **Argument looks like a GitHub issue/PR** — a bare number (`57`, `#57`) or a GitHub URL containing `/issues/` or `/pull/`: ```bash # Infer owner/repo from the URL, or from the current repo if none is given gh issue view <number> --json title,body,comments,url -R <owner/repo> ``` If that 404s, or the URL/context says `/pull/`, retry with `gh pr view` instead. If no repo can be inferred (not inside a git checkout, ambiguous), ask the user which repo before fetching. 2. **Argument is non-empty text** — treat it as a topic/description, not a literal ID. Search the current conversation for the decision it best matches. Numbers like "141" in a user's example phrasing are illustrative, not a real numbering scheme to look up — match on content, not on the digits. 3. **No argument** — scan the whole current conversation for every unresolved decision or action item (places where wor