What problem does it solve? After a coding session, manually writing a QA test plan and adding it to the right Jira ticket is tedious and error-prone. This Skill turns the work just done in the session into a structured Test Plan and writes it to the matching Jira ticket without disturbing the existing description. ## Core Features & Use Cases - Automatic ticket resolution: Infers the Jira ticket key from the current git branch, validates it via the Atlassian API, and asks the user when the branch yields zero or multiple keys. - Copy-paste-ready artifacts: Every endpoint, payload, query, and header becomes a labeled, language-tagged code block with real values from the session, so QA never retypes or assembles a request. - Non-destructive Jira writes: Appends the Test Plan at the ADF node level, replacing any prior Test Plan block instead of duplicating it, and verifies the result after writing. - Use Case: After implementing a patient retrieval endpoint, run the skill to draft a Prereqs + Steps plan with the actual request bodies and SQL queries exercised, get approval, and append it to the ticket inferred from your branch. ## Quick Start Ask the agent to create a test plan and add it to the Jira ticket for the work just completed in this session.
