acceptance-test-planlisted

## What this skill does Produces a traceable acceptance test plan with individually numbered test cases. Each test case maps to a source requirement (user story, use case, or FR), specifies preconditions, steps, and expected results, and includes coverage of the happy path, edge cases, and negative scenarios. ## When to use it - User asks to "write a test plan", "create acceptance tests", or "define test cases" for a feature or system. - A sprint is nearing completion and the team needs acceptance criteria turned into formal tests. - A stakeholder or client needs documented evidence that acceptance criteria have been verified. - User is preparing for UAT (User Acceptance Testing) and needs a test script. - Use cases or functional requirements from a `requirements-document` need test coverage. ## Key concepts ### Test case anatomy | Field | Description | | --- | --- | | **ID** | Unique identifier (TC-NNN) | | **Title** | Short description of what is being tested | | **Source** | The story, use case, or FR this test covers | | **Type** | Happy path / Edge case / Negative / Performance / Security | | **Priority** | Critical / High / Medium / Low | | **Preconditions** | State the system must be in before the test starts | | **Test steps** | Numbered actions the tester performs | | **Expected result** | What should happen if the system behaves correctly | | **Pass / Fail** | To be filled in during test execution | ### Coverage types | Type | Purpose | | --- | --- | | **Hap