tdd-diagnose

Name: tdd-diagnose
Availability: InStock
Author: morodomi

Inspect multiple bug hypotheses in parallel across code, logs, and artifacts.

8|2|Updated Oct 28, 2025

Search Tags:#subagent #diagnose #bug investigation #debug workflow #parallel hypotheses #agent teams

Ready to run

npx skills add https://github.com/morodomi/tdd-skills --skill tdd-diagnose

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-diagnose
Source: https://github.com/morodomi/tdd-skills/tree/main/plugins/tdd-core/skills/tdd-diagnose
Command: npx skills add https://github.com/morodomi/tdd-skills --skill tdd-diagnose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex bugs require evaluating multiple hypotheses in parallel to identify the root cause efficiently. This skill supports both Subagent (parallel exploration) and Agent Teams (debate-based) modes to ensure thorough coverage and faster resolution.

Core Features & Use Cases

Parallel hypothesis exploration: Runs multiple investigations simultaneously to surface root causes.
Dual operation modes: Supports Subagent mode for concurrent exploration and Agent Teams mode for structured debate and synthesis.
Workflow integration: Updates Cycle docs and triggers automatic tdd-plan execution based on findings.

Quick Start

Start a Diagnose cycle by providing the bug symptoms and requested evidence. For example, supply the bug category, severity, and relevant logs, then let the tool coordinate hypotheses and investigations, returning consolidated results.

Frequently Asked Questions about tdd-diagnose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate multiple bug hypotheses in parallel during debugging?▼

You can explore multiple bug hypotheses simultaneously using Subagent mode for concurrent code investigation or Agent Teams mode for structured debate, ensuring thorough root cause coverage across software projects.

What is the best way to diagnose complex software bugs using agent teams?▼

Agent Teams diagnose complex software bugs through structured debate and synthesis. Multiple agents evaluate conflicting hypotheses, cross-reference logs and artifacts, and consolidate findings to pinpoint the exact root cause efficiently.

How do I start a debugging workflow for analyzing code references and logs?▼

Start by providing the bug symptoms, category, severity, and relevant logs. The workflow coordinates parallel hypotheses, reads code references and artifacts via built-in explore capabilities, and returns consolidated diagnostic results.

Can I use subagents for concurrent code exploration to find root causes?▼

Yes, Subagent mode supports concurrent exploration by dispatching multiple agents to inspect different code paths and logs simultaneously. This parallel inspection accelerates root cause identification for complex software bugs.

Does parallel bug diagnosis integrate with downstream planning workflows?▼

Yes, the diagnosis workflow updates Cycle docs with consolidated findings and triggers automatic tdd-plan execution. This integration ensures that identified root causes directly feed into the subsequent planning phase.