deep-research

Generate format-controlled research reports with evidence tracking, citations, source governance, and multi-pass synthesis. This skill should be used when users request a research report, literature review, market or industry analysis, competitive landscape, policy or technical brief. Triggers: "帮我调

By daymade · 1,415 installs

npx skills add daymade/claude-code-skills --skill deep-research

Source repository · Upstream listing

Deep Research Create high fidelity research reports with strict format control, evidence mapping, source governance, and multi pass synthesis. Architecture: Lead Agent + Subagents Context discipline: Keep raw search result noise in task workspaces. Pass evidence packets to the lead agent, including locators and short source excerpts. Notes are routing aids, not authorities: the lead agent must open the original source for every load bearing claim, conflicting claim, and exact figure/date/quotation used in the report. Mode Selection Determine the research mode before starting: Dimension Options Topic Mode Enterprise Research (company/corporation) OR General Research (industry/policy/tech) Depth Mode Standard (multiple decision questions or contested evidence) OR Lightweight (one bounded question with a small evidence surface) Enterprise Research Mode : Question led company research with optional analysis frameworks selected only when they help answer the decision General Research Mode : Standard P0 P7 research pipeline with source governance Depth Selection : Choose from the number and consequence of unresolved questions, not prompt length, task count, or a target word count Source Governance (V6) Source Accessibility Classification Classify every source by accessibility: Accessibility Definition Examples Usage Rule public Available to any external researcher without authentication Public websites, news articles, WHOIS (without privacy), academic papers ✅ Always allowed semi public Requires registration or limited access LinkedIn profiles, Crunchbase basic, industry reports (free tier) ✅ Allowed with disclosure exclusive user provided User's paid subscriptions, private APIs, proprietary databases Crunchbase Pro, PitchBook, private data feeds, internal databases ✅ ALLOWED for third party research authorized first party User authorized records about the user's own organization, transactions, or work Contracts, invoices, CRM records, meeting transcripts ✅ May establish internal business facts; label provenance First party boundary: User authorized records may establish what the organization did, agreed, paid, delivered, or observed. They do not count as independent external validation of market standing, customer sentiment, regulatory compliance, or third party claims. Never relabel an internal record as an external finding. ✅ EXCLUSIVE INFORMATION ADVANTAGE : You SHOULD: Use user's Crunchbase Pro to research competitors Use user's proprietary databases for market research Use user's private APIs for investment analysis Leverage any exclusive source user provides for third party research Source Type Labels Every source MUST also be tagged with: Label Definition Examples official Primary source, official documentation Company SEC filings, government reports, official blog academic Peer reviewed research Journal articles, conference papers, dissertations secondary industry Professional analysis Industry reports, analyst coverage, trade publications journalism News reporting Reputable media outlets, investigative journalism community User generated content Forums, reviews, social media, Q&A sites other Uncategorized or mixed Aggregators, unverified sources Coverage diagnostics: Track source counts, domains, source type mix, and concentration to reveal thin coverage. Never pass or fail research from these totals alone. Gate on whether each decision question and load bearing claim has fit for purpose evidence, whether counter evidence was sought, and whether remaining unknowns are explicit. AS OF Date Policy Set AS OF date explicitly at P0. For all time sensitive claims: Include source publication date with every citation Downgrade confidence if source is older than relevant horizon Define a freshness horizon per claim class and flag material outside it; a universal age cutoff is only a diagnostic P0: Environment & Policy Setup Check capabilities before starting: Check Requirement Impact if Missing Required evidence channel available Required Narrow scope or stop with the affected questions marked unknown Original source retrieval available Required for load bearing claims Do not promote summaries/snippets to final evidence Subagent dispatch Preferred Degrade to sequential Filesystem writable Required In memory notes only Set policy variables: AS OF : Today's date (YYYY MM DD) mandatory for timed topics MODE : Standard (default) or Lightweight, justified by the question map SOURCE TYPE POLICY : Enforce official/academic/secondary/journalism/community/other labels COUNTER REVIEW PLAN : What evidence would overturn each provisional conclusion Report: [P0 complete] Subagent: {yes/no}. Mode: {standard/lightweight}. AS OF: {YYYY MM DD}. When researching a specific company, use the specialized workflow to route evidence by question. Treat the six dimensions as a coverage map, not a mandatory report outline. Enterprise Workflow Overview P1: Research Task Board Decompose the assignment into decision questions. Create tasks only where separate evidence routes or expertise make the work clearer. Each task assignment includes: Expert Role : Specialist persona (e.g., "Policy Historian", "Ecosystem Mapper") Objective : One sentence investigation goal Queries : 2 3 pre planned search queries Depth : DEEP (fetch 2 3 full articles) or SCAN (snippets sufficient) Output : Path to research notes file Parallel Group : Group A (independent) or Group B (depends on Group A) Decision Question : The exact question this task helps answer Load Bearing Claims : Provisional claims that would change the conclusion Disconfirming Evidence : What would weaken or overturn each claim Evidence Route : Which source owners or record systems can actually observe the fact Stop Rule : What counts as answered, contradicted, or still unknown Task Decomposition Rules 1. Each task covers one coherent sub topic a specialist would own 2. Group A tasks must be logically independent; source independence is assessed by underlying evidence, ownership, and incentive, not domain count 3. Max 3 tasks per parallel group (concurrency limit) 4. Every task must flag time sensitive claims, counter evidence sought, and expected citation aging risk Enterprise Research Integration When in Enterprise Research Mode, map questions to the relevant dimensions rather than creating all six tasks automatically: Task A: Company fundamentals (entity, founding, funding, ownership) Task B: Business & products (segments, products, revenue structure) Task C: Competitive position (industry rank, competitors, barriers) Task D: Financial & operations (3 year financials, efficiency metrics) Task E: Recent developments (6 month events, strategic signals) Task F: Authorized first party records (when they can answer a business fact; never counted as external corroboration) Report: [P1 complete] {N} tasks in {M} groups. Dispatching Group A. Enterprise Research Mode (Specialized Pipeline) When researching a specific company, route each decision question through the relevant enterprise dimensions. Use the dimensions to find missing evidence paths; do not run all six or add quantified frameworks by default. E1: Intake Same as P0/P1 above, plus: Confirm the exact legal entity being researched (parent vs subsidiary) Select research depth from the decision questions, evidence difficulty, and requested output; page counts are planning diagnostics only Identify any specific comparison targets (benchmark companies) P2: Dispatch + Investigate Subagents execute tasks using [references/subagent prompt.md](references/subagent prompt.md) and output evidence packets in [references/research notes format.md](references/research notes format.md). With Subagents (Claude Code / Cowork / DeerFlow) 1. Dispatch Group A tasks in parallel (max 3 concurrent) 2. Each subagent searches, fetches, and tags source types 3. Every source line includes Source Type and As Of 4. Wait for Group A completion 5. Dispatch Group B (can read Group A notes) Subagent Output Requirements Each task {id}.md must contain: Question status : answered / contradicted / unknown, with the stopping evidence Sources section : stable locators from actual retrievals with source type, accessibility, date, and source family identity Claim evidence table : claim, evidence excerpt/locator, scope, confidence, and whether the original was opened Counter evidence and unknowns : what was sought, what was found, and what remains unresolved Without Subagents (Degraded Mode) Lead agent executes tasks sequentially, acting as each specialist. Preserve raw search noise outside the final evidence packet; retain a query log when reproducibility matters. Enterprise Research: Six Dimension Collection Follow [references/enterprise research methodology.md](references/enterprise research methodology.md) for: Detailed collection workflow per dimension (query strategies, data fields, validation) Data source priority matrix (P0 P3 ranking) Claim specific corroboration and conflict handling rules Key principles : Evidence driven: every conclusion must trace to a citable source Corroboration: a second source adds weight only when it is independent of the same underlying disclosure or dataset Restrained judgment: mark speculation explicitly, avoid unsubstantiated claims Structured presentation: complex information via tables, lists, hierarchies Run L1 quality check after completing each dimension (see enterprise quality checklist.md). Status per task: [P2 task {id} complete] {N} sources, {M} findings. Status all: [P2 complete] {N} tasks done, {M} total sources. Building registry. E3: Select Analysis Frameworks Only When Useful Load [references/enterprise analysis frameworks.md](references/enterprise analysis frameworks.md) only when the user's decision benefits from a framework. Use SWOT for strategic option framing, a risk matrix for decisions with explicit probability/impact inputs, and scoring only when weights and scales are defensible. Omit the framework rather than fabricate entries or precision. Run L2 quality check after analysis is complete. E4: Quality Control Three level checks from [references/enterprise quality checklist.md](references/enterprise quality checklist.md): L1 (Data) : Source count, attribution, cross validation, timeliness L2 (Analysis) : Decision question coverage, claim support, counter evidence, and framework fitness when a framework is used L3 (Document) : Structure compliance, format consistency, readability, appendices E5: Draft Using Enterprise Template Use the 7 chapter enterprise report template from enterprise quality checklist.md only when it matches the requested decision. Otherwise adapt the structure around the question map. 1. Company Overview 2. Business & Product Structure 3. Market & Competitive Position 4. Financial & Operations Analysis 5. Risks & Concerns 6. Recent Developments 7. Comprehensive Assessment & Conclusion Plus appendices: Data Source Index, Glossary, Disclaimer. E3 E7: Enterprise Analysis, Drafting, and Review E3: Structured Analysis — Select a framework from [references/enterprise analysis frameworks.md](references/enterprise analysis frameworks.md) only when it improves the decision and its inputs are defensible; otherwise use a claim evidence table E4: Quality Control — Run L1/L2/L3 checks per [references/enterprise quality checklist.md](references/enterprise quality checklist.md) E5: Draft — Use 7 chapter enterprise template E6 E7: Multi Pass Drafting and Review — Same as P4 P7 below P3: Citation Registry + S