deep-divelisted

Rigorous multi-agent deep-dive analysis for complex investigative tasks — auditing codebases, evaluating trading strategies, validating designs, doing open-ended research. Deploys 4–6 specialist agents in parallel across distinct lanes, then synthesis, then adversarial red-team review, then optional patching — producing structured markdown research files plus a plain-English executive briefing with honest 1–10 confidence ratings. ALWAYS invoke when the user says any of "deep dive", "thorough audit", "rigorous analysis", "comprehensive review", "audit this codebase", "analyze the strategy", "evaluate this design", "review this thoroughly", or "research deep dive". Also invoke proactively for any open-ended investigative task involving a codebase, strategy, system design, or research question that warrants 30+ minutes of structured analysis — even when the user doesn't use these exact phrases.
nelsonwerd/deep-dive.skill · ★ 0 · AI & Automation · score 72

Install: claude install-skill nelsonwerd/deep-dive.skill

# Deep-Dive Multi-Agent Analysis This skill orchestrates rigorous multi-lane analysis for complex investigative tasks. It deploys specialist subagents in parallel, synthesizes their findings, runs adversarial red-team review, applies fixes, and delivers a structured evidence package plus a plain-English executive briefing. ## When to use this **Strong triggers** — invoke without asking: - "Do a deep dive on [X]" - "Thorough audit of [Y]" - "Rigorous analysis of [Z]" - "Comprehensive review" - "Audit this codebase" - "Evaluate this strategy / design" - "Research [open question] thoroughly" **Softer triggers** — invoke if the task is investigative and non-trivial: - The user describes a codebase or system and asks for "thoughts" or "objective analysis" - The user has built something and asks whether it's correct/safe/profitable - The user asks open-ended research questions that span multiple domains - The user is making a high-stakes decision and needs structured evidence **Do NOT use this for:** - Single-file code review (use direct Read + analysis) - Simple factual questions (one WebSearch is sufficient) - Tasks the user has scoped tightly (e.g., "fix this bug" — just fix it) - Tasks under ~15 minutes of investigative work (overhead exceeds benefit) When in doubt, prefer to invoke. The skill is designed to scale down gracefully (3 lanes for narrow scope, 6 for broad scope). ## The four scope variants Identify which variant fits, then read the matching reference file: