deep-research

Transform vague concepts into product specifications with a six-phase research methodology.

3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/gulati8/justice-league-factory --skill deep-research-gulati8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-research
Source: https://github.com/gulati8/justice-league-factory/tree/main/.claude/skills/deep-research
Command: npx skills add https://github.com/gulati8/justice-league-factory --skill deep-research-gulati8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Deep Research Skill provides a structured methodology to transform vague ideas into concrete, ship-ready product specifications, reducing misalignment and rework across teams.

Core Features & Use Cases

  • Phase-based approach (concept extraction, landscape survey, constraint discovery, shape definition, risk assessment, crystallization) to produce actionable outputs.
  • Outputs both a human-readable research brief and a machine-readable feature request, enabling seamless handoff to planning and implementation.
  • Used by product managers and engineers to ensure rigorous problem framing and risk-aware planning.

Quick Start

Feed in a vague concept and receive a six-phase research brief plus a machine-readable feature request.

Frequently Asked Questions about deep-research

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

FAQPage Schema
How do I transform a vague product concept into a ship-ready specification?

To transform a vague product concept into a ship-ready specification, apply a six-phase deep research methodology covering concept extraction, landscape survey, constraint discovery, shape definition, risk assessment, and output crystallization to produce structured documentation.

What is the best way to conduct risk assessment during product specification generation?

Risk assessment during product specification generation is best handled through a phased analysis approach that evaluates project constraints and shapes feature definitions, resulting in a comprehensive research brief and a machine-readable feature request.

How does a phased analysis methodology work for product documentation?

A phased analysis methodology for product documentation works by sequentially processing inputs through concept extraction, landscape survey, constraint discovery, shape definition, risk assessment, and crystallization to yield both human-readable briefs and machine-readable JSON feature requests.

Do I need any external dependencies or components to run deep research for feature requests?

No external dependencies or components are required to run deep research for feature requests. The process requires only standard documentation inputs to generate the defined research brief and feature request outputs.

Can I output a machine-readable feature request alongside a human-readable research brief?

Yes, you can output a machine-readable feature request alongside a human-readable research brief. The methodology crystallizes inputs into both formats, enabling seamless handoff from planning to implementation.

When should I use a landscape survey in product specification planning?

You should use a landscape survey in product specification planning during the early phases of research to map the existing environment and discover constraints before defining the feature shape and assessing risks.