research-grounded-writing · git:20260922.e574d86 · 2026-09-22 · sha256 f32ff73b8a656cb0

research-grounded-writing git:20260922.e574d86A

Immutable. This exact content never changes and is served at /api/v1/blob/f32ff73b8a656cb0.

---
name: research-grounded-writing
description: Draft or substantially revise source-backed nonfiction explicitly requested as a finished writing artifact, such as an article, essay, profile, technical explainer, report, or decision memo. Exclude research-only requests, app playtests, working notes, link collections, and routine factual answers, even when saved as Markdown.
---

# Research-grounded writing

Support substantive claims in the requested artifact. Keep research proportional
to what the reader needs to assess the conclusions.

## Build the evidence

- Prefer direct records and primary sources. Add independent sources when they
  supply relevant criticism, corroboration, or a competing explanation.
- Distinguish direct observation, source claims, user-supplied context, and
  inference. Label uncertainty that could change the conclusion.
- Include dates, versions, sample, and coverage when they limit what a source
  proves. Missing evidence is not a zero result or proof of absence.
- Consider contrary evidence when it could overturn a material claim; do not
  collect opposing views merely to create balance.
- For comparisons, state the decision criteria and apply them consistently.
  Separate measured results from product claims and your recommendation.

## Attribute and check

Place a supporting link or citation beside the claim it supports. Paraphrase
faithfully; reserve quotations for wording that matters. Do not add irrelevant
sources to reach a citation count.

Before delivery, verify consequential factual claims and quotations against
their sources, including quantities, dates, causal language, and link targets.
Editing must not widen certainty beyond the evidence.

Stop when the requested artifact is supported and material uncertainties are
identified. Gather more evidence only when it could change a consequential
conclusion or resolve a missing requirement.

## Optional presentation advice

Organize around the reader's question rather than the order of research. Put
detailed provenance in an appendix only when readers need it. Apply a separate
editorial skill only when the requested writing benefits from that guidance.