evidence-driven-writing

1# Evidence-Driven Writing
2 
3This skill turns a literature pool into manuscript argument. It is required for Introduction, Related Work, and any background section with citations.
4 
5## Hard Gate
6 
7Do not write the section until an evidence map and paragraph blueprint exist.
8 
9Required artifacts:
10 
11- `refs/evidence-map.md` or `plan/evidence-map.md`
12- `plan/chapter-blueprints/<section>-blueprint.md`
13- `plan/review/evidence-coverage.md`
14 
15## Evidence Map
16 
17Create one row per usable source:
18 
19| Source ID | Citation | Source type | Abstract-level finding | Usable fact | Supported claim | Citation slot | Risk |
20|---|---|---|---|---|---|---|---|
21 
22Rules:
23 
24- Use the user's literature pool first.
25- Use only information present in title, abstract, DOI metadata, or user-provided notes unless full text is available.
26- One citation must support one concrete claim, not a vague field statement.
27- Mark weak or indirect support as `Risk: indirect`.
28 
29## Paragraph Blueprint
30 
31For each paragraph, define:
32 
33```markdown
34### Paragraph N
35- Role: context / method landscape / limitation / gap / contribution
36- Main claim:
37- Evidence IDs:
38- Contrast or transition:
39- Forbidden content:
40```
41 
42Only after the blueprint is complete may manuscript prose be written.
43 
44## Introduction Pattern
45 
46A publishable technical Introduction usually follows this chain:
47 
481. Application context and why the problem matters, supported by foundational or survey citations.
49…