writing-qa-test-instructionslisted

# Writing QA Test Instructions This skill is the **single source of truth** for the handover from development to manual QA. It answers two questions, in this order: 1. **Is this ticket manually testable by a non-developer at all?** — the testability classification. 2. **If yes: what exactly does the tester do?** — the German test instructions posted as a Linear comment. > **Goal:** A ticket only reaches a manual-testing column when someone who has never seen the code can pick it up and verify it from the ticket alone. Everything else is routed past QA rather than parked there half-documented. ## When to Use This Skill | Caller | Phase | What it needs from here | |--------|-------|-------------------------| | `/lt-dev:ticket-cycle` | STEP 4b.1b + 4b.3c | Classification (drives the post-merge Linear state) + the posted comment | | `/lt-dev:git:ship` | STEP 10c | The comment format for the post-merge Linear comment | | `/lt-dev:dev-submit` | STEP 3 | The comment format for the reviewer-handoff Linear comment | `ticket-cycle` is the only caller that lets the classification **change the ticket's target state**. For `git:ship` and `dev-submit` the classification only decides which of the two comment shapes gets posted — those commands transition to "Dev Review" either way. ## Part 1 — Is the ticket QA-testable? A ticket is **QA-testable** when all three hold: - **Reachable surface** — there is at least one screen, route, or API response a non-developer can reach through th