deep-research

Conducts pre-build product discovery across local projects, competitors, ecosystems, and platform capabilities.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill deep-research-scsm-unrestrict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-research
Source: https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent/tree/main/frontend-engineer/skills/deep-research
Command: npx skills add https://github.com/scsm-unrestrict/dsh-frontend-engineer-agent --skill deep-research-scsm-unrestrict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into code from training data leads to missed reusable work, outdated platform assumptions, and uninformed architecture decisions. This Skill performs structured research and discovery before building something new, producing a research brief that makes the actual build far more productive. ## Core Features & Use Cases - Three Depth Levels: Choose focused (one decision, ~30 min), wide (landscape understanding, 1-2 hours), or deep (exhaustive, 3-6 hours) research scopes. - Multi-Source Discovery: Scans local projects for reusable code, analyzes competitors, mines GitHub issues and forum sentiment, evaluates libraries, and audits platform capabilities (e.g., Cloudflare Workers, D1, Vectorize) against current docs rather than stale training data. - Structured Research Brief: Synthesizes findings into a markdown brief saved to .jez/artifacts/ covering competitive landscape, user needs, technical decisions, reusable assets, risks, and suggested build phases. - Use Case: Before building a markdown note app on Cloudflare, run deep research to discover that Workers AI toMarkdown, D1 FTS5, and Vectorize enable document import, full-text search, and semantic search — capabilities you would have missed from training data alone. ## Quick Start Ask the agent to do deep research on the product or feature you want to build, specifying a depth level such as focused, wide, or deep.

Frequently Asked Questions about deep-research

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

FAQPage Schema
How do I research competitors before building a new product?

Use the wide or deep research depth to analyze 3-10 competitors across features, pricing, user complaints, tech stack, and documentation quality. Findings come from landing pages, Reddit, Hacker News, app store reviews, and GitHub issues, then feed into a structured research brief.

What is the difference between focused, wide, and deep research?

Focused answers one specific decision in about 30 minutes with a 1-page recommendation. Wide maps the landscape for a new product in 1-2 hours, enough to write a spec. Deep takes 3-6 hours and adds library research, plugin ecosystems, GitHub issue mining, and future-casting to drive weeks of coding.

How do I find reusable code in my existing projects before starting a new build?

The local exploration step scans your machine for related projects by keyword, reads their CLAUDE.md files for architecture context, and identifies reusable schemas, components, utilities, and configs. Results are captured in the brief's Reusable From Existing Projects section.

Why research platform capabilities instead of relying on training data?

Training data lags behind platforms like Cloudflare, Vercel, and Supabase that ship features constantly. The skill reads current changelogs, blogs, and full product catalogues to find recently launched capabilities, such as Workers AI toMarkdown or D1 FTS5, that change what is feasible to build.

Where is the research brief saved and what does it contain?

The brief is saved as a markdown file to .jez/artifacts/research-brief-{topic}.md. It contains an executive summary, competitive landscape, ecosystem signals, user needs, technical recommendations, library evaluations, platform capabilities, proposed architecture, risks, suggested phases, and sources.

When should I not use this research skill?

Do not use it for cited fact-checking research reports, which are handled by a separate harness. This skill is specifically for pre-build product discovery: deciding what to build, what to reuse, and which technical approach to take.