test-strategy-plannerlisted

# Test Strategy Planner ## Phase Contract This skill runs in **PLANNING** only. Before any other step, read `vibeflow.config.json`'s `currentPhase`. If it is not PLANNING, emit: > test-strategy-planner is for PLANNING phase; current is `<phase>`. In > REQUIREMENTS, run `/vibeflow:prd-quality-analyzer` first; advance > through DESIGN and ARCHITECTURE with `/vibeflow:advance`; only then > plan the test strategy. …and stop. The scenario-set.md this skill produces feeds every downstream test-writer — generating it with a stale or un-approved PRD poisons the rest of the pipeline. This is the KEYSTONE skill in the VibeFlow testing pipeline. scenario-set.md produced here is required by 80% of downstream test skills. ## Input - PRD content (required): The product requirements document - Platform (required via $ARGUMENTS): web, ios, android, or all - prd-quality-report.md (optional): Output from prd-quality-analyzer ## Algorithm ### Step 1: Document Analysis Extract from the PRD: - Functional requirements (FR-XXX) - Non-functional requirements (NFR-XXX) - User roles and permissions - Critical business flows - Integration points - Ambiguities flagged by prd-quality-analyzer (if available) ### Step 2: Scenario Set Creation For EACH requirement, generate minimum 3 scenarios: | Scenario Type | Naming Convention | Purpose | |--------------|-------------------|---------| | Happy Path | SCN-X-XXX-H-01 | Normal successful flow | | Edge Case | SCN-X-XXX-E-01 | Boundary values, limits