Skill

tdd-init

Start a new TDD cycle and create a Cycle doc. Triggers on "new feature", "start TDD", "add feature".

npx claudepluginhub morodomi/tdd-skills --plugin tdd-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Start a new TDD cycle and create a Cycle doc.

Supporting Assets

reference.ja.mdreference.mdtemplates/cycle.md

SKILL.md

Similar Skills

tdd-cycle

Runs full RED-GREEN-REFRACTOR TDD workflow for features from descriptions, task IDs, or specs. Confirms plan then automates failing tests (RED), minimal implementation (GREEN), and refactoring.

2 files11 tools

agent-alchemy-tdd-tools

qa-tdd-orchestrate

Orchestrates RED/GREEN/REFACTOR TDD cycles using context-isolated agents for test-first feature implementation.

7 tools

jaan-to

TDD Team

Orchestrates agentic Red-Green-Refactor TDD cycles to build features incrementally: decompose into small tasks, write failing tests, make pass, refactor. Detects project lang and test setup.

1 file

toby-essentials

Stats

Parent Repo Stars5

Parent Repo Forks0

Last CommitFeb 12, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

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:

Score	Result	Action
0-29	PASS	Show confirmation, auto-proceed
30-59	WARN	Quick questions (Step 4.6), then Step 5
60-100	BLOCK	Brainstorm & risk questions (Step 4.7)

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:

Layer	Description	Plugin
Backend	PHP/Python etc.	tdd-php, tdd-python, tdd-flask
Frontend	JavaScript/TypeScript	tdd-js, tdd-ts
Both	Full stack	Multiple plugins

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:

環境変数	実行
有効 (`1`)	`Skill(tdd-core:tdd-orchestrate)`
無効 / 未設定	`Skill(tdd-core:tdd-plan)`

Reference

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