tdd-workflow

Enforce test-driven development workflows with unit, integration, and E2E tests.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/ValenBorras/upscribe --skill tdd-workflow-valenborras
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/ValenBorras/upscribe/tree/main/.github/skills/tdd-workflow
Command: npx skills add https://github.com/ValenBorras/upscribe --skill tdd-workflow-valenborras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures code is developed following test-driven development practices to achieve robust test coverage and fewer defects.

Core Features & Use Cases

  • Guidance across unit, integration, and end-to-end testing
  • Clear activation contexts for feature work, bug fixes, refactoring, API additions, and new components
  • A repeatable workflow that drives 80%+ test coverage

Quick Start

Write tests before implementing code to begin aligning development with TDD principles.

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 my codebase?

You enforce test-driven development by writing tests before code, applying a structured workflow across unit, integration, and E2E tests to drive 80%+ test coverage and reduce defects.

What is the best way to achieve 80%+ test coverage during refactoring?

The best way to achieve 80%+ test coverage during refactoring is to follow a repeatable TDD workflow that specifies test requirements before code changes, ensuring robust coverage for feature work and bug fixes.

Does test-driven development work for API additions and new components?

Yes, test-driven development works for API additions and new components by providing clear activation contexts that require tests-before-code, ensuring robust integration and end-to-end testing for new functionality.

How do I structure unit, integration, and e2e tests for feature development?

Structure unit, integration, and E2E tests for feature development by following a repeatable workflow that specifies test requirements before code implementation, ensuring comprehensive coverage and fewer defects.

When should I not use test-driven development for bug fixes?

The metadata does not specify when to avoid test-driven development for bug fixes, but it enforces a tests-before-code workflow across all contexts including bug fixes to maintain 80%+ coverage and reduce defects.