tdd-workflow

Enforce test-driven development workflows from failing tests to green with coverage verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce a test-driven development discipline across software projects to ensure code correctness, maintainability, and faster iteration.

Core Features & Use Cases

  • Enforces tests-first approach across feature development, bug fixes, and refactoring.
  • Provides clear patterns and scaffolding for unit, integration, and end-to-end tests (e.g., Jest/Vitest, API tests, Playwright).
  • Guides a deterministic workflow from failing tests to green, including coverage verification and quality gates.

Quick Start

Write tests for a new feature first, then implement minimal code to pass them and verify 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 discipline across new features and refactoring?

To enforce test-driven development discipline, you write tests for new features or bug fixes first, then implement minimal code to pass them, and verify coverage. This ensures code correctness and maintainability throughout the workflow.

What's the best way to structure unit, integration, and end-to-end tests for a deterministic workflow?

The best way to structure tests for a deterministic workflow is to use clear patterns like Jest or Vititest for unit tests, API integration tests, and Playwright for E2E. This ensures a consistent progression from failing tests to green.

How do I guide a test-first workflow from failing tests to green with coverage verification?

You guide a test-first workflow by writing failing tests first, implementing minimal code to turn them green, and applying coverage verification and quality gates. This deterministic process enforces testing discipline across software projects.

Can I use Jest, Vititest, and Playwright patterns for unit, integration, and E2E testing?

Yes, you can use Jest or Vititest for unit tests, API integration tests, and Playwright for E2E tests. The workflow provides clear scaffolding and patterns to guide test creation, execution, and coverage targets across these layers.

Does test-driven development discipline apply to bug fixes and refactoring?

Yes, test-driven development discipline applies to bug fixes and refactoring. It enforces a tests-first approach across feature development, ensuring code correctness and faster iteration regardless of the task type.

Why use a test-first approach for maintaining code correctness and faster iteration?

You use a test-first approach to maintain code correctness and faster iteration because it enforces test-driven development discipline. By requiring tests before implementation, it ensures maintainability and verifies coverage targets.