skills.rest
CDO-07-New
CDO-07-NewOFFICIAL
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-first development with 80 percent coverage before refactoring.

2|Updated Jul 1, 2026
Search Tags:#unit tests#testing#tdd#refactoring#integration tests#e2e tests#coverage
One-click install
npx skills add https://github.com/CDO-07-New/TF4-AIO-03-foresight-lens-final --skill tdd-workflow-cdo-07-new
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/CDO-07-New/TF4-AIO-03-foresight-lens-final/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/CDO-07-New/TF4-AIO-03-foresight-lens-final --skill tdd-workflow-cdo-07-new

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents rushed code changes by enforcing a test-first workflow before implementation, making feature delivery, bug fixes, and refactors safer and more predictable.

Core Features & Use Cases

  • Test Planning: Break user goals into clear unit, integration, and end-to-end test cases.
  • Coverage Discipline: Keep behavior covered with an 80%+ threshold and explicit edge-case checks.
  • Workflow Guidance: Support common engineering work such as API endpoints, component updates, and refactoring.
  • Example Use Case: A developer can use this Skill to add a new endpoint by writing failing tests first, implementing the smallest fix, and confirming the full suite remains green.

Quick Start

Use the tdd-workflow skill to turn your feature request into failing tests first, then implement the smallest code change that makes them pass and verify coverage before refactoring.

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-first development for new API endpoints and component updates?▼

Test-first development for new API endpoints and components requires writing failing tests before implementation. You break user goals into unit, integration, and end-to-end test cases, then implement the smallest code change to make them pass.

What is the required test coverage threshold for safe code refactoring?▼

The required test coverage threshold for safe code refactoring is 80 percent or higher. This coverage discipline ensures behavior remains protected with explicit edge-case checks and error-path testing before you refactor or release.

How do I plan unit, integration, and e2e tests for a new feature?▼

To plan unit, integration, and e2e tests for a feature, you break user goals into clear test cases. You must include isolated mocks, validate edge cases, and ensure the full test suite remains green before refactoring.

Can I use this test-first workflow for bug fixes without breaking existing behavior?▼

Yes, you can use this test-first workflow for bug fixes to prevent rushed code changes. It requires writing failing tests that replicate the bug, implementing the smallest fix, and confirming the full suite stays green before release.

What is the best way to ship code safely during software delivery?▼

The best way to ship code safely is to enforce a test-first workflow with 80 percent or higher coverage. This makes feature delivery, bug fixes, and refactors safer by requiring green test runs and edge-case validation before release.

Related Skills

Explore More Software Engineering Skills→
Dokkabei97Dokkabei97
3

tdd-workflow

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

Community
Advanced
jvegafjvegaf
17

tdd-workflow

Enforce Test-Driven Development with tests before implementation and 80% coverage.

Community
Advanced
mehdicmehdic
21

test-coverage

Generate comprehensive test coverage reports for Python, JavaScript, Go & Java projects.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

atdd-assistant

Guide Acceptance Test-Driven Development workflows for defining and validating user stories.

Community
Intermediate