Menú
Debug complex issues using competing hypothesis investigation with 3 parallel agents
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Complete guide to integrating official fillable PDF forms (especially GTA forms) into web applications. Covers AcroForm field mapping, pdf-lib usage, field inspection, and hybrid browser-native editing workflow.
Creates Excalidraw diagrams programmatically. Use when the user wants flowcharts, architecture diagrams, system designs, or any visual diagram instead of ASCII art. Outputs .excalidraw files that can be opened directly in Excalidraw or VS Code with the Excalidraw extension.
Hardware specs, system recovery history, and environment details for the current system
Complete reference of available tools, plugins, marketplaces, and workflow commands
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
Basado en la clasificación ocupacional SOC
| name | parallel-debug |
| description | Debug complex issues using competing hypothesis investigation with 3 parallel agents |
| user-invocable | true |
| disable-model-invocation | true |
Validated by Anthropic's official Agent Teams docs as the "Competing Hypotheses" pattern.
Launch all 3 in a SINGLE message (parallel execution):
// Agent 1: Where symptoms appear (child component / output layer)
Task({ subagent_type: "fire-debugger", prompt: "Investigate [symptom location]..." });
// Agent 2: What triggers it (parent/caller / data layer)
Task({ subagent_type: "fire-debugger", prompt: "Investigate [trigger source]..." });
// Agent 3: Working reference (proven patterns in codebase)
Task({ subagent_type: "Explore", prompt: "Find working examples of [similar pattern]..." });
.planning/research//warrior-add-newskill)Solved in ~1 hour vs 3+ hours sequential debugging.
YouTube/Vimeo videos stopping after 2-3 seconds in MERN LMS:
Skills Library Reference:
~/.claude/plugins/warrior-workflow/skills-library/video-media/REACT_VIDEO_PLAYER_REINITIALIZATION_FIX.md
"When the root cause is unclear, a single agent tends to find one plausible explanation and stop looking. The debate structure fights anchoring bias. The theory that survives is much more likely to be the actual root cause."