ワンクリックでManusで任意のスキルを実行

始める

tdd-init

スター8

フォーク2

更新日2026年2月12日 23:39

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

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

morodomi

morodomi/tdd-skills

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

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

このリポジトリの他の Skills

同じリポジトリ

tdd-green

morodomi/tdd-skills

テストを通すための最小限の実装を行う。REDの次フェーズ。「実装して」「green」で起動。

2026-02-138

tdd-plan

morodomi/tdd-skills

実装計画を作成し、Test Listを定義する。INITの次フェーズ。「設計して」「計画して」で起動。

2026-02-138

tdd-onboard

morodomi/tdd-skills

既存プロジェクトにTDD環境をセットアップする。フレームワーク検出、CLAUDE.md生成、docs/STATUS.md作成を行う。「TDDセットアップ」「onboard」「プロジェクト初期化」で起動。

2026-02-128

tdd-orchestrate

morodomi/tdd-skills

TDDサイクル全体をPdMとして管理。Agent Teams有効時にtdd-initから呼ばれ、全Phaseを自律的に委譲・判断する。

2026-02-098

plan-review

morodomi/tdd-skills

PLANフェーズの設計を5観点で並行レビュー。信頼スコア80以上でBLOCK。

2026-02-098

quality-gate

morodomi/tdd-skills

コード変更を6観点で並行レビュー。信頼スコア80以上でBLOCK。tdd-reviewで自動実行。

2026-02-098

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

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