writing-qa-test-instructions
Installation
SKILL.md
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:
- Is this ticket manually testable by a non-developer at all? — the testability classification.
- 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 3b + 4b.1 + 4b.3c | The test context on dev (accounts, records) while the developer is present, the classification (decides which post-merge states the user is even offered), and the posted comment, completed once the deploy is healthy |
/lt-dev:git:ship |
STEP 10c | The test context (Part 4) and the comment format for the post-merge Linear comment |
/lt-dev:dev-submit |
STEP 3 | The test context (Part 4) and the comment format for the reviewer-handoff Linear comment |
ticket-cycle is the only caller that lets the classification decide which target states the user is offered. 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.