tdd-plan

Name: tdd-plan
Availability: InStock
Author: curtisthe

Transform detailed designs into task-based implementation plans with assigned tests.

4|1|Updated Apr 8, 2026

Search Tags:#planning #testing #tdd #documentation #task-generation #design-to-plan

Ready to run

npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-plan-curtisthe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-plan
Source: https://github.com/CurtisThe/three-pillars-plugin/tree/main/skills/tdd-plan
Command: npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-plan-curtisthe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns a detailed design into a concrete, task-based plan that can be executed by engineers and testers. It ensures each design element is translated into actionable tasks with clear acceptance criteria.

Core Features & Use Cases

Extracts the implementation order from detailed-design.md and breaks it into discrete, testable tasks.
Generates docs/tdd-designs/<design-name>/plan.md following the standardized plan format.
Performs design-name validation and coordinates with collaboration controls before committing artifacts.

Quick Start

Run /tdd-plan <design-name> to generate a ready-to-use implementation plan for that design.

Frequently Asked Questions about tdd-plan

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

FAQPage Schema

How do I turn a detailed design into testable implementation tasks?▼

To turn a detailed design into testable implementation tasks, you generate a task-based plan that extracts the implementation order from your design document and breaks it down into discrete, actionable steps with assigned tests.

How do I generate a test-driven development plan from an existing design document?▼

You generate a test-driven development plan by processing the design document to create small, testable tasks, saving the output as a structured markdown file within a specific designs directory, and committing the artifacts via a standard workflow.

What is the best way to break down software design implementation order for testers?▼

The best way to break down software design implementation order for testers is to translate each design element into a concrete task with clear acceptance criteria, ensuring the resulting plan can be directly executed by both engineers and testers.

Do I need a specific design document format to create a task-based implementation plan?▼

Yes, you need a detailed design document that specifies the implementation order. The planning process extracts this order to create small, testable tasks and assigns corresponding tests for each step.

How does design name validation work when generating implementation plans?▼

Design name validation enforces correct naming conventions before generating the implementation plan. It coordinates with collaboration controls to respect locks and ensures artifacts are committed safely via the standard workflow.

Can I coordinate collaboration locks while committing test-driven design artifacts?▼

Yes, the planning process respects collaboration locks during artifact generation. It validates the design name, coordinates with these controls, and commits the finalized task-based plan via the standard workflow to prevent conflicts.