What problem does it solve? Formal QA governance requires a structured Test Plan that groups test cases, establishes traceability to acceptance criteria, and documents scope, resources, and risks — but writing one manually for each TMS (Jira Xray, Jira Native, Azure DevOps, Notion) is slow and inconsistent. This Skill automates the creation of ISO/IEC/IEEE 29119-compliant Test Plans and derives manual test cases from acceptance criteria. ## Core Features & Use Cases - ISTQB 10-Section Test Plans: Generates Identification, Scope, Objectives, Approach, Resources, Schedule, Test Items, Deliverables, Entry/Exit Criteria, and Risks as a single YAML artifact exportable to any TMS. - Manual Test Case Design: Derives 1:N test cases per acceptance criterion using Equivalence Partitioning, Boundary Value Analysis, State-Transition, Decision Table, and Pairwise techniques, with Candidate/Manual/Deferred classification. - TMS-Agnostic Export: Adapters translate the same YAML into Jira Xray Test Plans, Jira native issues, Azure DevOps Test Plan objects, or Notion database entries; fictional user stories are cached locally and migrate to a real TMS later. - Use Case: A QA lead needs a master Test Plan for an authentication module spanning three Jira stories. The skill gathers scope and risks interactively, designs 18 test cases, links 6 existing TCs from test-documentation, and publishes the plan to Jira Xray with a full AC-to-TC-to-Risk traceability matrix. ## Quick Start Run the test-planning skill with a Jira story key like PROJ-123 to interactively build and publish a formal Test Plan.
