synthesis
Synthesize all accumulated notes and drafts to generate the Discussion and Abstract sections. Sixth step of writer workflow. Requires all notes/*.md files and drafts/introduction.md, methods.md, results.md.
What this skill does
# Synthesis
Integrates all accumulated notes and prior drafts to generate the Discussion and Abstract sections, connecting findings to the broader literature.
## Prerequisites
Required files:
- `scope.md` - Research question and key findings
- `notes/papers/*.md` - Literature notes (from user-provided PDFs)
- `notes/literature-synthesis.md` - Aggregated themes and findings (key input!)
- `notes/code-analysis.md` - Methods context
- `notes/data-analysis.md` - Results context
- `drafts/introduction.md` - For narrative continuity
- `drafts/methods.md` - For methodological context
- `drafts/results.md` - Findings to discuss
## Workflow
```
[Load all notes and drafts]
│
▼
[Map findings to literature] ─── What supports/contradicts
│
▼
[Draft Discussion] ─── Interpret, compare, contextualize
│
▼
[Draft Abstract] ─── Structured summary
│
▼
[Output] ─── drafts/discussion.md, drafts/abstract.md
```
## Step 1: Load and Organize Materials
### Read Literature Synthesis (Primary Reference)
Start with `notes/literature-synthesis.md` - this document already contains:
- **Paper Citation Tracker** — Shows which papers have planned citations and which need review
- Source inventory with relationships to our work
- Key themes identified across all papers
- Findings that support our hypothesis
- Contradictory findings to address
- Methodological patterns
- Gaps our study addresses
- Citation map showing foundational papers
- Implications for Discussion section
This synthesis is the primary guide for drafting the Discussion.
### Review Paper Citation Tracker
Check the Paper Citation Tracker table to see which papers have natural fits planned. Use these as your citation guide.
**Important**: Only cite papers where they contribute meaningfully. Do not:
- Add sentences solely to include a citation
- Force parenthetical references that interrupt flow
- Stretch to make a paper seem relevant when it isn't
Papers marked "Not Applicable" in the tracker should remain uncited. A focused manuscript with relevant citations is better than a cluttered one that forces every paper.
### Read All Notes
```bash
ls notes/papers/*.md notes/*.md
```
Use individual paper notes for specific quotes and statistics.
### Mapping from Literature Synthesis
The synthesis document provides:
- Which sources support our findings
- Which sources provide contrasting results
- Which sources explain mechanisms
- Which sources address limitations
### Extract Key Results
From `drafts/results.md` and `notes/data-analysis.md`:
- Primary finding (statistic and interpretation)
- Secondary findings
- Unexpected results
- Null findings (if any)
### Review Scope
From `scope.md`:
- Research question being answered
- Hypothesis (was it supported?)
- Limitations to address
## Step 2: Map Findings to Literature
Use `notes/literature-synthesis.md` as the starting point - it already contains:
- "Findings That Support Our Hypothesis" table
- "Contradictory or Conflicting Findings" table
- "Implications for Discussion" section
Extend this mapping with our actual results from `drafts/results.md`:
| Our Finding | Supporting Literature | Contrasting Literature | Notes |
|-------------|----------------------|------------------------|-------|
| [Primary result] | [from synthesis] | [from synthesis] | [why contrast] |
| [Secondary result] | [from synthesis] | None | |
For each finding, the synthesis document identifies:
1. **Agreement**: Papers with similar findings
2. **Disagreement**: Papers with different findings (explain why)
3. **Mechanism**: Papers that explain why this occurs
4. **Clinical relevance**: Papers that contextualize importance
## Step 3: Draft Discussion
Create `drafts/discussion.md` following this structure:
### Discussion Structure (6-7 paragraphs)
```markdown
# Discussion
## Principal Findings (Paragraph 1)
[Open with main finding - interpret, don't just restate]
This study demonstrates that [interpretation of primary finding].
[Connect to research question from scope.md].
[One sentence on significance].
## Comparison with Literature (Paragraphs 2-3)
[Compare findings to existing work]
Our findings are consistent with [Author et al.], who reported [finding] [citation].
Similarly, [Author2 et al.] demonstrated [related finding] [citation].
[Address any discrepancies]
In contrast to [Author3 et al.], who found [different result] [citation], our study suggests [explanation].
This difference may be attributed to [methodological differences, population differences, etc.].
## Mechanistic Interpretation (Paragraph 4)
[Explain WHY these results might occur]
These findings may reflect [biological/clinical mechanism].
[Author et al.] previously showed that [mechanistic evidence] [citation],
which supports the hypothesis that [explanation].
[If speculative, use appropriate hedging: "may", "might", "could potentially"]
## Clinical/Practical Implications (Paragraph 5)
[What does this mean for practice?]
These results have several implications for [clinical practice / research / etc.].
First, [implication 1].
Second, [implication 2].
[If applicable: These findings suggest that clinicians should consider...]
## Limitations (Paragraph 6)
[Honest but constructive discussion of limitations]
This study has several limitations that should be considered.
First, [limitation 1 with mitigation if possible].
Second, [limitation 2].
[Frame constructively: "While [limitation], [mitigating factor]..."]
Common limitations to address:
- Sample size
- Single-center
- Retrospective design
- Selection bias
- Technical limitations
- Generalizability
## Future Directions (Paragraph 7)
[What should come next?]
Future studies should [specific actionable suggestion].
Prospective validation in [population] is warranted.
Additionally, [another future direction].
---
## Discussion References
[List all citations used in Discussion with note references]
```
### Writing Guidelines
- **Present tense**: General truths ("MRI enables...")
- **Past tense**: Specific studies ("Smith et al. found...")
- **Hedging**: Match to evidence strength
- **No new data**: All statistics should be in Results
### Literature Integration Phrases
**Agreement:**
- "Consistent with prior work [X], we found..."
- "Our findings support those of [X], who demonstrated..."
- "In line with [X], our results indicate..."
**Disagreement:**
- "In contrast to [X], our study suggests..."
- "Unlike [X], who reported..., we found..."
- "Our results differ from [X], possibly due to..."
**Extension:**
- "Our findings extend those of [X] by demonstrating..."
- "Building on work by [X], we show..."
- "While [X] established..., our study further demonstrates..."
## Step 4: Draft Abstract
Create `drafts/abstract.md`:
```markdown
# Abstract
## Background/Purpose
[2-3 sentences: Gap in knowledge + study objective]
[Clinical/scientific problem]. [What is unknown]. The purpose of this study was to [objective].
## Methods
[3-4 sentences: Design, population, key methods, statistics]
This [study design] included [n] patients from [setting]. [Key methods]. [Primary outcome measure]. [Statistical approach].
## Results
[3-4 sentences: Key findings with numbers]
[Primary finding with statistics]. [Secondary finding]. [Additional notable result].
## Conclusion
[1-2 sentences: Main takeaway + implication]
[Main conclusion]. [Clinical/research implication].
---
**Word Count**: [count]
**Keywords**: [keyword1], [keyword2], [keyword3], [keyword4], [keyword5]
```
### Abstract Guidelines
- **Standalone**: Understandable without reading paper
- **Specific**: Include key numbers (n, primary statistic, p-value)
- **Consistent**: Match paper content exactly
- **Past tense**: Throughout (this study was conducted)
- **No citations**: Never cite in abstract
- **No abbreviations**: Or define on first use
### Word Count Targets
| Section | Target |
|---------|--------|
| Background | 50-75 words 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.