paper-discourse-graphlisted

# Paper Discourse Graph Use this skill to review a paper section as a reader-state graph, not only as a linear outline. The goal is to see what each paragraph plants, what it pays off, where notation appears before intuition, and where a justification detour interrupts the main story. ## 1. Workflow ### 1.1 Establish scope Identify the source `.tex` file or section to audit. If the user wants discussion before editing, produce findings and proposed interventions only. Look for project-local guidance before running a generic pass: - `AGENT_REVIEW_BRIEF.md` - `docs/*review*brief*.md` - `tools/discourse_graph/profiles/*.json` - paper-specific profiles or terminology docs ### 1.2 Choose a profile Use the most specific available profile: 1. user-provided `--profile` 2. project-local profile, if present 3. bundled `references/profiles/cphast.json` for C-PHAST drafts 4. bundled `references/profiles/default_scientific_paper.json` Profiles define the central reader question, audience needs, domain terms, and topic checks. Keep project taste in profiles, not in the engine. For methods, theory, or appendix sections where paragraphs hand off to notation and equations, also read `references/formal_block_flow.md`. When authoring or revising source files and the user wants durable machine-readable breadcrumbs for later passes, read `references/source_semantic_comments.md`. For late-stage paragraph-by-paragraph refinement, task breakdowns for fresh agents, or requests to zoom into e