tdd-workflow

Enforce test-driven development with Vitest and pytest coverage checks.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/Konstantin212/countOnMe --skill tdd-workflow-konstantin212
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Konstantin212/countOnMe/tree/main/.cursor/skills/tdd-workflow
Command: npx skills add https://github.com/Konstantin212/countOnMe --skill tdd-workflow-konstantin212

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures development teams adopt test-driven development (TDD) by guiding them to write tests before implementing code and maintaining 80%+ test coverage across client (Vitest) and backend (pytest).

Core Features & Use Cases

  • Guided TDD Workflow: From user journeys to test case generation and iterative implementation.
  • Cross‑stack Coverage: Applies to both client and backend with Vitest and pytest.
  • Quality Assurance Practice: Enforces unit, integration, and e2e testing with defined thresholds.

Quick Start

Draft user journeys and test cases following the workflow. Run tests to observe failures. Implement minimal code to satisfy tests, then re-run to verify 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 across my development team?

To enforce test-driven development, this Skill codifies a workflow that guides teams to write tests before code and mandates 80%+ test coverage across client and backend implementations.

How does the TDD workflow handle coverage verification for both Vitest and pytest?

The TDD workflow handles cross-stack coverage verification by applying enforced 80%+ thresholds to client tests using Vitest and backend tests using pytest during feature development and refactoring.

What is the best way to start test-driven development from user journeys to test case generation?

The best way to start TDD from user journeys is to draft the journeys and test cases first, run them to observe failures, then implement minimal code to satisfy the tests and verify coverage.

Can I use this TDD workflow for unit, integration, and e2e testing patterns?

Yes, you can use this TDD workflow for unit, integration, and e2e testing patterns. It enforces quality assurance practices with defined coverage thresholds across all testing stages.

Does the TDD workflow apply to API and component creation?

Yes, the TDD workflow applies to API and component creation. It guides iterative implementation and test execution to ensure code quality during these specific development tasks.

What are the limitations of enforcing strict 80%+ test coverage during bug fixes?

A limitation of enforcing strict 80%+ test coverage during bug fixes is that developers must write tests before implementing any code fixes, which requires maintaining unit, integration, and e2e tests consistently.