evidence-driven-writing

Transform literature pools into citation-grounded manuscript arguments with evidence maps and paragraph blueprints.

Updated May 15, 2026
One-click install
npx skills add https://github.com/lth0/codexSkill --skill evidence-driven-writing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-driven-writing
Source: https://github.com/lth0/codexSkill/tree/main/skills/agents/research-writing/evidence-driven-writing
Command: npx skills add https://github.com/lth0/codexSkill --skill evidence-driven-writing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you write manuscript sections where claims must be traceable to specific citations, preventing unsupported or citation-light prose.

Core Features & Use Cases

  • Evidence map + coverage validation: structures sources into an evidence map and enforces evidence coverage before drafting.
  • Paragraph-level blueprinting: forces each paragraph to define role, main claim, evidence IDs, transitions, and forbidden content.
  • Introduction/Related Work argument patterns: generates publishable, theme-based argument flows instead of chronological paper dumps.
  • Process-to-text contamination firewall: prevents requirement/process notes from leaking into the final manuscript text.

Quick Start

Ask for an evidence-driven Introduction or Related Work section for your draft, and provide your literature pool so the skill can build the evidence map and paragraph blueprints first.

Frequently Asked Questions about evidence-driven-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a literature review with strong citation coverage for an academic manuscript?

To write a literature review with strong citation coverage, provide your literature pool so the tool can build an evidence map and paragraph blueprints before drafting manuscript arguments.

How do I structure an Introduction section so every claim is backed by specific sources?

To structure an Introduction section backed by specific sources, generate theme-based argument flows from an evidence map that links concrete claims to citation IDs before writing prose.

What is the best way to synthesize a literature pool into related work arguments without unsupported prose?

The best way to synthesize a literature pool into related work arguments without unsupported prose is enforcing evidence coverage validation and paragraph-level blueprints before generating text.

Can I generate theme-based argument flows for a related work section instead of chronological paper dumps?

Yes, you can generate theme-based argument flows for a related work section by mapping sources into an evidence map and defining paragraph roles, main claims, and transitions before drafting.

Do I need to provide an evidence map before drafting Introduction or background sections?

Yes, you must provide an evidence map with concrete claim-to-citation links and section-specific paragraph blueprints before prose is written for Introduction or background sections.

How to prevent process notes from contaminating the final manuscript text?

To prevent process notes from contaminating the final manuscript text, use a process-to-text contamination firewall that blocks requirement notes from leaking into the drafted prose.