tdd-workflow

Enforce test-driven development workflows with 80%+ coverage across feature, bug fix, and refactoring tasks.

171|10|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/fmflurry/settings-opencode --skill tdd-workflow-fmflurry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/fmflurry/settings-opencode/tree/main/skills/tdd-workflow
Command: npx skills add https://github.com/fmflurry/settings-opencode --skill tdd-workflow-fmflurry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill enforces test-driven development with 80%+ coverage, ensuring features are implemented after tests to improve reliability and maintainability.

Core Features & Use Cases

  • Enforce TDD across feature work, bug fixes, and refactors.
  • Provide guidance for creating unit, integration, and E2E tests and tracking coverage.
  • Real-world workflow examples: write user journeys, generate tests, run tests, implement code, refactor, and verify coverage.

Quick Start

Write tests first for the new feature, then implement the code to achieve 80%+ 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 workflows for feature development and refactoring?

Test-driven development workflows enforce writing tests before implementing features or refactoring code. The workflow guides you through writing user journeys, generating tests, implementing code, and refactoring to ensure reliability.

What is the best way to achieve 80% code coverage with unit and integration testing?

Achieving 80% code coverage requires running unit and integration tests after implementation. The workflow involves generating tests first, writing the code, and then verifying that appropriate test types reach the coverage threshold.

Does test-driven development apply to bug fixes and end-to-end testing?

Test-driven development applies to bug fixes and end-to-end testing. It guides creating appropriate unit, integration, and E2E tests to track coverage and verify fixes across the software creation process.

How do I write user journeys before generating tests in a TDD workflow?

Writing user journeys before generating tests defines the expected behavior upfront. The workflow then runs these tests, implements the code to pass them, and refactors while maintaining 80%+ coverage.

Can I use this TDD workflow to track quality assurance across different test types?

Yes, this TDD workflow tracks quality assurance by guiding the creation of unit, integration, and E2E tests. It verifies that features are implemented after tests to improve overall reliability and maintainability.