skills.rest
samwelmunga
samwelmungaCOMMUNITY
Explore all skills by this author →
GitHub

deep-dive

Orchestrate a multi-phase investigation workflow to refine complex ideas into project documentation.

Updated Aug 23, 2026
Search Tags:#workflow#planning#brainstorming#investigation#analysis#scrutiny
One-click install
npx skills add https://github.com/samwelmunga/JengaAgent --skill deep-dive-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deep-dive
Source: https://github.com/samwelmunga/JengaAgent/tree/main/.agents/skills/deep-dive
Command: npx skills add https://github.com/samwelmunga/JengaAgent --skill deep-dive-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of ad-hoc, shallow planning by providing a rigorous, multi-phase framework for investigating complex ideas, ensuring that assumptions are challenged and solutions are thoroughly vetted before implementation.

Core Features & Use Cases

  • Multi-Phase Pipeline: Orchestrates information gathering, interactive brainstorming, critical scrutiny, and solution assessment.
  • Configurable Depth: Offers three modes (explore, challenge, resolve) to match the complexity of the request.
  • Auditability: Automatically generates and saves structured documentation for scrutiny and solution assessments.
  • Use Case: Use this when you have a high-level feature proposal and need to identify potential risks, edge cases, and technical requirements before committing to a development plan.

Quick Start

Invoke the deep-dive skill to perform a thorough analysis of the proposed user authentication feature.

Frequently Asked Questions about deep-dive

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

FAQPage Schema
How do I structure a multi-phase investigation workflow for complex feature planning?▼

A multi-phase investigation workflow orchestrates information gathering, interactive brainstorming, critical scrutiny, and solution assessment to refine complex ideas into actionable project documentation before committing to implementation.

What is the best way to challenge assumptions during architectural decision-making?▼

The best way to challenge assumptions during architectural decision-making is applying a critical scrutiny phase that automatically generates structured documentation to validate technical viability and identify potential risks.

Can I adjust the depth of analysis for high-stakes problem-solving scenarios?▼

Yes, you can adjust the depth of analysis for problem-solving scenarios using three configurable modes: explore, challenge, and resolve, which match the rigor applied to the complexity of your request.

How do I identify edge cases and technical requirements before starting development?▼

To identify edge cases and technical requirements before development, apply a structured investigation pipeline that evaluates high-level feature proposals through interactive brainstorming and rigorous solution assessment.

Does the deep-dive workflow require integration with scrutiny and solution-assessor agents?▼

Yes, the deep-dive workflow requires integration with scrutiny and solution-assessor agents to automatically generate audit documentation, validate assumptions, and assess technical viability throughout the investigation phases.

Related Skills

Explore More Product & Management Skills→
amdmaxamdmax
2

play-story

Fetch GitHub Projects tasks and gather requirements, context, and ADRs.

Community
Advanced
growingiogrowingio
91

brainstorming

Transform vague feature requests into detailed actionable specifications.

Official
Intermediate
alo-expalo-exp
6

product-brainstorming

Guide structured product brainstorming sessions to surface diverse ideas and assumptions.

Official
Advanced
Andreicr1Andreicr1

adversarial-document-reviewer

Challenge document premises and surface unstated assumptions and risks.

Community
Advanced