Test Design

Test-suite design for any layer a team relies on — applied before writing the tests (author), when shaping the suite as a portfolio (strategize), or when deciding what to remove (prune). Provenance lives in skill.json; this file is runtime routing only.

Produces: an intent-specific artifact — author-design.md (a behavior, a test outline, the heuristics it satisfies, the failure modes it prevents) / strategy-doc.md (layer-by-layer investment with rationale) / prune-plan.md (deletion and quarantine candidates with reasons).

Boundaries

Do NOT use to REVIEW or triage existing tests for smells, flakiness, or false-pass (use test-audit).

Core principle