What problem does it solve? When a Playwright test fails, manually investigating the root cause, reproducing the failure, and writing a complete Jira bug ticket with evidence is slow and error-prone. This Skill automates the full failure-to-ticket workflow so every defect is documented consistently with screenshots attached. ## Core Features & Use Cases - Failure Analysis and Reproduction: Parses Playwright error output, re-runs the failing test with --workers=1 and --repeat-each=2 to confirm reproducibility, and collects failure screenshots via helper scripts. - Structured Jira Sub-task Creation: Creates Sub-tasks under the correct parent DS story via the Atlassian MCP, with a Taya [Composer] summary prefix, severity/priority mapping, and a full markdown bug report template. - Duplicate Detection and Mandatory Evidence: Searches Jira with JQL before creating tickets to avoid duplicates, and attaches screenshots using scripts/jira-attach-screenshots.mjs since MCP cannot upload files. - Use Case: A regression run fails on DS-2.spec.ts because the program list shows stale data after an edit. The Skill reproduces the failure, checks for an existing sub-task, drafts the report, creates the Jira sub-task under DS-2, and attaches the failure screenshot. ## Quick Start Investigate the failing Playwright test in DS-2.spec.ts, reproduce it, and file a Jira bug sub-task with the failure screenshots attached.
