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. **A run never opens a red PR** (ADR-0020). If the typecheck or a test fails, the skill diagnoses and retries up to 3 times; if it still fails — or if the failure means the **app** contradicts an AC rather than the generated code being wrong — it reports what it found and opens nothing. ## 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. Or read the ticket from a local file instead of Jira — same pipeline, no Atlassian connection needed: > Use the from-issue skill with --from-file tickets/SW-901-inventory-cart-badge.md Jira stays the real ticket source (ADR-0011); a file is for exercising the pipeline and for testing changes to this skill without burning a real ticket. It is a **rehearsal, not a delivery path**: the run generates, typechecks and executes the tests, then stops — no branch, no commit, no PR and no TCMS records (ADR-0026). A file-sourced run never claims a Jira URL it did not read. See `references/workflow.md` St