tdd-workflow

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

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/rivaldiekaptrrr/Track-app --skill tdd-workflow-rivaldiekaptrrr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/rivaldiekaptrrr/Track-app/tree/main/.agent/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/rivaldiekaptrrr/Track-app --skill tdd-workflow-rivaldiekaptrrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures developers follow a test-driven development workflow, promoting high-quality code by enforcing tests before implementation and maintaining 80%+ test coverage.

Core Features & Use Cases

  • Test-first workflow: Translate user requests into tests before coding.
  • Coverage enforcement: Automatically validate 80%+ test coverage across unit, integration, and E2E tests.
  • Guided iteration: Map from user journeys to test cases, to implementation, to refactoring with continuous validation.

Quick Start

Write tests first for a new feature, then implement the feature until all tests pass.

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 for new features and bug fixes?

To enforce test-driven development, this workflow translates user requests into tests before coding, then implements the feature until all tests pass. It guides iterations from user journeys to validated tests across unit, integration, and E2E layers.

How do I maintain 80%+ test coverage across unit, integration, and E2E tests?

Maintaining 80%+ test coverage is achieved by automatically validating thresholds across unit, integration, and E2E tests during refactoring or API endpoint addition. The workflow continuously checks coverage after mapping journeys to implementation.

What is the best way to guide a development workflow from user journeys to test cases?

The best way to guide development from user journeys to test cases is a test-first workflow that maps requests to tests before implementation. It specifies workflow steps to validate tests continuously during refactoring and feature creation.

Does this test-first workflow apply to adding API endpoints and refactoring?

Yes, this test-first workflow applies to adding API endpoints, creating features, fixing bugs, and refactoring. It maintains 80%+ coverage by specifying test types and validating implementation against the pre-written tests.

Why should I write tests before implementation when creating new software features?

Writing tests before implementation promotes high-quality code by ensuring development follows a test-driven workflow. It maps user journeys to specific test cases, validating that the implementation meets requirements before refactoring.