tdd-workflow

Enforces test-driven development with unit, integration, and E2E coverage ≥80%.

3|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/jenningsloy318/claude-skill-artifacts --skill tdd-workflow-jenningsloy318
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/jenningsloy318/claude-skill-artifacts/tree/main/super-dev-plugin/skills/tdd-workflow
Command: npx skills add https://github.com/jenningsloy318/claude-skill-artifacts --skill tdd-workflow-jenningsloy318

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces a disciplined test-driven development workflow for code projects, ensuring that tests drive implementation and solid coverage.

Core Features & Use Cases

  • Middleware for development: Enforces writing tests before coding across features, fixes, and refactors.
  • Comprehensive test coverage: Guides unit, integration, and end-to-end tests to reach and maintain 80%+ coverage.
  • Practical workflow guidance: Provides step-by-step guidance from defining user journeys to generating tests and validating outcomes in real-world projects.

Quick Start

Activate this skill when starting a new feature or debugging; then define user journeys, generate tests, implement code, and run the full test suite to ensure green results.

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a test-driven development workflow for new features?▼

To enforce test-driven development, require tests to drive implementation by defining user journeys, generating tests first, implementing code, and running the full test suite to ensure green results.

How do I achieve 80% code coverage with unit, integration, and e2e tests?▼

Achieve 80% code coverage by applying a stepwise workflow from user journeys to test generation, guiding unit, integration, and end-to-end test execution across features, bug fixes, and refactoring.

When should I use e2e tests with playwright during refactoring?▼

Use e2e tests with playwright during refactoring to validate user journeys and ensure end-to-end test coverage maintains a minimum 80% overall code coverage before implementation changes.

Can I write tests after coding instead of driving implementation with tests?▼

Writing tests after coding bypasses the disciplined test-driven development workflow, which requires tests to drive implementation across feature work, bug fixes, and refactoring to solidify coverage.

What is the stepwise process for generating unit and integration tests?▼

The stepwise process for generating tests involves defining user journeys, generating tests to drive implementation, writing code, and executing the full test suite to validate outcomes and ensure green results.