skills.rest
feldboy
feldboyCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development with tests before code and 80% coverage.

Updated Jan 24, 2026
Search Tags:#workflow#testing#tdd#e2e#unit-tests#integration-tests#test-driven-development
One-click install
npx skills add https://github.com/feldboy/parlament-app --skill tdd-workflow-feldboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/feldboy/parlament-app/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/feldboy/parlament-app --skill tdd-workflow-feldboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing maintainable code quickly is hard without disciplined testing; this skill helps teams adopt test-driven development to ensure features are implemented with tests and target 80%+ coverage across unit, integration, and end-to-end tests.

Core Features & Use Cases

  • Enforces tests-before-code discipline for features, bug fixes, and refactoring.
  • Targets and validates 80%+ coverage across unit, integration, and E2E tests with edge-case coverage.
  • Provides a clear workflow for writing user journeys, generating test cases, running tests, and refactoring.

Quick Start

Start by writing tests before implementing new functionality and aim for at least 80% overall test coverage.

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 practices for new features?▼

Enforce test-driven development by writing tests before implementing functionality. This workflow ensures code is accompanied by tests, targeting 80%+ coverage across unit, integration, and E2E tests with clear guardrails for edge cases.

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

Maintain 80% test coverage during refactoring by applying a strict tests-before-code discipline. This validates edge cases and error paths, ensuring structural changes do not break existing unit, integration, or end-to-end workflows.

How does TDD workflow handle bug fixes and edge cases?▼

TDD workflow handles bug fixes by enforcing test creation before code implementation. It validates edge cases and error paths, applying guardrails to ensure fixes are accompanied by tests across unit, integration, and E2E levels.

Can I target both unit and end-to-end testing with a test-driven development approach?▼

Yes, you can target both unit and end-to-end testing. This approach applies test-driven development across unit, integration, and E2E workflows, ensuring minimum 80% overall coverage with clear guardrails for validating user journeys.

Do I need to write tests before code for all bug fixes and refactors?▼

Yes, you need to write tests before code for bug fixes and refactors. This discipline ensures all implementation is accompanied by tests, targeting 80%+ coverage and validating error paths before functional changes are merged.

Related Skills

Explore More Software Engineering Skills→
zhangzhang-111-izhangzhang-111-i
2

senior-qa

Generate Jest, React Testing Library, and Playwright tests for React/Next.js applications.

Community
Advanced
mayurpisemayurpise
39

coverage

Aggregate coverage reports across languages to identify untested code paths.

Community
Intermediate
disciplin-run-orgdisciplin-run-org

python-coder

Analyze Python code for style, structure, and error handling compliance.

Official
Intermediate
flatrickflatrick
1

tdd-workflow

Enforce Test-Driven Development with tests before code and 80% coverage.

Community
Advanced