---

name: tdd-init description: Start a new TDD cycle and create a Cycle doc. Triggers on "new feature", "start TDD", "add feature".

TDD INIT Phase

Start a new TDD cycle and create a Cycle doc.

Progress Checklist

CopyINIT: STATUS check → Environment → Existing cycle → Questions → Risk assessment → Scope → Feature name → Cycle doc → Guide to PLAN

Restrictions

• No detailed implementation planning (done in PLAN)
• No test code (done in RED)
• No implementation code (done in GREEN)

Workflow

Step 1: Check Project Status

Copycat docs/STATUS.md 2>/dev/null

If not found, recommend tdd-onboard.

Step 2: Collect Environment Info

Collect language versions and key packages for Cycle doc Environment section. Details: reference.md

Step 3: Check Existing Cycles

Copyls -t docs/cycles/*.md 2>/dev/null | head -1

If an active cycle exists, recommend continuing it.

Step 4: Ask What to Implement

Ask "What feature do you want to implement?" e.g., login, CSV export.

Step 4.5: Risk Score Assessment

Calculate risk score (0-100) from user input:

Keyword scores: reference.md Record Risk: [score] ([result]) in Cycle doc.

Step 4.6: Brainstorm & Risk Questions (BLOCK only)

First, clarify the problem (Brainstorm):

• What problem are you really trying to solve?
• Have you considered alternative approaches?

Then, risk-type questions based on detected keywords:

Templates: reference.md. Record in Risk Interview section.

Step 5: Scope (Layer) Confirmation

Use AskUserQuestion to confirm scope:

Details: reference.md

Step 6: Generate Feature Name & Create Cycle Doc

Generate feature name (3-5 words) and create Cycle doc from templates/cycle.md.

Step 7: Complete & Guide to PLAN

Display INIT Complete and guide to PLAN phase.

Reference

Details: reference.md | Japanese: reference.ja.md