dd-synthesis
Synthesize findings from multiple specialist agents into a coherent investment recommendation. Use when combining reports from 9+ specialist agents into a single decision document.
What this skill does
# Multi-Source Synthesis Methodology
As the Deal Lead, you must synthesize reports from 9 specialist agents into a coherent narrative and investment recommendation.
## Synthesis Process
### Step 1: Gather All Reports
Collect reports from shared folders:
```
/shared-out/founder-analysis/
/shared-out/market-analysis/
/shared-out/competitor-analysis/
/shared-out/tech-analysis/
/shared-out/bizmodel-analysis/
/shared-out/traction-analysis/
/shared-out/compliance-analysis/
/shared-out/captable-analysis/
/shared-out/legal-analysis/
```
### Step 2: Extract Key Findings
From each report, extract:
- Executive summary headline
- Risk score and top 3 concerns
- Top 3 positive indicators
- Any CRITICAL or HIGH severity red flags
- Unverified claims
### Step 3: Identify Patterns
Look for themes across reports:
**Corroborating Evidence**
When multiple specialists cite the same positive or negative:
- Strong team: Founder + Tech + Traction all positive
- Market concern: Market + Competitor + BizModel all flag saturation
**Contradictions**
When specialists disagree:
- Founder says $5M ARR, Traction finds $3M evidence
- Tech says "novel IP", Legal finds prior art
**Gaps**
What wasn't adequately analyzed:
- Missing international market analysis
- No direct customer interviews conducted
### Step 4: Build the Narrative
Structure your synthesis as:
1. **The Opportunity** (1 paragraph)
- What makes this company interesting
- Market timing and positioning
2. **The Team** (1 paragraph)
- Key strengths and gaps
- Track record and references
3. **The Risk Profile** (2-3 paragraphs)
- Material risks with evidence
- Mitigating factors
- Unresolved questions
4. **The Recommendation** (1 paragraph)
- Clear INVEST/PASS/NEGOTIATE stance
- Conditions or terms if applicable
## Output Documents
### 1. Investment Recommendation (JSON)
```json
{
"recommendation": {
"decision": "INVEST | NEGOTIATE | PASS",
"confidence": "HIGH | MEDIUM | LOW",
"conditions": ["condition 1", "condition 2"],
"suggested_terms": {
"valuation_range": "$X-$Y",
"check_size": "$Z",
"special_terms": ["board seat", "pro-rata rights"]
}
},
"synthesis": {
"opportunity_thesis": "Why this could be a great investment",
"primary_risks": ["risk 1", "risk 2", "risk 3"],
"mitigating_factors": ["factor 1", "factor 2"],
"open_questions": ["question 1", "question 2"]
},
"specialist_summary": {
"founder": {"score": 25, "headline": "..."},
"market": {"score": 30, "headline": "..."}
},
"overall_risk_score": 28.5
}
```
### 2. IC Briefing (Markdown)
Human-readable document for Investment Committee:
- 2-page executive summary
- Risk/reward matrix
- Comparable investments
- Recommended next steps
Save as: `/shared-out/investment-recommendation/ic_briefing.md`
## Handling Incomplete Data
If any specialist report is missing or incomplete:
1. Note the gap explicitly in your synthesis
2. Adjust confidence level downward
3. Flag as follow-up item
4. Do NOT extrapolate missing analysis
## Quality Checklist
Before finalizing your recommendation:
- [ ] All 9 specialist reports reviewed
- [ ] Risk score calculated with documented weights
- [ ] Contradictions identified and resolved
- [ ] Unverified claims flagged
- [ ] Conditions clearly stated
- [ ] Next steps defined
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.