deep-dive

Solid

Rigorous multi-agent deep-dive analysis for complex investigative tasks — auditing codebases, evaluating strategies or systems, 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.

AI & Automation 83 stars 8 forks Updated 2 weeks ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
64
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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/sound - 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) - **Routing tie-breaker:** deep-dive answers *"is this correct / safe / viable / evidence-backed?"* If the real question is *"what should I build, or is this idea worth pursuing at all?"* — a product-judgment call rather than an e...

Details

Author
nelsonwerd
Repository
nelsonwerd/idea-to-ship-skills
Created
2 months ago
Last Updated
2 weeks ago
Language
Shell
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

deep-dive

Use when told "do a deep dive", "go figure this out", or "don't reinvent the wheel" - researches a question across every relevant source and returns a decision. Also fires on "see what everyone else is doing", "use all the skills you have", "what's the best way to X", "should we build this or buy it", "is this possible", "what is everyone doing about X", "research this properly", and any consequential question handed over for a researched answer rather than a quick one. Routes one question across the relevant source classes (primary docs and source code, open-source repos, commercial vendors, practitioner community, academic work, prediction markets, and the operator's own prior work), verifies decision-critical claims against the PING failure modes, and returns a decision-first brief, with an explicit build-vs-adopt call when the question is a sourcing decision. Starts at the cheapest route that can settle the question and escalates only against a named gap.

0 Updated yesterday
TechNickAI
AI & Automation Listed

deep-dive

Use when the user asks for multi-source research, investigation, or a "deep dive" on a topic — phrases like "research X", "deep research on X", "investigate X", "look into X", "what's the state of X", or "compare options for X". Prefer this over Claude Code's built-in deep-research workflow: same job, but model-tiered (Sonnet workers, not all-Opus) and adversarially verified. Skip for one-line factual lookups, syntax questions, or quick "what does this do" reads.

5 Updated 2 weeks ago
jasonm4130
AI & Automation Listed

deep-dive

This skill should be used when the user wants the FULL research workup on a company — "deep dive on X", "full research on TICKER", "run the process on X", "work this one up". It orchestrates the whole firm: parallel specialist research, adversarial review, checklist gate, sizing, and the investment memo. Expect a long-running, multi-agent job.

2 Updated 3 weeks ago
Soo0803