tdd-workflow

Guide AI agents through PortKit's RED-GREEN-REFACTOR TDD workflow with task tracking.

6|3|Updated Jul 2, 2025
One-click install
npx skills add https://github.com/anchapin/portkit --skill tdd-workflow-anchapin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/anchapin/portkit/tree/main/.skills/tdd-workflow
Command: npx skills add https://github.com/anchapin/portkit --skill tdd-workflow-anchapin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PortKit teams struggle to implement consistent TDD workflows without explicit cycles and task tracking, leading to flaky tests and unclear progress.

Core Features & Use Cases

  • Enforces the RED-GREEN-REFACTOR cycle with explicit state and task updates
  • Provides structured templates for common TDD patterns and sample code scaffolds
  • Serves as a repeatable blueprint for integrating tests into PortKit development

Quick Start

Follow the RED-GREEN-REFACTOR lifecycle to implement a new feature's tests and code.

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 consistent TDD workflow in backend feature development?

To implement TDD consistently, apply the RED-GREEN-REFACTOR lifecycle with explicit task states, mandate a .factory/tasks.md file for tracking, and use structured templates for backend services and integration tests.

What is the RED-GREEN-REFACTOR cycle and how does it manage task tracking?

The RED-GREEN-REFACTOR cycle is a TDD process mandating explicit task state updates across phases. It manages tracking by requiring a .factory/tasks.md file to record progress throughout feature development and integration tests.

How do I structure integration tests using a TDD workflow?

Structure integration tests through the TDD workflow by following the RED-GREEN-REFACTOR lifecycle steps, utilizing provided sample code scaffolds, and recording explicit test cycle states in the .factory/tasks.md file.

Does this TDD workflow require specific task tracking files for PortKit development?

Yes, this TDD workflow mandates a .factory/tasks.md file for PortKit feature development to enforce explicit task states and track progress throughout the RED-GREEN-REFACTOR test cycles.

Why does my TDD process result in flaky tests and unclear progress?

Your TDD process results in flaky tests and unclear progress when lacking explicit cycles and task tracking. Implementing the RED-GREEN-REFACTOR lifecycle with mandatory task states resolves these inconsistencies.