What problem does it solve? Teams investing in tests for an existing product often lack a structured strategy: they either write tests ad hoc, over-invest in expensive e2e coverage, or produce a test plan that goes stale after the first sprint. This Skill writes a phased test rollout strategy grounded in real evidence (PRD, roadmap, git hot-spots, user interview) and then drives each rollout phase through the research, plan, and implement chain, resuming from the next pending phase on every run. ## Core Features & Use Cases - Stateful rollout orchestration: Re-derives progress from artifacts on disk (change folders, research.md, plan.md) and hands off to the next downstream command, so re-running always resumes where you left off. - Evidence-based risk map: Combines document discovery, a git hot-spot scan, a test-base profile, and a five-question user interview into an impact × likelihood risk map with response guidance per risk. - Growing cookbook: The generated test-plan.md starts as a strategy (§1–§5) and fills in cookbook patterns (§6) as each rollout phase ships, with a freshness ledger to prevent rot. - Use Case: A brownfield project with a PRD but no test strategy invokes the Skill; it interviews the owner, writes context/foundation/test-plan.md with 3–5 rollout phases, then queues /10x-new for the first phase and resumes automatically on later runs. ## Quick Start Run /10x-test-plan in a project that already has a PRD and roadmap to generate the phased test plan and begin the first rollout phase.
