create-issuelisted

## Prerequisites If `$ARGUMENTS` is empty, ask the user to describe their user story, bug report, or feature idea before proceeding. ## Core principle **An issue is the output of resolved decisions — not a place to park unresolved ones.** Every decision a developer would otherwise have to guess at MUST be resolved by asking the user *before* the issue is written. Whatever the user genuinely will not or cannot resolve goes into one explicit **Blocked** section — never disguised as an "option", a "recommended approach", an "Open Question", a default, or conditional wording scattered through the body. Listing options in the issue body is the failure this skill exists to prevent. ## Completion checklist (do this first) This skill is a **pipeline that ends with a created GitHub issue and an offer to start implementation** — not with a documentation report. Before doing anything else, create a TodoWrite todo list with exactly these items: 1. Run `/docs-verify --report-only` and capture its findings report 2. Clarify the user story until the **Definition of Ready** is met (Step 2) 3. Draft the issue and pass the **no-options gate** (Step 3) 4. Present the rendered issue, get the user's explicit confirmation, then create it (Step 4, sub-steps 1–5) 5. After creation succeeds, offer to start implementation (Step 4, sub-step 6) Mark each todo `in_progress` when you start and `completed` only when done. **The issue is created only after the user explicitly confirms the rendered d