tdd-init

Create a Cycle document and prepare the PLAN phase for a new feature.

8|2|Updated Oct 28, 2025
One-click install
npx skills add https://github.com/morodomi/tdd-skills --skill tdd-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-init
Source: https://github.com/morodomi/tdd-skills/tree/main/plugins/tdd-core/skills/tdd-init
Command: npx skills add https://github.com/morodomi/tdd-skills --skill tdd-init

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the initiation of a TDD cycle by creating a Cycle document and preparing the PLAN phase for a new feature.

Core Features & Use Cases

  • Automatic Cycle doc creation when starting a new feature.
  • Environment collection and scope confirmation to inform the PLAN phase.
  • Automatic triggering of the PLAN step when appropriate.

Quick Start

Start a new TDD cycle for a feature to create the Cycle doc and begin the PLAN workflow.

Frequently Asked Questions about tdd-init

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

FAQPage Schema
How do I start a TDD cycle and auto-create cycle documentation for a new feature?

To start a TDD cycle, this Skill automates Cycle document creation and prepares the PLAN phase for a new feature by collecting environment information and confirming scope to seed the TDD workflow.

What is the best way to document preliminary scope and risk when onboarding a new feature?

The best way to document preliminary scope and risk is to use a TDD cycle initiation workflow that automatically generates a Cycle document and records environment details to inform the PLAN phase.

Does TDD cycle initialization require manually triggering the PLAN step?

No, TDD cycle initialization does not require manually triggering the PLAN step. The workflow automatically prepares and triggers the PLAN phase once environment collection and scope confirmation are complete.

Can I use this TDD onboarding workflow across different software development projects?

Yes, you can use this TDD onboarding workflow across different software development projects. It applies to new feature onboarding by collecting environment information and confirming scope to seed the TDD workflow.

What environment information do I need to start a TDD cycle?

Starting a TDD cycle requires collecting environment information and confirming the feature scope. The workflow gathers these inputs to automatically create the Cycle document and prepare the PLAN phase.

When should I not use automated TDD cycle initiation?

You should avoid automated TDD cycle initiation when your new feature lacks defined scope or environment details, as the workflow depends on confirming scope and collecting environment information to generate the Cycle document.