test-agent-skill

Test-driven development (TDD) uses failing tests as executable specifications. This Skill generates comprehensive RED-phase test suites using Vitest, Playwright, and Testing Library that intentionally fail to prove no implementation exists yet, establishing immutable requirements across entities, use cases, services, APIs, and end-to-end flows before implementation begins.

Yes. This Skill orchestrates Vitest for unit and integration testing, Playwright for end-to-end browser testing, and Testing Library for component testing, covering all architectural layers in a unified TDD workflow with mandatory Context7 pattern consultation and strict RED-phase failure guarantees.

Organize tests by architectural tier—entities, use cases, services, APIs, and E2E flows—using template-driven test creation. This Skill enforces this layered approach with Zod schemas for validation, coverage configuration, and mock infrastructure, ensuring comprehensive specification coverage from Phase 0 research through Phase 6 handoff.

This Skill generates comprehensive test specifications from PRD-driven feature requirements, eliminating manual ambiguity. It produces template-driven test suites that fail intentionally with 'not defined' or 'not implemented' errors, serving as the definitive specification without requiring manual specification writing.

This Skill enforces strict RED-phase failure guarantees through mandatory research, template-driven test creation, and mock infrastructure setup. Tests are validated to fail with appropriate 'not defined' or 'not implemented' errors, proving the specification is defined and implementation does not yet exist.

After RED-phase test creation, implementation follows the test specifications through Phases 1–6. The immutable failing tests guide development and serve as acceptance criteria, ensuring the final implementation matches the originally defined specification exactly.