tdd-plan

Plan and implement software features with strict Red-Green-Refactor TDD steps.

2|Updated Jun 7, 2022
One-click install
npx skills add https://github.com/SebasAren/dotfiles --skill tdd-plan-sebasaren
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-plan
Source: https://github.com/SebasAren/dotfiles/tree/main/pi/.pi/agent/skills/tdd-plan
Command: npx skills add https://github.com/SebasAren/dotfiles --skill tdd-plan-sebasaren

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? This Skill removes ambiguity and manual ad-hoc development by enforcing a strict Test-Driven Development workflow so features are planned, tested, implemented, and refactored in small, verifiable steps.

## Core Features & Use Cases

  • Structured planning: Create JSON-backed TDD plans with named steps that each include RED (failing test), GREEN (minimal implementation), and REFACTOR phases.
  • Guided implementation: Drive step-by-step execution, run and validate tests, update phase progress, and require commits after each completed step.
  • Project integration: Detect test commands, explore code context before changes, set a single kickoff checkpoint, and store plans under .pi/plans for repeatable developer workflows.

Quick Start

Ask the skill to plan and implement a user login feature using strict TDD and confirm the plan to begin the first Red-Green-Refactor step.

Frequently Asked Questions about tdd-plan

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

FAQPage Schema
How do I implement a feature using strict test-driven development?

To implement a feature using strict test-driven development, you create a structured JSON plan with named steps, then execute guided Red-Green-Refactor phases that require failing tests, minimal implementation, and commits after each step.

What is the Red-Green-Refactor workflow in software development?

The Red-Green-Refactor workflow is a test-driven development process where you first write a failing test (Red), implement the minimal code to pass it (Green), and then clean up the code without changing behavior (Refactor).

How do I plan and break down a feature into small, verifiable test-first steps?

You can break down a feature into verifiable test-first steps by generating a JSON-backed TDD plan that explicitly defines RED, GREEN, and REFACTOR phases for each named step before any code is written.

Can I apply test-driven development planning across different programming languages and projects?

Yes, you can apply this test-driven development planning across different projects and languages by detecting local test commands and exploring code context dynamically to execute the lifecycle steps.

How do I integrate test-driven development with my local commit workflow and CLI?

You can integrate test-driven development with your commit workflow by using CLI lifecycle commands that update phase progress, run local test validation, and require a commit after each completed Red-Green-Refactor step.

What is the best way to track progress during a test-driven development cycle?

The best way to track progress during a test-driven development cycle is using a JSON plan file with a single kickoff checkpoint that records phase updates and validates test results as each step completes.