from-issuelisted

# from-issue Given a Jira issue key (e.g. `SW-123`), this skill reads the ticket via the Atlassian MCP, normalizes its requirement in whatever form it was written (narrative, Given/When/Then, bullet ACs, prose, or mixed), generates a set of Playwright tests, runs them locally, and opens a GitHub PR with a structured description. The PR is the review gate, and the GitHub-for-Jira app auto-links it onto the ticket. See [ADR-0011](../../../docs/adr/0011-jira-ticket-source.md). ## How to use it Tell Claude what you want: > Use the from-issue skill on SW-123. Or for experimentation (skip push/PR): > Use the from-issue skill on SW-123 with dry-run. If the ticket's feature already has a generated spec, the skill **augments** that file (adds the new tests, and adds/modifies the Page Object as needed) instead of creating a new file — see [ADR-0010](../../../docs/adr/0010-from-issue-augment-mode.md). Re-running any ticket that already contributed to the file refuses. To force a separate file instead of augmenting: > Use the from-issue skill on SW-123 with --new-file. ## 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) for the Step 2 ticket read — defined at project scope in [`.mcp.json`](../../../.mcp.json). Its read tools (`mcp__atlassian__getAccessibleAtlassianResources`, `mcp__atlassian__getJiraIssue`) are pre-authorized i