tdd-workflow

Enforce test-driven development and 80% coverage across TypeScript and Kotlin projects.

3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/Dokkabei97/hardened-claude-code --skill tdd-workflow-dokkabei97
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Dokkabei97/hardened-claude-code/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/Dokkabei97/hardened-claude-code --skill tdd-workflow-dokkabei97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The TDD workflow helps engineering teams enforce test-driven development and achieve high test coverage across TypeScript and Kotlin projects.

Core Features & Use Cases

  • Enforces a discipline of writing tests first for new features, bug fixes, and refactors.
  • Supports TypeScript (Jest/Vitest/Playwright) and Kotlin (Kotest/MockK/Spring Boot Test) with concrete examples and patterns.
  • Provides a repeatable workflow: capture user journeys, generate tests, run and fail, implement code, and verify coverage.

Quick Start

Describe a feature as a user journey, create failing tests, implement code to make tests pass, and verify at least 80% coverage across unit, integration, and e2e tests.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce test-driven development and achieve high test coverage in TypeScript and Kotlin projects?

Test-driven development is enforced by applying a repeatable workflow: capture user journeys, generate failing tests, implement code to pass tests, and verify at least 80% coverage across unit, integration, and e2e tests.

Can I use this TDD workflow with Playwright for end-to-end testing in TypeScript?

Yes, the TDD workflow supports TypeScript environments using Playwright for e2e testing, alongside Jest and Vitest, to validate features and verify comprehensive test coverage.

Does this testing workflow support Kotlin frameworks like Kotest and MockK?

Yes, the testing workflow supports Kotlin projects by utilizing Kotest, MockK, and Spring Boot Test to drive feature development, bug fixes, and refactoring with concrete patterns.

What is the step-by-step process to start writing tests first for new features?

To start writing tests first, describe a feature as a user journey, generate and run failing test cases, implement the code to make tests pass, and verify coverage reaches 80% or higher.

Why should I use a defined TDD workflow for refactoring instead of writing tests afterward?

A defined TDD workflow enforces writing tests first for bug fixes and refactors, ensuring a repeatable process that captures user journeys and validates 80%+ coverage before implementation.

What are the limitations of enforcing an 80% test coverage threshold across different test types?

The workflow enforces an 80% coverage threshold across unit, integration, and e2e tests, requiring you to generate and pass failing tests for all new features, bug fixes, and refactors.