skills/deep-research/SKILL.md
Structured web research methodology for market analysis, competitor research, and technology evaluation. Ensures research uses live web data with source citations and confidence tags.
npx skillsauth add navraj007in/architecture-cowork-plugin deep-researchInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Systematic approach to web-based research for architecture and product decisions. Use this skill whenever generating market research, competitor analysis, pitch decks, cost estimates, or technology evaluations.
Cast a wide net to identify the landscape:
Competitor search: Use WebSearch for:
"{product category}" alternatives"{product category}" competitors 2025"best {product category}" software"{product category}" market leadersMarket sizing search: Use WebSearch for:
"{product category}" market size 2025"{product category}" TAM SAM"{industry}" market report"{product category}" growth rate forecastFunding/trends search: Use WebSearch for:
"{product category}" startup funding 2024 2025"{product category}" trends"{competitor name}" funding roundCollect 10-15 relevant URLs from search results for Phase 2.
Drill into specific sources to extract and verify data:
For each competitor found — Use WebFetch to:
For market size claims — Cross-reference with 2+ sources:
For funding data — Check:
For technology claims — Verify:
github.com/{repo})Organize findings into a clear, actionable document:
Confidence tagging — Mark every data point:
[Verified] — Confirmed via direct source (pricing page, press release, report)[Estimated] — Based on partial data or extrapolation[Inferred] — Based on training data, not web-verifiedSource citation — For every verified claim:
Market size: $4.2B in 2025 [Verified]
Source: Grand View Research, "Collaboration Software Market Report 2025"
URL: https://example.com/report
Data freshness — Note when data was published:
Last verified: March 2025
Source published: January 2025
Structured tables — Present competitor data as scannable tables:
| Competitor | Pricing | Funding | Key Feature | Weakness | |-----------|---------|---------|-------------|----------| | {name} | {tier} | {$Xm} | {feature} | {gap} |
Calculate quantified metrics beyond basic research:
Competitive Momentum Scoring (0-100 scale)
Feature Parity Scoring (0-100 scale)
Market Sizing with Confidence Intervals
"Note: Based on training data as of [date]. Live web search was not available. Data should be independently verified before use in investor materials."
# [Research Topic] — Deep Research Report
**Project**: [Project name from SDL]
**Researched**: [Today's date]
**Web search**: [Used / Not available]
## Executive Summary
[3-5 key findings]
## Competitor Landscape
[Table of competitors with verified data]
## Market Sizing
[TAM/SAM/SOM with sources]
## Feature Comparison Matrix
[Our product vs competitors across key dimensions]
## Opportunity Gaps
[Underserved areas competitors miss]
## Technology Landscape
[Relevant tech trends and adoption]
## Sources
[Numbered list of all URLs referenced]
This skill is automatically loaded by:
/architect:deep-research — Full standalone research report/architect:cost-estimate — For verifying current cloud/service pricingOther commands can reference this skill when they need web-verified data:
### Step N: Load Skills
Load **deep-research** skill for web research methodology
development
# Trade-Off Analysis Skill Quantifies exact trade-offs when switching between architecture options. Shows users precisely what they gain and lose when choosing Option A over Option B. ## When to Use Use this skill to help users decide between options by showing: 1. **Cost difference** — how much more/less per month? 2. **Performance difference** — how much faster/slower? 3. **Complexity difference** — how much harder to build/maintain? 4. **Scalability difference** — when does this option hit
testing
# Stage Detection Skill Detects the current project stage (concept → mvp → growth → enterprise) based on `_state.json` field presence and completeness. Used by `/architect:next-steps`, `/architect:check-state`, and roadmap commands. ## When to Use Invoke this skill when you need to determine what stage a project is at based on its state file. Stage detection drives: - Command recommendations (what to run next) - Required fields validation (what should exist at this stage) - Risk assessment (w
development
# Stack Swap Simulator Skill Estimates cost and effort to switch from one tech stack to another. Helps answer: "Can we migrate later if needed?" ## When to Use Use this skill to understand: 1. **Cost of switching stacks** — engineer weeks + downtime risk 2. **Timeline to switch** — how long is the project? 3. **Risk of switching** — what can go wrong? 4. **ROI of switching** — does it save money long-term? 5. **Backwards compatibility** — can we do a gradual migration? ## Input Provide sour
tools
# Stack Compatibility Skill Verifies that chosen technologies integrate well together. Prevents "I picked these tools and they don't work well together" regrets. ## When to Use Use this skill to verify: 1. **Chosen tools work together** — React + Node + MongoDB = good? 2. **No hidden incompatibilities** — will I hit issues in production? 3. **Team can support it** — do we have expertise for this combo? 4. **Licenses compatible** — can we use these together commercially? 5. **Performance assum