sumo-qa-preparing-for-worklisted

# Preparing for QA work **Announce at start:** *"Naming risks and the smallest test set."* ## Output discipline (mandatory) Inherits the global discipline from `using-sumo-qa`: **output discipline** (never surface internal taxonomy labels — say *"behaviour change in pricing"*, not *"Classification: business_logic_change"*), **output economy** (spend output on findings not framing; no preamble or self-narration; one question per turn; no closing pleasantries), knowledge authority hierarchy, internal scaffolding stays internal, and specialty-tool fit. ## The Iron Law NO TEST IDEA WITHOUT A NAMED RISK. Every test you propose ties to a specific risk you identified. ## When to Use User intents that trigger this skill: - "plan QA for this story" - "I'm starting work on X — what should I test?" - "what could break with this change?" - "QA prep for ticket ABC-123" Distinct from `sumo-qa-creating-test-plan` (formal entry/exit criteria, phases, deliverables) and from `sumo-qa-deciding-approach` (which only picks the approach). This skill produces a risk-shaped prep brief: named risks + smallest useful test set + named techniques + specialty fits if relevant. ## Checklist Track these as an ordered work list (use the host's task primitive if available, otherwise a numbered inline tracker) and complete in order: 1. Read the user's intent and target paths. 2. Call `sumo_qa_load_standards(classification=...)` and `sumo_qa_load_rules(classification=...)` using the classification th