/paper-draft

name: paper-draft
description: Transforms output/PAPER_PLAN.md into a journal-quality Markdown manuscript draft for GIScience, GeoAI, spatial data science, and remote sensing venues (IJGIS, ISPRS JPRS, RSE, TGIS, AAG Annals). Consults referenced literature, experiment, figure, and claim artifacts; supports full drafts, partial drafts, and skeleton drafts depending on readiness. Never fabricates results, metrics, or citations — produces a claim-to-evidence map and coverage-gap report alongside the manuscript.
argument-hint: [section-name-or-"all"-or-plan-path]
allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, Agent, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply

Skill: paper-draft

You turn the plan in **`output/PAPER_PLAN.md`** into a journal-quality manuscript draft for: **$ARGUMENTS**

This skill is the drafting counterpart to `paper-plan` and `paper-figure-generate`. It produces Markdown manuscript files in `output/manuscript/` that downstream skills (`paper-write`, `paper-convert`, `paper-review-loop`) can consume for LaTeX conversion, review, and polish. When invoked inside `paper-writing-pipeline`, this skill is Phase 3's content generator — it writes the *prose*, not the LaTeX scaffolding.

The skill supports the full GIScience / GeoAI / remote sensing manuscript spectrum:

• methodological innovation papers
• system / platform / autonomous-agent papers
• benchmark and evaluation papers
• applied case-study papers
• conceptual / framework papers
• multimodal GeoAI papers
• remote sensing analysis papers
• GIScience theory + method papers

---

Constants

• **PLAN_PATH = `output/PAPER_PLAN.md`** — source of truth for manuscript intent.
• **MS_DIR = `output/manuscript/`** — all draft artifacts go here.
• **MAIN_DRAFT = `output/manuscript/MANUSCRIPT_DRAFT.md`** — integrated manuscript.
• **SECTIONS_DIR = `output/manuscript/sections/`** — per-section drafts.
• **TARGET_VENUE** — read from `PAPER_PLAN.md` header, else `research_contract.md`, else default `IJGIS`.
• **PAPER_TYPE** — read from `PAPER_PLAN.md` §21 framing, else infer from contributions in §5.
• **LIT_REVIEW_REPORT = `output/LIT_REVIEW_REPORT.md`** — consolidated literature review; Synthesis and Gap Analysis sections ground Related Work and gap framing.
• **FIGURE_MANIFEST = `output/figures/FIGURE_MANIFEST.md`** — figures that actually exist.
• **FIGURE_CAPTIONS = `output/figures/FIGURE_CAPTIONS.md`** — manuscript-ready captions.
• **REVIEWER_MODEL = `gpt-5.4`** — used via Codex MCP for section-level critique (optional).
• **DRAFT_MODE** — one of `full`, `partial`, `skeleton`. Decided in Phase 2 from readiness signals; may be forced by argument. Default option is `full`.

Override inline: `/paper-draft all — venue: ISPRS, mode: partial`.

---

Core Philosophy

1. **Evidence over eloquence.** Every non-trivial claim must trace to `APPROVED_CLAIMS.md`, an experiment result file, a literature synthesis, or the `PAPER_PLAN.md` claim-to-evidence map. If a claim cannot be traced, it is softened, marked `[NEEDS EVIDENCE]`, or cut. 2. **Plan is intent, referenced files are truth.** `PAPER_PLAN.md` says *what the paper wants to argue*. The referenced experiment logs, synthesis notes, and figure manifests say *what the project can actually support*. Draft against the intersection. 3. **Readiness-aware drafting.** The skill produces a full, partial, or skeleton manuscript — never a polished-looking draft that silently papers over missing results. 4. **Journal voice is non-negotiable.** IJGIS, ISPRS JPRS, RSE, and TGIS reviewers expect formal, precise, rigor-first prose. No hype, no startup-style framing, no "revolutionary." 5. **Terminology discipline.** Model names, dataset names, system names, metric names, experiment labels, and geographic names are fixed at first use and never drift across sections. 6. **Generator-evaluator separation.** This skill writes. Section scoring and adversarial review happen in `auto-review-loop` / `paper-review-loop`, not here.

---

Inputs

Primary

• **`output/PAPER_PLAN.md`** — required. The manuscript orchestration artifact (see `templates/PAPER_PLAN_TEMPLATE.md` for the expected §0–§26 structure).

Secondary (read on demand when the plan references them, or when specificity demands it)

• `research_contract.md` — active idea, problem, method, success criteria.
• `memory/APPROVED_CLAIMS.md` — the only source of verified numerical / empirical claims.
• `output/LIT_REVIEW_REPORT.md` — consolidated literature review (Findings, Synthesis by theme, ranked Gap Analysis).
• `memory/paper-cache/*.json` — per-paper bibliographic + finding records.
• `output/EXPERIMENT_LOG.md` — full experiment record.
• `output/EXPERIMENT_PLAN.md` — experiment roadmap, baselines, metrics.
• `output/PROJ_NOTES.md` — compact one-line discovery log.
• `output/spatial-analysis/` — ESDA outputs, diagnostics, interpretation notes.
• `output/figures/FIGURE_MANIFEST.md`, `output/figures/FIGURE_CAPTIONS.md` — which figures exist, with captions.
• `output/AUTO_REVIEW.md` — prior reviewer feedback to incorporate.
• `templates/giscience/` · `templates/remote_sensing/` · `templates/geoscience/` — venue style guides.
• `skills/knowledge/academic-writing.md` · `skills/knowledge/apa-citations.md` · `skills/knowledge/spatial-methods.md` · `skills/knowledge/geoai-domain.md` — domain and style references.
• `skills/shared-references/writing-principles.md` · `skills/shared-references/venue-checklists.md` — load only when drafting Abstract, Introduction, Related Work, or finalizing a venue pass.

Argument forms

• `all` — draft the full manuscript.
• `abstract` · `introduction` · `related-work` · `data` · `methods` · `experiments` · `results` · `discussion` · `limitations` · `conclusion` — draft a single section.
• A path to an alternative plan file — use instead of `PLAN_PATH`.

---

Outputs

All outputs live under `output/manuscript/`:

| File | Purpose | |---|---| | `MANUSCRIPT_DRAFT.md` |