ReddRadar
Agent skill
synthesizing-research
Consolidate multiple parallel research documents into a single unified report. Produces a self-contained document that a reader with no prior context can understand completely.
Install this agent skill to your Project
npx add-skill https://github.com/bostonaholic/rpikit/tree/main/skills/synthesizing-research
SKILL.md
Research Synthesis
Consolidate research for: $ARGUMENTS
Purpose
When research is conducted in parallel — multiple agents exploring different aspects of a problem — each produces a separate findings file. This skill combines those files into one self-contained document that a reader with no prior context can understand completely.
Process
1. Locate Research Files
Search for research files related to the topic:
Glob pattern: docs/plans/*-<topic>-*.md
Exclude: *-plan.md, *-research.md (the consolidated output)
If no files are found, ask the user to specify the file paths.
2. Read All Source Files
Read each research file completely. Note:
- Key findings from each source
- Overlapping or contradictory information
- Gaps — topics mentioned but not investigated
- Confidence levels stated by each researcher
3. Organize by Theme
Restructure findings by theme, NOT by source. Multiple researchers may have found related information — group it together rather than presenting each researcher's output sequentially.
Themes to look for:
- Architecture and design patterns
- Data flow and state management
- External dependencies and APIs
- Security and performance considerations
- Testing patterns and coverage
- Gaps and open questions
4. Write Consolidated Document
Create the synthesis at: docs/plans/YYYY-MM-DD-<topic>-research.md
(Use today's date in YYYY-MM-DD format)
# Research: <Topic> (YYYY-MM-DD)
## Problem Statement
[What is being investigated and why]
## Requirements
[Key requirements gathered from research]
## Findings
### [Theme 1]
[Findings organized by theme, not by source document]
### [Theme 2]
[Continue for each theme...]
## External Research
[Findings from web research with source citations and confidence
assessments]
## Technical Constraints
[Limitations, dependencies, and compatibility concerns]
## Open Questions
[Questions that remain unanswered across all research]
## Recommendations
[Synthesis of all findings into actionable recommendations]
## Sources
| Document | Researcher | Focus Area |
| -------- | ---------- | ---------- |
| [path] | [agent] | [scope] |
5. Validate and Present
After writing the document:
- Present a summary of key findings to the user
- Note any contradictions or gaps found during synthesis
Quality Criteria
A good synthesis document:
- Is self-contained — no prior context required to understand it
- Organizes by theme, not by source
- Resolves contradictions between sources (or flags them explicitly)
- Preserves source citations for external research
- Identifies gaps where more research may be needed
- Provides actionable recommendations
Anti-Patterns
| Do Not | Instead |
|---|---|
| Copy-paste each researcher's output sequentially | Reorganize by theme |
| Drop source citations from web research | Preserve all citations |
| Silently resolve contradictions | Flag them explicitly |
| Include raw notes or exploration logs | Distill into findings |
| Assume all findings are equally confident | Note confidence levels |
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
bostonaholic/rpikit
brainstorming
Collaborative design methodology for creative work. Use before research or planning when requirements are unclear, multiple approaches exist, or the idea needs exploration. Refines ideas through progressive questioning.
bostonaholic/rpikit
researching-codebase
Thorough codebase exploration that builds understanding through collaborative dialogue. Investigates architecture, patterns, and implementation details before planning or making changes.
bostonaholic/rpikit
test-driven-development
Rigorous TDD methodology enforcing RED-GREEN-REFACTOR discipline. Use when implementing features or fixing bugs during the implement phase. Tests must be written before production code - no exceptions.
bostonaholic/rpikit
parallel-agents
Concurrent agent dispatch for independent problems. Use when facing multiple independent tasks that can be worked on simultaneously. Reduces total time by parallelizing work that has no shared state.
bostonaholic/rpikit
implementing-plans
Disciplined plan execution with checkpoint validation, progress tracking, and verification at each step. Follows an approved plan strictly, running verification criteria before proceeding.
bostonaholic/rpikit
git-worktrees
Isolated workspace creation for parallel development work. Use when starting feature work that needs isolation from the current workspace. Creates git worktrees with proper setup and safety verification.
Didn't find tool you were looking for?