test-strategylisted

# Test Strategy Design the smallest real validation plan that answers the controller's question with credible evidence. This skill belongs to Test windows. It plans and collects evidence; it does not accept product work or dispatch follow-up implementation. ## Source Skills Used - `senior-qa`: risky user journeys, test layer choice, must-pass automated tests, focused manual checklist, and flakiness as a product bug. - `code-reviewer`: evidence should cover correctness, safety, maintainability, performance, and tests when relevant. - Industry basis: risk-based testing, test pyramid, and evidence confidence. ## Wakeflow Role Use this skill only when Test is justified by one of these: - real project/environment verification; - cold-start, dashboard, runtime, daemon, or monitoring observation; - reproduction/regression that the controller cannot safely perform alone; - cross-repository integration evidence; - release or smoke confidence. Do not use Test to rediscover defects already known to the controller or to run general QA without a boundary. ## Required Inputs - Controller test card or state-root reference. - Exact question Test must answer. - Target repository/window. - What the controller/product window already self-verified. - Success meaning. - Failure meaning. - Invalid conclusions. - Stop conditions. If those inputs are missing, stop and report missing test boundary evidence. ## Workflow 1. Restate the question. - What decision will this evidence ena