j.deep-dive

Guides multi-phase investigation workflows through brainstorming, scrutiny review, and solution assessment.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-deep-dive-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.deep-dive
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-deep-dive
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-deep-dive-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ideas and proposals often go straight from a quick brainstorm to implementation without critical review, leaving hidden risks, unchallenged assumptions, and unanswered questions that surface too late. This Skill structures deep investigation into a repeatable multi-phase workflow with saved, auditable outputs. ## Core Features & Use Cases - Three investigation modes: Explore (brainstorm only), Challenge (brainstorm plus critical scrutiny, the default), and Resolve (full pipeline with solution assessment). - Agent-orchestrated review: Summons a scrutiny-agent for structured risk and assumption analysis, and a solution-assessor for effort, risk, and viability evaluation of candidate fixes. - Persistent outputs: Saves amended brainstorm documents with a Deep Dive Synthesis section into project documentation directories, co-locating scrutiny and solution-assessment files. - Use Case: Before committing a new feature to the sprint board, run a deep dive to brainstorm the design, have the scrutiny agent flag medium and high severity risks, assess concrete solutions, then convert the refined output into Epics and Stories. ## Quick Start Ask the agent to deep dive on your feature idea and choose the challenge mode to get a brainstorm with critical scrutiny and a saved synthesis document.

Frequently Asked Questions about j.deep-dive

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

FAQPage Schema
How do I run a structured deep dive analysis on a feature idea?▼

Invoke the deep-dive workflow with your idea and select a mode: explore for brainstorm only, challenge for brainstorm plus critical scrutiny, or resolve for the full pipeline with solution assessment. The output is saved as a Markdown document in your project documentation.

What is the difference between explore, challenge, and resolve modes?▼

Explore runs information gathering and brainstorming only. Challenge adds a scrutiny-agent review that flags risks, assumptions, and open questions. Resolve additionally runs a solution assessment that evaluates candidate fixes with effort, risk, and viability ratings.

When does the deep dive escalate from scrutiny to solution assessment?▼

Escalation happens automatically when any risk is rated medium or high severity, any key question remains unanswered, or any core assumption is challenged without resolution. Resolve mode always includes the solution assessment step.

Where are deep dive results saved?▼

Outputs go to project documentation directories based on content type: plans/ for results that seed Epics or Stories, examples/ for descriptive content, and summaries/ for everything else. Scrutiny and solution-assessment files are co-located with the main document.

Why use the j-deep-dive alias instead of the plain deep-dive command?▼

The j-deep-dive directory name guarantees the workflow is reachable when another tool's built-in command shadows the bare /deep-dive name. It is a generated duplicate with identical behavior, synced from the source skill by a generator script.