skills.rest
Jamkris
JamkrisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd-workflow

Guide test-first development with 80%+ coverage across unit, integration, and end-to-end tests.

86|21|Updated Feb 9, 2026
Search Tags:#workflow#testing#tdd#e2e#unit-tests#integration-tests
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill tdd-workflow-jamkris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill tdd-workflow-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow guides teams to adopt test-driven development, ensuring that tests are written before implementation and that codebases maintain high reliability through comprehensive test coverage.

Core Features & Use Cases

  • Test-First Development: Dictates writing unit, integration, and end-to-end tests before coding.
  • Coverage Targets: Aims for 80%+ overall test coverage across multiple test types.
  • Structured Workflow: Provides step-by-step guidance from user journeys to test execution and refactoring.

Quick Start

Begin your feature work by writing unit tests first, then implement code to satisfy them and achieve 80%+ 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 and maintain high test coverage?▼

Test-driven development dictates writing unit, integration, and end-to-end tests before coding. This workflow provides step-by-step guidance from user journeys to test execution, ensuring 80%+ overall test coverage before implementation begins.

What is the structured workflow for writing tests before implementation?▼

The structured workflow involves writing user journeys, generating test cases, running tests to fail, implementing code, and re-running tests to verify coverage. It provides clear guidance on testing patterns and validation for new features, bug fixes, and refactoring.

Can I use this TDD workflow for fixing bugs and refactoring existing code?▼

Yes, you can apply this test-first workflow when building new features, fixing bugs, or refactoring. It ensures you create appropriate unit, integration, and end-to-end test scenarios before making code changes to maintain reliability.

What types of tests are required to achieve the 80% test coverage target?▼

Achieving the 80%+ overall test coverage target requires writing unit tests, integration tests, and end-to-end tests. The workflow guides the creation of these multiple test types alongside test-first development practices.

Are there any dependencies or specific testing frameworks required for this TDD process?▼

No specific dependencies or testing frameworks are required for this TDD process. The workflow provides clear guidance on testing patterns and validation that can be applied across your existing software engineering stack.

Related Skills

Explore More Software Engineering Skills→
Ying-Kai-LiaoYing-Kai-Liao
1

tdd-workflow

Enforce test-driven development workflows with 80%+ coverage across unit, integration, and end-to-end tests.

Community
Advanced
steven715steven715
2

tdd-workflow

Enforce test-driven development in C++ projects using Google Test and CMake/CTest.

Community
Intermediate
lastcowlastcow

innozverse-testing-quality

Enforce linting, type checking, formatting, and build checks for the innozverse project.

Community
Intermediate
pedropaulovcpedropaulovc
3

test-driven-development

Enforce a failing test-first workflow for each feature or bugfix.

Community
Intermediate