tdd-workflow

Coordinates teams' SELinux-driven workflows, ensuring secure file transfers and process isolation through automated policy enforcement and MCP-based management.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Test-Driven Development workflow that enforces a red-green-refactor cycle to reduce defects and increase confidence in code.

Core Features & Use Cases

  • PLAN Tests: Map features to test cases including happy paths, edge cases, and error scenarios.
  • WRITE Failing Test (Red): Write a test that initially fails to prove a missing implementation.
  • IMPLEMENT Minimum Code (Green): Implement the simplest code to satisfy the failing test.
  • REFACTOR: Refine design and improve maintainability while tests remain green.
  • VERIFY Coverage: Check and improve test coverage across the codebase.
  • Best Practices: Use deterministic gates, maintain readable tests, and guard against flaky tests.
  • Real-world Scenarios: Apply TDD to feature enhancements, bug fixes, and API changes.

Quick Start

Start by writing a failing test for the feature, then implement the minimum code to pass and iterate toward a green state.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce a test-driven development workflow for new features and bug fixes?

Enforce a test-driven development workflow by following a strict red-green-refactor cycle: plan test cases, write failing tests, implement minimum code to pass, and refactor while tests stay green. This reduces defects and increases delivery confidence.

How do I start writing tests with pytest using a red-green-refactor cycle?

Start writing tests with pytest by first mapping features to test cases including edge and error scenarios. Write a failing test to prove missing implementation, then add the simplest code to pass and iterate toward a green state.

What is the best way to plan test cases for test-driven development?

The best way to plan test cases for test-driven development is mapping features to happy paths, edge cases, and error scenarios. This structured protocol ensures tests guide design, documentation, and quality gates before implementation begins.

Does test-driven development work for refactoring existing codebases?

Test-driven development works for refactoring existing codebases by maintaining green tests while you refine design and improve maintainability. It provides deterministic quality gates that guard against flaky tests during structural improvements.

How do I verify test coverage across my codebase after implementing changes?

Verify test coverage across your codebase by checking and improving coverage metrics after implementing minimum code. The workflow ensures tests remain green during refactoring, using coverage verification as a final quality gate.

Do I need a specific test framework to apply this test-driven development cycle?

You need a test framework like pytest to apply this test-driven development cycle. The workflow requires a framework to execute tests, prove red states, validate green implementations, and verify coverage across feature enhancements and API changes.