Menu
Cross-references multiple research documents to identify themes, gaps, conflicts, and priority rankings
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | synthesize |
| description | Cross-references multiple research documents to identify themes, gaps, conflicts, and priority rankings |
Analyze multiple research files together to identify cross-cutting themes, knowledge gaps, conflicts, and priorities.
{{RESEARCH_DIR}} — Directory containing all research markdown files.{{OUTPUT_PATH}} — File path where the synthesis report will be written.Discover and read all research files.
{{RESEARCH_DIR}} (pattern: **/*.md).Identify cross-cutting themes.
Detect knowledge gaps.
Find conflicting information.
Build a dependency graph.
Rank priorities.
critical, high, medium, or low.Write the synthesis.
Write a markdown file to {{OUTPUT_PATH}} with this structure:
# Synthesis Report
**Generated:** [ISO 8601 timestamp]
**Research files analyzed:** [count]
**Total topics covered:** [count]
## Cross-cutting Themes
[For each theme that spans multiple topics:]
### [Theme Name]
- **Appears in:** [list of topic IDs]
- **Core concept:** [1-2 sentence explanation]
- **Why it matters:** [relevance to the domain]
## Knowledge Gaps
| Topic ID | Topic Title | Gap Description | Sources Consulted | Severity |
|----------|-------------|-----------------|-------------------|----------|
| ... | ... | ... | [n], [m] from topic's research | high/med/low |
Note which source citations were checked when identifying each gap. If a gap exists because no source covered the subtopic, state "no sources found."
## Conflicting Information
### [Conflict Title]
- **Topics involved:** [topic IDs]
- **Source citations:** [cite the specific `[n]` references from each topic's research that conflict]
- **Conflict:** [description of the contradiction, referencing the cited sources]
- **Resolution:** [if known, how to reconcile; otherwise "needs investigation"]
## Topic Relationships
### Dependency Graph
[Describe the dependency ordering. Which topics are foundational? Which
build on others? Use indented lists or ASCII-style tree notation.]
### Independent Topics
[List topics that can be approached in any order without prerequisites.]
## Priority Rankings
| Priority | Topic ID | Topic Title | Rationale |
|----------|----------|-------------|-----------|
| critical | ... | ... | ... |
| high | ... | ... | ... |
| medium | ... | ... | ... |
| low | ... | ... | ... |
## Recommended Order
[Numbered list of topics in the recommended sequence, considering
dependencies and priorities.]
The SOLE WRITER to the V3.0 mem0 second brain. Invoked agentically by the executive at write moments — post-run, post-retro, post-spec-merge, manual /harvest. Decides which facts to classify into which memory type (principle/semantic/procedural/episodic/reflective), validates against the schema, and calls the deterministic plumbing in references/ via Bash. Blocks until writes are durable (poll event endpoint for SUCCEEDED). Never invoked from worker code.
Consult the V3.0 mem0 second brain agentically during executive planning, work selection, pre-spawn memory pack building, and failure diagnosis. Use this skill whenever the executive needs to remember prior runs, retros, or learned principles. Read-only — never writes. Drives the unified `mem0` CLI via Bash, orchestrating multiple iterative search queries (mem0 does not do multi-hop graph traversal natively, so iterative search IS the multi-hop).
Hook D — Failure-Diagnosis memory consultation. Runs at executive Phase 7 (after 3+ consecutive failures on a work item) BEFORE the failure-diagnosis skill itself runs. Consults the second brain for similar prior failures and successful retry strategies, then hands enriched context to the failure-diagnosis skill. Read-only. Invokes the memory-reader skill.
Hook E — Post-Retrospective Harvest. Runs after a retrospective markdown doc completes (per-run or weekly). Reads the retro fully and decides which durable lessons (reflective, semantic, procedural memories) to write to the second brain. Typically 3–8 writes per weekly retro, 0–3 per per-run retro. Invokes the memory-harvester skill for the actual writes.
Hook C — Post-Run Harvest. Runs after a worker completes (executive Phase 6 success path). Decides agentically which facts from the run to write to the second brain — typically 0–3 memory writes per run (one episodic, optionally a semantic or procedural). Invokes the memory-harvester skill to do the actual writes (with event-polling for durability).
Hook B — Pre-Spawn Memory Pack build. Runs before each worker spawn (executive Phase 4 prep). Reads the second brain for project-specific memories and produces a Memory Pack markdown block that worker-spawner injects into the worker's generated CLAUDE.md. Workers consume this as static markdown — they never call mem0 themselves. Read-only. Invokes the memory-reader skill.