tdd-workflow

To enforce test-driven development workflows, you need a structured playbook that defines test types, coverage targets, and quality gates. This skill guides the entire TDD process from writing user journeys to validating code before release.

Maintaining 80% test coverage requires defining specific quality gates for unit, integration, and E2E tests during development cycles. This skill enforces these targets by integrating coverage validation into your feature implementation and refactoring stages.

Structuring unit, integration, and end-to-end tests requires clear file organization and workflow documentation. This skill provides practical examples and best practices for defining test types and organizing tests from initial user journeys through final release validation.

Yes, a test-first approach works for both bug fixes and code refactoring by ensuring changes are validated against user journeys. This skill activates at the start of any development task to guide test generation and validate coverage before release.

Teams struggle to align on quality gates and review standards when lacking a repeatable, collaborative playbook for software delivery. This skill provides structured guidance on workflow steps, test types, and best practices to unify team standards.

The tdd-workflow skill does not list specific framework dependencies, focusing instead on the workflow logic for achieving 80%+ coverage. It provides category-level best practices applicable across unit, integration, and E2E testing environments.