tdd-planning

Generate a TDD implementation plan from a PRD or design document.

23|2|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill tdd-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-planning
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/tdd-planning
Command: npx skills add https://github.com/kaptinlin/gozod --skill tdd-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a PRD, spec, or design document into a self-contained TDD implementation plan, detailing the interface contract, acceptance criteria, and phased guidance, without delivering implementation code.

Core Features & Use Cases

  • Defines exported signatures, data types, and error contracts to guide TDD cycles.
  • Maps a feature into phased, testable tasks suitable for iterative implementation.
  • Facilitates alignment between planning and implementation, reducing ambiguity and rework.

Quick Start

Generate a plan for the target feature from the provided PRD or design document.

Frequently Asked Questions about tdd-planning

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

FAQPage Schema
How do I turn a PRD into an actionable TDD plan?

To turn a PRD into a TDD plan, provide your spec or design document to generate a single plan file detailing interface contracts, acceptance criteria, and phased tasks for iterative implementation.

What is test-driven development planning for code design?

Test-driven development planning defines exported signatures, data types, and error constraints from a design document to guide TDD cycles, reducing ambiguity and aligning implementation with requirements.

How do I define interface contracts and acceptance criteria before coding?

Define interface contracts and acceptance criteria by transforming feature requirements into a structured document that specifies exported signatures, behaviors, and phased testable tasks.

Can I generate phased implementation tasks from a design document?

Yes, you can generate phased implementation tasks by mapping a feature design document into iterative, testable steps suitable for structured development without delivering the actual code.

Does TDD planning generate actual implementation code?

No, TDD planning does not generate implementation code; it produces a self-contained plan file with sections for Architecture, Constraints, Interface Contracts, and Phased Tasks to guide coding.

What sections should a TDD implementation plan include?

A TDD implementation plan should include sections for Constraints, Architecture, Interface Contract, Phases, Commit, Out of Scope, and References to document signatures and behaviors.