synthesizing-research

Included with Lifetime

$97 forever

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.

General

What this skill does


# 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:

```text
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)

```markdown
# 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:

1. Present a summary of key findings to the user
2. 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 |

Files: 1

Size: 3.3 KB

Complexity: 12/100

Category: General

Source: https://github.com/bostonaholic/rpikit/tree/main/skills/synthesizing-research

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts