Tdd Init

TDD INIT Phase

Start a new TDD cycle and create a Cycle doc.

Progress Checklist

INIT Progress:
- [ ] STATUS確認 → 環境収集 → 既存cycle確認
- [ ] 実装内容確認 → リスク評価 → スコープ確認
- [ ] Cycle doc作成 → tdd-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

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

If not found, recommend tdd-onboard. Also check hooks: reference.md

Step 2: Collect Environment Info

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

Step 3: Check Existing Cycles

ls -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: Quick Questions (WARN only)

Ask 2 lightweight questions. Templates: reference.md

Step 4.7: Brainstorm & Risk Questions (BLOCK only)

Templates: reference.md. Bug keywords detected → Skill(tdd-core:tdd-diagnose).

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 & Auto-Execute Next Phase

Display INIT Complete and execute based on CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS:

Reference

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

Converted and distributed by TomeVault — claim your Tome and manage your conversions.