skills.rest
chofurenairengo
chofurenairengoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

tdd-workflow

Enforce test-driven development with prescribed tests and 80% coverage targets.

Updated Aug 27, 2026
Search Tags:#testing#tdd#quality-assurance#unit-tests#integration-tests#e2e-tests
One-click install
npx skills add https://github.com/chofurenairengo/emotion-readar --skill tdd-workflow-chofurenairengo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/chofurenairengo/emotion-readar/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/chofurenairengo/emotion-readar --skill tdd-workflow-chofurenairengo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces test-driven development by ensuring code changes are guided by tests and high coverage targets.

Core Features & Use Cases

  • Test-First Development: Write tests before implementing code to guide design and catch regressions early.
  • Coverage Enforcement: Aim for 80%+ overall test coverage across unit, integration, and end-to-end tests.
  • Structured Workflow: Follow a disciplined sequence from user journeys and test case generation to implementation and refactoring.

Quick Start

Write a failing test for the feature, implement the minimal code to pass it, then run the full test suite to verify coverage.

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 feature work and bug fixes?▼

The TDD workflow applies to feature development, bug fixes, refactoring, API endpoints, and component creation. It guides implementation by prescribing tests and coverage targets before writing the actual code.

How do I start writing tests before code for a new feature?▼

To start writing tests before code, write a failing test for the feature, implement the minimal code to pass it, then run the full test suite to verify coverage and check edge cases.

What is the minimum test coverage required for unit, integration, and E2E tests?▼

The minimum required test coverage is 80% overall, combining unit, integration, and E2E tests. This coverage enforcement ensures code changes are guided by comprehensive tests and high coverage targets.

Does the test-driven development workflow work for API endpoints and component creation?▼

Yes, the test-driven development workflow applies to API endpoints and component creation. It ties these tasks to prescribed tests and coverage targets to guide design and catch regressions during refactoring.

What's the best way to structure a TDD workflow for refactoring existing code?▼

The best way to structure a TDD workflow for refactoring is following a disciplined sequence from user journeys and test case generation to implementation, ensuring edge-case checks and 80%+ overall test coverage are maintained.

When should I not use a strict test-first development approach?▼

You should not use strict test-first development when rapid prototyping without defined user journeys, as this structured workflow requires prescribed tests, edge-case checks, and an 80%+ coverage target to guide implementation.

Related Skills

Explore More Software Engineering Skills→
wraithyywraithyy

tdd-workflow

Enforce a TDD workflow with 80% coverage across unit, integration, and E2E tests.

Community
Advanced
Varuas37Varuas37
1

spec-verify

Verify specifications against test results using the spec-test tool.

Community
Intermediate
haidonglethqbhaidonglethqb

ck:test

Automate unit, integration, e2e, and UI tests with coverage analysis.

Community
Advanced
LeandroBenjaminLLeandroBenjaminL

lend-ai-testing

Enforce mandatory pre-commit and pre-PR tests with coverage checks.

Community
Intermediate