refine-ticketlisted

# refine-ticket Given a Jira issue key (e.g. `SW-123`), this skill reads the ticket via the Atlassian MCP, scores it against the refinement rubric, and loops — auto-resolving gaps from existing automation + docs and asking you (or a source you point it at) for the rest — until the ticket is unambiguous. On your approval it writes a `Refined Acceptance Criteria` section back to the ticket, using Jira's own rich formatting — a divider, an info panel marking the section machine-owned, and a `status` lozenge per acceptance criterion. It does NOT generate tests; run `/from-issue` after. See ADR-0013. ## How to use it Tell Claude what you want: > Use the refine-ticket skill on SW-123. Or to preview without writing to Jira: > Use the refine-ticket skill on SW-123 with dry-run. During the loop, when asked about a gap you can either answer directly or point the skill at a source ("it's in Confluence page X", a URL, a doc path). The skill ingests it and continues. It does NOT inspect a running app — it's shift-left, so it works even before the feature is built. It stops when the ticket has no open gaps, then asks before writing anything back. ## Workflow The full procedural workflow is in [`references/workflow.md`](references/workflow.md). Read that file before executing the skill. > **Setup note:** the Atlassian MCP must be connected (OAuth) with **write** scope for the Step 7 description update — defined at project scope in `.mcp.json`. Its read + write tools are pre-author