What problem does it solve? Teams investing in tests for an existing product often lack a prioritized strategy: they either test everything uniformly or chase coverage without targeting real risks. This Skill writes a phased test rollout plan grounded in PRDs, git hot-spot churn, and a structured user interview, then drives each rollout phase through a research, plan, and implement chain. ## Core Features & Use Cases - Stateful rollout orchestration: Writes context/foundation/test-plan.md with a fixed schema, then re-derives progress on every invocation from artifacts on disk and hands off to the next downstream command. - Evidence-based risk mapping: Combines PRD lines, archived slice plans, a 30-day git hot-spot scan, and a five-question user interview into an impact-by-likelihood risk map with response guidance per risk. - Use Case: A team with a shipped product and sparse tests runs the Skill, answers five interview questions about what scares them, and receives a 3-5 phase rollout plan where each phase opens its own change folder and proceeds through research, planning, and implementation. ## Quick Start Ask the assistant to create a test plan for this project and answer the interview questions about your biggest failure concerns.
