tdd-workflow

Enforces test-first development workflows with minimum 80% coverage across unit, integration, e2e suites.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/Manvendra08/TradingBot --skill tdd-workflow-manvendra08
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Manvendra08/TradingBot/tree/main/_agent/skills/tdd-workflow
Command: npx skills add https://github.com/Manvendra08/TradingBot --skill tdd-workflow-manvendra08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common problem of inconsistent testing practices, insufficient test coverage, and avoidable production bugs that occur when developers skip writing tests before implementing code changes.

Core Features & Use Cases

  • Test-First Enforcement: Mandates writing tests before implementing code for all development tasks including new features, bug fixes, and refactoring.
  • Comprehensive Coverage Requirements: Sets a minimum 80% test coverage threshold across unit, integration, and end-to-end test suites, with guidance for testing edge cases, error paths, and boundary conditions.
  • Ready-to-Use Test Patterns: Includes pre-built templates and examples for common testing scenarios like API endpoint testing, UI component testing, and external service mocking.
  • Use Case: For example, when building a new user authentication endpoint, this Skill ensures you write passing integration tests for valid requests, invalid token handling, and database errors first, then implement the endpoint logic to meet those test requirements, catching critical edge cases before deployment.

Quick Start

Use the tdd-workflow skill to write comprehensive tests for your new user profile update feature before implementing the feature logic.

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?

Enforce test-driven development by mandating tests before implementing code changes for new features, bug fixes, and refactoring. This workflow eliminates inconsistent testing practices, reduces production bugs, and ensures solid code.

What is the minimum test coverage required for unit and integration testing?

The minimum required test coverage is 80% across unit, integration, and end-to-end test suites. This threshold ensures comprehensive edge case, error path, and boundary condition testing to reduce avoidable production bugs.

How do I write tests for API endpoints and UI components before implementation?

Write tests for API endpoints and UI components before implementation using ready-to-use test patterns. These templates cover common scenarios like valid requests, invalid token handling, database errors, and external service mocking.

Does test-first development work for refactoring existing web applications?

Test-first development works for refactoring existing web applications. It applies to all code modification tasks, ensuring standardized test patterns for unit, integration, and end-to-end suites are met before logic changes are deployed.

Why should I write end-to-end tests before implementing code logic?

Write end-to-end tests before implementing code logic to catch critical edge cases before deployment. This test-first approach satisfies comprehensive coverage requirements and validates error paths, preventing avoidable production bugs.

Can I use standardized test patterns for external service mocking and error paths?

You can use standardized test patterns for external service mocking and error paths. The workflow includes pre-built templates and examples for common scenarios, ensuring comprehensive edge case and boundary condition coverage.