Inspect multiple bug hypotheses in parallel across code, logs, and artifacts.
npx skills add https://github.com/morodomi/tdd-skills --skill tdd-diagnose
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
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.
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.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
LucasSantana-DevGuide structured four-phase debugging with root cause analysis and hypothesis testing.
AsiaOstrichGuide teams through ATDD workflows with Given-When-Then acceptance criteria.
baasith6Launch multiple read-only subagents to explore different codebase areas in parallel.
GratefulJinx77Manage multi-agent council debates with structured workflows and session persistence.
