tdd-plan

Generate structured Red/Green/Refactor test plans from specifications and architecture designs.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/jsalio/My-sdd-flow --skill tdd-plan-jsalio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-plan
Source: https://github.com/jsalio/My-sdd-flow/tree/main/tdd-plan
Command: npx skills add https://github.com/jsalio/My-sdd-flow --skill tdd-plan-jsalio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of structured test plans, allowing developers to start writing tests before coding, ensuring thorough test coverage with TDD (Test-Driven Development) principles.

Core Features & Use Cases

  • Generate Test Plans: Automatically create a structured Red/Green/Refactor test plan from specifications and architectural designs.
  • Define Test Cases: Organize tests by layer, type, and priority, and provide clear descriptions and expected results.
  • Incorporate Invariants: Ensure that all specifications invariants are covered by tests.
  • Use Case: Before beginning to implement a new backend feature, use the skill to create a comprehensive test plan based on the spec and arch files.

Quick Start

Generate a test plan for the 'user-registration' feature by executing /tdd-plan.

Frequently Asked Questions about tdd-plan

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

FAQPage Schema
How do I create a structured test plan for backend development using TDD?

To create a structured test plan for backend development, you need to generate test cases from specifications and architecture designs using the Red/Green/Refactor cycle. This ensures thorough test coverage before writing any code.

What is the test pyramid approach in test-driven development?

The test pyramid approach in test-driven development is a methodology that organizes tests by layer, type, and priority. It generates structured test cases from specifications to ensure comprehensive coverage and clear expected results.

Can I generate a TDD test plan for any programming language or framework?

Yes, you can generate a TDD test plan for any programming language or framework. The test planning methodology is language and framework agnostic, focusing purely on specifications, architecture designs, and test coverage.

What's the best way to ensure all specification invariants are covered by tests?

The best way to ensure specification invariants are covered by tests is to automatically organize test cases by layer and priority while generating the plan. This incorporates all architectural invariants into clear expected results.

Do I need existing specifications and architecture designs before planning tests?

Yes, you need existing specifications and architecture designs before planning tests. The test plan generation directly uses these files as input to define test cases, organize them by layer, and map expected results to invariants.

Why should I generate a test plan before implementing a new backend feature?

You should generate a test plan before implementing a new backend feature to enforce Test-Driven Development principles. This allows developers to define test cases and expected results upfront, ensuring thorough test coverage before coding begins.