tdd-workflow

Automate test-driven development workflows enforcing tests-before-code with 80% coverage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures all code development follows TDD principles with comprehensive test coverage.

Core Features & Use Cases

  • Enforces tests-before-code workflow for feature development, bug fixes, and refactoring.
  • Defines a minimum of 80% test coverage across unit, integration, and E2E tests, with edge cases covered.
  • Provides structured testing patterns for Unit Tests, API Integration Tests, and E2E Playwright tests, plus example test skeletons and workflow steps.

Quick Start

Describe a user journey and write tests that drive the implementation to 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 a tests-before-code workflow for feature development and bug fixes?▼

To enforce tests-before-code, you must define a clear user journey and generate test cases before implementation. The TDD workflow drives code creation iteratively to pass these tests, ensuring green failure-free builds across feature development, bug fixes, and refactoring.

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

Achieving 80% test coverage requires automated workflows that generate unit, integration, and E2E tests with explicit edge-case handling. By iteratively executing tests against your code, you ensure comprehensive coverage and green failure-free builds across all testing layers.

How do I start test-driven development when writing tests for a new user journey?▼

To start TDD for a new user journey, describe the specific user flow and write tests that drive the implementation. You generate structured test cases first, then write code iteratively until the tests pass, achieving a green failure-free build.

Does TDD workflow require predefined user journeys before generating test cases?▼

Yes, the TDD workflow requires clearly defined user journeys before generating test cases. Defining the user journey is a mandatory prerequisite to ensure the generated unit, integration, and E2E tests accurately drive the implementation to pass.