AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Tdd Diagnose

skill-morodomi-tdd-skills-tdd-diagnose · by morodomi

複雑なバグの並列仮説調査。Subagent/Agent Teams両モード対応。「原因調査」「investigate」「diagnose」で起動。

↗ Repository
— No reviews yet
0 installs
32 views
0.0% view→install

Install

$ agentstack add skill-morodomi-tdd-skills-tdd-diagnose

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-morodomi-tdd-skills-tdd-diagnose)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 7mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Tdd Diagnose? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

TDD Diagnose Phase

複雑なバグに対し、複数の仮説を並行調査し根本原因を特定する。

Progress Checklist

DIAGNOSE Progress:
- [ ] バグ情報収集（カテゴリ・重要度・症状）
- [ ] 仮説生成（3つ以上）
- [ ] 調査実行（モード自動選択）
- [ ] 結果統合・分岐判定
- [ ] Cycle doc更新 → tdd-plan自動実行

Workflow

Step 1: バグ情報収集

1a. AskUserQuestion で構造化入力:

  • バグカテゴリ: regression / new behavior / intermittent / performance degradation
  • 重要度: blocking development / blocking users / workaround exists

1b. 続けて自然言語で質問:

  • 「エラーメッセージやログを貼り付けてください」
  • 「関連するファイルパスがあれば教えてください」

詳細: [reference.md](reference.md#バグ情報収集)

Step 2: 仮説生成

収集した情報から原因候補を 3つ以上 リスト:

| # | 仮説 | 調査方針 | |---|------|---------| | H1 | [原因候補1] | [検証方法] | | H2 | [原因候補2] | [検証方法] | | H3 | [原因候補3] | [検証方法] |

仮説テンプレート: [reference.md](reference.md#仮説テンプレート)

Step 3: 調査実行

CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS 環境変数でモードを選択:

| 環境変数 | モード | 手順 | |----------|--------|------| | 有効 (1) | 討論型 (Agent Teams) | [steps-teams.md](steps-teams.md) | | 無効 / 未設定 | 並行型 (Subagent) | [steps-subagent.md](steps-subagent.md) |

Step 4: 調査結果統合

各仮説の検証結果を集約し、分岐判定:

根本原因が特定された場合 (Identified)

→ Cycle doc に根本原因を記録、Step 5 へ

2-3候補に絞込まれた場合 (Narrowed)

→ AskUserQuestion で候補からユーザーが選択、Step 5 へ

不明・全仮説否定の場合 (Inconclusive)
調査結果が不明確です。
1. 仮説を追加して再調査（最大2回まで）
2. 手動調査へエスカレート（現時点の発見事項を記録）

再調査2回で未解決の場合、選択肢2へ強制遷移。

Step 5: Cycle doc 更新 → tdd-plan 自動実行

調査結果を Cycle doc に記録し、Skill(tdd-core:tdd-plan) を自動実行。

Reference

  • 詳細: [reference.md](reference.md)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Communication