skills.rest
DrinkBoooz
DrinkBooozCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development with failing tests before code implementation.

Updated Apr 12, 2026
Search Tags:#workflow#testing#tdd#unit-testing#integration-testing#e2e-testing#test-driven-development
One-click install
npx skills add https://github.com/DrinkBoooz/PyTrade --skill tdd-workflow-drinkboooz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/DrinkBoooz/PyTrade/tree/main/.opencode/skills/trading-creation-tool/ecc/skills/tdd-workflow
Command: npx skills add https://github.com/DrinkBoooz/PyTrade --skill tdd-workflow-drinkboooz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures teams adopt test-driven development, driving code changes through tests and safeguarding refactors with robust test suites.

Core Features & Use Cases

  • Enforces 80%+ test coverage across unit, integration, and end-to-end tests.
  • Provides a clear, step-by-step workflow for writing tests before implementation and for incremental delivery.
  • Supports guided refactoring with test-driven guardrails to prevent regressions.

Quick Start

Outline a feature's user journey, write failing tests first, implement code to pass them, and iterate until all tests pass and coverage goals are met.

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 unit, integration, and E2E tests?▼

You can enforce test-driven development by writing failing tests before implementation and iterating code until all unit, integration, and E2E tests pass. This ensures changes are driven by tests and guided by clear scaffolds.

What is the best way to maintain 80% test coverage during refactoring?▼

Maintaining 80% test coverage during refactoring requires test-driven guardrails using existing unit, integration, and E2E tests. This prevents regressions by ensuring incremental implementation passes tests before integration.

How do I start writing tests before coding for a new feature?▼

Start writing tests before coding by outlining the feature's user journey, creating clear failing test scaffolds, implementing code to pass them, and iterating until tests pass and coverage goals are met.

Does test-driven development work for bug fixes and refactoring?▼

Test-driven development works for bug fixes and refactoring by requiring tests before coding. It applies incremental implementation across unit, integration, and E2E tests to achieve 80%+ coverage and prevent regressions.

Why should I write failing tests before implementing code?▼

Writing failing tests before implementing code ensures changes are driven by test requirements. This safeguards refactors with robust test suites and maintains 80%+ coverage thresholds until all tests pass.

Related Skills

Explore More Software Engineering Skills→
caobingshengcaobingsheng
1

tdd-workflows-tdd-red

Generate failing tests to define expected behavior in the TDD red phase.

Community
Advanced
hbvg234hbvg234
1

tdd-workflow

Enforce test-driven development with unit, integration, and E2E tests at 80%+ coverage.

Community
Advanced
abhishekdutta18abhishekdutta18

plankton-code-quality

Run formatters and linters to enforce code quality during file edits.

Community
Intermediate
narumirunanarumiruna
8

test-driven-development

Enforce red/green/refactor cycles for feature development, bug fixes, and refactors.

Community
Intermediate