skills.rest
hellangleZ
hellangleZCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd-workflow

Guide Test-Driven Development with tests-first methodology and 80% code coverage.

112|9|Updated Jan 23, 2026
Search Tags:#unit tests#testing#tdd#software development#integration tests#code coverage#e2e tests
One-click install
npx skills add https://github.com/hellangleZ/burn-in-cceverywhere-ralph --skill tdd-workflow-hellanglez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/hellangleZ/burn-in-cceverywhere-ralph/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/hellangleZ/burn-in-cceverywhere-ralph --skill tdd-workflow-hellanglez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures robust software development by enforcing Test-Driven Development (TDD), guaranteeing high code coverage and reliability for new features, bug fixes, and refactoring.

Core Features & Use Cases

  • TDD Enforcement: Mandates writing tests before implementation.
  • Comprehensive Testing: Supports unit, integration, and E2E tests.
  • Coverage Guarantee: Aims for 80%+ code coverage across all test types.
  • Use Case: When developing a new API endpoint, you'll first write tests for its expected behavior, error conditions, and edge cases, then implement the API logic to satisfy those tests.

Quick Start

Use the tdd-workflow skill to guide the development of a new user authentication feature, ensuring all tests are written before the code.

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?▼

Test-driven development is enforced by mandating a strict tests-first methodology, guiding you to write expected behavior, error condition, and edge case tests before implementing feature logic or applying bug fixes.

What is the minimum code coverage required for unit, integration, and e2e tests?▼

Minimum code coverage is set at 80% across unit, integration, and e2e tests. This coverage guarantee ensures high reliability during software development, refactoring, and feature implementation.

How do I start writing tests before code for an API endpoint?▼

To start writing tests before code for an API endpoint, write tests defining expected behavior and error conditions first, then implement the API logic to satisfy those tests, ensuring comprehensive test file organization.

Does this TDD workflow support end-to-end and integration tests?▼

This TDD workflow supports comprehensive testing across unit, integration, and end-to-end tests. It provides detailed patterns for writing effective test cases to guarantee robust software development and high code coverage.

When do I need a strict tests-first methodology for software refactoring?▼

A strict tests-first methodology is needed for software refactoring to guarantee reliability and prevent regressions. It enforces writing comprehensive tests before modifying existing code, maintaining 80% code coverage.

Related Skills

Explore More Software Engineering Skills→
DocaariDocaari
1

test-writer

Generate executable tests from project specs and architecture diagrams.

Community
Advanced
rube-derube-de
10

test

Detect test frameworks, run suites with coverage, and report findings as a GitHub issue.

Community
Advanced
Yeachan-HeoYeachan-Heo
38.5k

tdd

Enforce Test-Driven Development with failing tests before production code.

Community
Basic
Z1-TestZ1-Test

gherkin-authoring

Create executable behavior specifications using Gherkin Given/When/Then syntax.

Official
Intermediate