tdd-workflow

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

1|Updated Mar 23, 2026

Search Tags:#workflow #tdd #unit-tests #integration-tests #e2e-tests #test-driven-development #software-testing

Ready to run

npx skills add https://github.com/sbalagan22/bloomr --skill tdd-workflow-sbalagan22

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/sbalagan22/bloomr/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/sbalagan22/bloomr --skill tdd-workflow-sbalagan22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures code development follows test-driven development with comprehensive test coverage.

Core Features & Use Cases

Enforces tests-before-code across unit, integration, and E2E.
Provides a repeatable workflow for writing user journeys, test cases, and implementation.
Supports step-by-step guidance from test planning to coverage verification.

Quick Start

Describe a new feature as a user journey, generate tests, implement code, and verify 80%+ coverage.

Frequently Asked Questions about tdd-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is test-driven development and how does a test-first workflow function?▼

Test-driven development (TDD) is a software testing approach where you write unit, integration, and E2E tests before implementing code. A test-first workflow functions by defining user journeys, generating test cases, writing code to pass them, and verifying 80%+ coverage.

How do I enforce test-driven development for new features and bug fixes?▼

You can enforce test-driven development by adopting a deterministic, stepwise workflow for feature development and bug fixes. This involves describing a user journey, generating tests before writing implementation code, and tracking coverage to ensure it exceeds 80%.

Can I apply unit, integration, and E2E tests during API and component refactoring?▼

Yes, you can apply unit, integration, and E2E tests during API, component, and refactoring work. A TDD workflow guides teams step-by-step from test planning to coverage verification, ensuring deterministic outcomes across all test types during structural code changes.

What's the best way to track software testing coverage across unit and integration tests?▼

The best way to track software testing coverage is through a stepwise TDD workflow that guides you from test planning to coverage verification. This ensures you consistently achieve 80%+ coverage across unit, integration, and E2E tests.

Does test-driven development require writing user journeys before generating test cases?▼

Yes, test-driven development requires writing user journeys before generating test cases. Describing a new feature as a user journey is the quick start step to producing deterministic tests, implementing the code, and verifying 80%+ coverage.