test-roadmaplisted

# test-roadmap skill ## Purpose Synthesize. Take the three phase artifacts and produce the single document that drives execution. ## When invoked By the `/test-roadmap` command. Requires: - `docs/test-readiness/test-inventory.md` - `docs/test-readiness/test-system.md` - `docs/test-readiness/test-migration.md` ## Output structure `docs/test-readiness/test-readiness-plan.md` has six sections: ### 1. Where we are now Distilled from Phase 3: - Layer coverage map (counts: how many tests at each layer, how many ought to be there) - Local-runnable status: % of tests that run locally with no network - Canary status: size of current canary suite vs. target (from Phase 2 critical-path roster) - Speed status: current p95 per layer vs. budget - "Rebuild" debt: count by layer and effort - "Delete (redundant)" count and what it implies about false-confidence coverage ### 2. Where we want to be Distilled from Phase 2: - Framework matrix per layer - Local-substitute map - Coverage targets per tier - Canary suite definition (critical-path roster) - Speed budgets per layer ### 3. The gap The concrete diff between sections 1 and 2: - Missing layers (e.g., "no integration tests at all") - Wrong-layer tests (count and severity) - External-only deps with no local substitute (blockers) - Canary suite size vs. target - **Speed delta** — current per-layer p95 vs. target, expressed as ratio or time-to-close ### 4. Roadmap — five milestones Always five, in this order. Each milestone has a