related-work-writing

Included with Lifetime

$97 forever

Write Related Work sections that compare and contrast prior work with your approach. Organize by theme, cite broadly, and explain how your work differs. Use when writing or improving the Related Work section of a paper.

Writing & Docs

What this skill does


# Related Work Writing

Generate publication-quality Related Work sections with proper citations and thematic organization.

## Input

- `$0` — Current paper draft or method description
- `$1` — Collected literature (BibTeX entries, paper summaries, or literature review notes)

## References

- Related work writing prompts and strategies: `~/.claude/skills/related-work-writing/references/related-work-prompts.md`

## Workflow

### Step 1: Analyze the Paper's Contributions
- Read the current paper draft (especially Methods and Introduction)
- Identify the key contributions and novelty claims
- List the technical components that need literature context

### Step 2: Organize Literature by Theme
Group related papers into thematic clusters:
- Each cluster should represent a research direction or technique
- Common themes: problem formulation, methodology family, application domain, evaluation approach
- Order themes from most to least relevant to your work

### Step 3: Write Each Theme Paragraph
For each thematic group:
1. **Topic sentence** — Introduce the research direction
2. **Describe key works** — Summarize 2-5 representative papers
3. **Compare and contrast** — How does each approach differ from yours?
4. **Transition** — Connect to the next theme or to your contribution

### Step 4: Refine
- Ensure every cited paper has a clear reason for inclusion
- Check that your work's novelty is clear from the comparisons
- Verify all `\cite{}` keys exist in the `.bib` file
- Aim for 1-2 pages (single column) or 0.5-1 page (double column)

## Rules

- **Compare and contrast, don't just describe** — "Unlike [X] which assumes..., our method..."
- **Organize by theme, not chronologically** — Group by research direction
- **Cite broadly** — Not just the most popular papers; include recent and diverse work
- **Be fair** — Acknowledge strengths of prior work before stating limitations
- **Explain inapplicability** — If a method could apply to your setting, explain why you don't compare experimentally, or add it to experiments
- **Use present tense for established facts** — "Smith et al. propose..." or "This approach uses..."
- **End with positioning** — The final paragraph should clearly position your work relative to all discussed prior work

## Related Skills
- Upstream: [literature-search](../literature-search/), [literature-review](../literature-review/), [citation-management](../citation-management/)
- Downstream: [paper-writing-section](../paper-writing-section/)
- See also: [survey-generation](../survey-generation/)

Files: 2

Size: 6.7 KB

Complexity: 25/100

Category: Writing & Docs

Source: https://github.com/lingzhi227/agent-research-skills/tree/main/skills/related-work-writing

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts