synthesize

Name: synthesize
Author: Kastalien-Research/thoughtbox

$npx mdskill add Kastalien-Research/thoughtbox/synthesize

Integrates scattered information from multiple sources into coherent understanding.

Solves the problem of scattered information needing integration.
Depends on Read, Glob, Grep, Bash, WebFetch, and WebSearch tools.
Scans at least three source types, extracts claims, patterns, conflicts, and gaps.
Delivers a synthesized summary using convergent or divergent integration strategies.

SKILL.md

.github/skills/synthesizeView on GitHub ↗

---
name: synthesize
description: Fuse insights from multiple knowledge sources (code, docs, memory, research, web) into coherent understanding. Use when you have scattered information that needs integration.
argument-hint: "[topic to synthesize]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Bash, WebFetch, WebSearch
---

Synthesize knowledge on this topic: $ARGUMENTS

## Process

### 1. Source Inventory

Identify relevant knowledge sources across these categories:

| Source Type | Where to Look |
|---|---|
| **Code** | Current codebase (Glob/Grep), implementation patterns, tests, comments |
| **Documentation** | Specs, READMEs, ADRs, API docs in the repo |
| **Memory** | `.claude/` project memory, agent memory, previous learnings |
| **External research** | WebSearch, Exa for papers, blog posts, community discussion |
| **Issue history** | selected tracker or handoff entries, closed issues, decision rationale |

Scan at least 3 source types. Don't rely on a single category.

### 2. Extract & Classify

For each source, extract:
- **Claims** — specific assertions about the topic
- **Patterns** — recurring approaches or structures
- **Conflicts** — where sources disagree
- **Gaps** — what no source addresses

### 3. Integration

Three integration strategies, used as appropriate:

**Convergent** — Multiple sources agree. High confidence. Extract the common principle.

**Divergent** — Sources disagree. Analyze *why* (different contexts? different values? different data?). Don't force resolution — document the conditions under which each view applies.

**Complementary** — Sources cover different facets. Weave into a complete picture, noting which source contributed which piece.

### 4. Output

```
## Synthesis: [Topic]

### Sources Consulted
- [Source type]: [what was found]

### Convergent Findings (high confidence)
- [Finding]: supported by [sources]

### Divergent Findings (context-dependent)
- [Claim A] (applies when [X]) vs. [Claim B] (applies when [Y])

### Gaps
- [What no source addressed]

### Integrated Understanding
[Coherent narrative combining all sources — the actual synthesis]

### Confidence Assessment
[Overall confidence and what would increase it]

### Actionable Next Steps
[What to do with this understanding]
```

More from Kastalien-Research/thoughtbox

Skill	Description
assumptions	Manage the assumption registry — track, verify, and query assumptions about external dependencies and system behavior. Prevents costly rediscovery of known failures.
capture-learning	Capture significant learnings from the current work session. Structures insights for future sessions and updates agent memory.
claude-opus-4-6-prompting	>
claude-prompt	Write or improve prompts for Claude using Anthropic's official best practices. Creates system prompts, agent prompts, tool descriptions, and MCP resource templates. Pass an existing prompt to improve it, or describe what you need to create one from scratch.
coolify-compose	Convert Docker Compose files to Coolify templates. Use when creating Coolify services, converting docker-compose.yml for Coolify deployment, working with SERVICE_URL/SERVICE_PASSWORD magic variables, or troubleshooting Coolify compose errors.
crafting-effective-readmes	Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
diagram	Generate architecture diagrams for a codebase subsystem or module. Explores source files and produces Mermaid diagrams in docs/.
diataxis	Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.
escalate	Format a structured escalation to the human decision-maker (Chief Agentic). Use when hitting an escalation threshold.
frontend-design-principles	Create polished, intentional frontend interfaces. Use this skill when building any UI — dashboards, admin panels, landing pages, marketing sites, or web applications. Routes to specialized guidance based on context.