tdd-workflow

Enforce test-driven development by writing tests before implementation code.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/joonwon-space/kis-api-ai --skill tdd-workflow-joonwon-space
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/joonwon-space/kis-api-ai/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/joonwon-space/kis-api-ai --skill tdd-workflow-joonwon-space

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps ensure all development is driven by tests, reducing bugs and regression risk by embedding test-first thinking into every feature, bug fix, or refactor.

Core Features & Use Cases

  • Test-First Development: Write tests before implementing code to clarify requirements and prevent scope creep.
  • Coverage & Quality: Enforce minimum 80% test coverage across unit, integration, and E2E tests, including edge cases and error paths.
  • Guided Workflow: Provide structured steps for crafting user journeys, generating test cases, running tests, and refactoring with confidence.

Quick Start

To start applying this workflow, outline a user journey, generate corresponding test cases, implement minimal code to satisfy tests, and repeatedly run tests until coverage goals are met.

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 across my codebase?▼

To enforce test-driven development, write tests before implementing code for features, bug fixes, and refactoring, ensuring minimal code satisfies tests and meets 80%+ coverage. This reduces bugs and regression risk.

What is the best way to maintain 80% test coverage during refactoring?▼

Maintain 80% test coverage during refactoring by running existing unit, integration, and E2E tests repeatedly until goals are met. Refactor with confidence by ensuring user journeys and edge cases remain covered.

Can I use this test-first workflow for both bug fixes and feature development?▼

Yes, you can use this test-first workflow for both bug fixes and feature development. It clarifies requirements, prevents scope creep, and embeds test-first thinking into every code change across modern projects.

Does test automation with TDD cover edge cases and error paths?▼

Test automation with TDD covers edge cases, error paths, and performance considerations. It applies structured steps to craft user journeys, generate test cases, and satisfy the 80%+ coverage requirement.

How do I start applying a test-first workflow to generate test cases?▼

Start applying a test-first workflow by outlining a user journey, generating corresponding test cases, implementing minimal code to satisfy tests, and repeatedly running tests until coverage goals are met.