tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: danielkhigay

Enforce test-driven development with test-first coding and 80%+ coverage targets.

Updated Feb 19, 2026

Search Tags:#workflow #testing #tdd #unit-testing #integration-testing #e2e-testing #test-coverage

Ready to run

npx skills add https://github.com/danielkhigay/gaz --skill tdd-workflow-danielkhigay

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/danielkhigay/gaz/tree/main/.claude/skills/archived/tdd-workflow
Command: npx skills add https://github.com/danielkhigay/gaz --skill tdd-workflow-danielkhigay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures development follows test-driven development by enforcing test-first coding and demanding high test coverage, reducing regression risk and enabling reliable refactors.

Core Features & Use Cases

Enforce tests-before-code principle across feature work, bug fixes, and refactors.
Track and achieve 80%+ test coverage across unit, integration, and end-to-end tests.
Provide a repeatable workflow: write user journeys, generate tests, run tests, implement code, and verify coverage.

Quick Start

Begin by outlining a user journey and corresponding tests, then implement code to satisfy the tests and re-run 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 practices across feature work and refactoring?▼

Test-driven development is enforced by applying a structured workflow that mandates writing tests before implementation across features, bug fixes, and refactoring tasks. This ensures code is written with tests first and meets coverage targets, reducing regression risk.

What is the best way to achieve 80%+ test coverage across unit, integration, and end-to-end tests?▼

Achieving 80%+ test coverage requires a repeatable workflow: write user journeys, generate tests, run tests, implement code, and verify coverage across test types. This structured approach ensures coverage goals are consistently met during development.

How do I start coding with a test-first workflow for new features?▼

Begin a test-first workflow by outlining a user journey and generating corresponding tests. Then implement the code to satisfy the tests and re-run them until the 80%+ coverage goals are met across all test types.

Does test-first coding work for both bug fixes and code refactoring?▼

Yes, test-first coding applies to bug fixes and refactoring. Enforcing tests-before-code principles during these tasks reduces regression risk and enables reliable refactors by validating changes against existing and new tests.

Why do I need to write user journeys before generating tests?▼

Writing user journeys before generating tests provides a structured workflow that defines expected application behavior upfront. This ensures the generated unit, integration, and end-to-end tests accurately reflect requirements before code implementation begins.

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

A strict test-first workflow ensures high test coverage and reduces regression risk, but it may require more initial time for writing user journeys and tests. It is less suited for rapid prototyping where requirements are highly unstable and code will be discarded.