ai-testlisted

# Test ## Purpose TDD enforcement and testing skill. Tests are executable specifications -- they define what the system does before the system does it. Maximum confidence per minute of developer time. ## When to Use - `tdd`: driving new features test-first (RED-GREEN-REFACTOR) - `run`: writing and executing tests for existing code - `gap`: analyzing coverage gaps and missing edge cases - `plan`: designing test strategy before writing tests ## Process Step 0 (load contexts): read `.ai-engineering/manifest.yml` `providers.stacks`; load `.ai-engineering/overrides/<stack>/conventions.md` for each stack and `.ai-engineering/overrides/_shared/conventions.md`; load `.ai-engineering/team/*.md` for team conventions. ### Mode: tdd (RED-GREEN-REFACTOR) For TDD mode, follow `handlers/tdd.md` for the full RED-GREEN-REFACTOR flow. ### Mode: run 1. Detect test framework from project files 2. Follow existing conventions (directory structure, naming, fixtures) 3. Write tests using AAA pattern with descriptive names 4. Run with stack-appropriate command 5. Report results: pass/fail count, coverage delta ### Mode: gap 1. Run coverage tool with branch coverage enabled 2. Identify untested critical paths (business logic > glue code) 3. Check for missing edge cases: null, empty, boundary, error paths 4. Produce gap report with prioritized recommendations ### Mode: plan 1. Map the testing surface (modules, public APIs, critical paths) 2. Assign test categories: unit, integration, e2e