What problem does it solve? Teams that validate behavior during sprints often lose that knowledge because test cases never reach the test management system, leaving no regression repository and broken traceability between stories, test plans, and test cases. This Skill formalizes already-validated scenarios into TMS artifacts (Test Cases, Acceptance Test Plans, Test Sets, Test Executions) with correct naming, prioritization, and link structure. ## Core Features & Use Cases - Analyze, Prioritize, Document pipeline: Derives test cases from acceptance criteria using EP, BVA, state-transition, decision-table, and pairwise techniques, then applies an ROI formula to classify each as Candidate, Manual, or Deferred before writing anything to the TMS. - Multi-modality TMS support: Resolves whether the project uses Jira with Xray, Jira-native, Notion, or Azure DevOps, and adapts artifact containers, membership semantics, and linking rules accordingly. - Repair-traceability mode: Audits an existing Story-ATS-ATP-ATR-TC cascade, presents a fix plan, waits for explicit approval, then repairs broken links and verifies coverage. - Use Case: After a story is QA-approved, invoke the skill with the story key to create the mandatory ATS, link the ATP and ATR, and persist only regression-worthy test cases with Gherkin specifications and automation verdicts. ## Quick Start Ask the agent to document the validated test scenarios for a specific Jira story key, for example by requesting that it analyze and document test cases in the TMS for PROJ-123.
