coverage

Map all testable surfaces in the application and identify what's tested vs. what's missing. Use the Explore subagent to catalog: Routes/Pages: Components: API Endpoints: User Flows: Scan all *.spec.ts / *.spec.js files: Rank uncovered areas by business impact: For each gap, recommend: Ask user: "Generate tests for the top N gaps? [Yes/No/Pick specific]" If yes, invoke /pw:generate for each gap with the recommended template. - Scan route definitions (Next.js app/ , React Router config, Vue Router, etc.) - List all user-facing pages with their paths - Identify interactive components (forms, modals, dropdowns, tables) - Note components with complex state logic - Scan API route files or backend controllers - List all endpoints with their methods - Identify critical paths: auth, checkout, onboarding, core features - Map multi-step workflows - Extract which pages/routes are covered (by page.goto() calls) - Extract which components are tested (by locator usage) - Extract which API endpoints are mocked or hit - Count tests per area - Critical — auth, payment, core features → test first - High — user-facing CRUD, search, navigation - Medium — settings, preferences, edge cases - Low — static pages, about, terms - Number of tests needed - Which template from templates/ to use - Estimated effort (quick/medium/complex) - Coverage matrix (table format) - Coverage percentage estimate -...