dotagents

Deep Research Foundations

Use this skill when a repo needs a durable foundations/<topic>/ packet rather than a one-off research summary.

The skill preserves the useful deep-research orchestration pattern:

It removes person-specific residue and treats foundations work as a canonical Miadi / Mighty Eagle stewardship contract.

Stewardship Contract

Purpose

Create academically grounded, repo-local foundation packets that help a branch, skill, runtime, issue, or artifact stand on recognized fields, explicit provenance, and readable intent.

Stewardship Responsibilities

Default Placement

Every repo owns its own local packet root:

foundations/<topic>/

Default rule:

Packet Shape

Recommended minimum structure:

foundations/<topic>/
  README.md
  source-ledger.yaml
  context-layer.md
  intent-understanding.md
  synthesis.md

For fielded packets, add one file or folder per field:

foundations/<topic>/
  README.md
  source-ledger.yaml
  context-layer.md
  intent-understanding.md
  synthesis.md
  <field-slug>.md

Explicit Layer Separation

1) Context-Layer

The context-layer captures the shared framing and durable metadata around the packet.

Include:

Questions this layer answers:

2) Intent-Understanding

The intent-understanding layer captures why the packet exists and what structural tension it resolves.

Include:

Questions this layer answers:

Research Diamond

         [Broad: decompose question]
              /        \
    [Narrow: 3-6 parallel field agents]    ← Wave 1
              \        /
         [Evaluate: gaps, cautions]
              /        \
    [Deep: 1-2 targeted agents]            ← Wave 2 if needed
              \        /
         [Synthesize: foundations packet]

Start broad, go narrow in parallel, identify gaps, go deep on gaps, synthesize.

Workflow

Phase 0 — Establish Date Context

Record today’s date and include it in prompts, packet metadata, and the source ledger.

Phase 1 — Gather Local Context

Before external research:

Phase 2 — MECE Field Decomposition

Break the topic into mutually exclusive, collectively exhaustive fields.

Common field families:

Scale effort to complexity:

Phase 3 — Parallel Research

Each research lane should include:

  1. Date context
  2. Why the packet matters
  3. Specific field angle and boundaries
  4. Source strategy
  5. Source quality bar
  6. Expected output shape

Prompt skeleton:

You are researching [FIELD / ANGLE] for a repository-local foundations packet.
TODAY'S DATE: [date]
PURPOSE: [why this packet matters]
AUDIENCE: [who will use it]
ANGLE: [field scope]
BOUNDARIES: [what this lane does not cover]
SOURCE QUALITY: Prefer academic papers, standards, official docs, primary sources, and strong practitioner engineering writing.
OUTPUT: canonical concepts, key findings, cautions, engineering implications, provenance notes, and sources with URLs/DOIs.

Phase 4 — Gap Analysis

After all lanes return:

Phase 5 — Synthesis

The final packet should synthesize, not concatenate.

Recommended outputs:

source-ledger.yaml should include at minimum:

meta:
  packet: <topic-slug>
  generated: <date>
  method: deep-research-foundations
  verification_status: live-web-verified | training-knowledge-only | mixed
sources:
  - id: <short-id>
    field: <field>
    title: <title>
    url: <url>
    doi: <doi-if-any>
    supports: <claim-or-decision>
    verified: true|false

Phase 6 — Placement, Crosswalk, and Verification

Before calling the packet done:

Quality Gate

Do not call the packet complete unless:

Common Pitfalls