PaperLab Chapter Flow Editor
When to Use
USE WHEN: improving chapter structure, transitions, case continuity, or the
overall reading path of a PaperLab book. This skill is useful after source
coverage, figure generation, and notebook execution have already produced enough
material, but before final typesetting.
DO NOT USE for: rewriting scientific claims without validation, changing
numerical results, or deleting pedagogical repetition without review.
Chapter Arc
Each chapter should have a visible arc:
- Opening contract: what engineering decision or student capability the
chapter supports.
- Concept foundation: the minimum theory, terminology, and physical logic.
- Engineering method: equations, workflow, or design procedure.
- Computational or case example: a worked use of the method.
- Decision consequence: what the result changes for concept selection,
operation, risk, or economics.
- Transfer forward: how the output is reused in later chapters.
Flow Checks
Review the chapter for:
- abrupt section starts that need a one-sentence bridge,
- equations introduced before variables or intuition,
- figures placed before the concept needed to read them,
- repeated background that should become a cross-reference,
- case-study material that conflicts with the canonical case thread,
- summaries that repeat headings instead of synthesizing decisions,
- generated source or lecture-checkpoint texture in the main reading path.
Case Thread Pattern
When a recurring case is used across chapters, keep a small handoff pattern:
**Case handoff.** This chapter uses <input> from Chapter N, calculates <result>,
and carries <output> forward to Chapter M where it becomes <later use>.
Use this sparingly. One handoff per case-heavy chapter is usually enough.
Repetition Policy
Some repetition is useful for students; uncontrolled repetition is not. Keep:
- definitions that prevent a chapter from becoming inaccessible,
- summaries in review and exam-preparation chapters,
- short reminders before major calculations.
Compress or move:
- duplicate background paragraphs,
- repeated slide-topic inventories,
- repeated captions or figure explanations,
- repeated "NeqSim implementation" boilerplate that does not add chapter-specific value.
Output Pattern
## Chapter Flow Review: <chapter>
- Status: ready | minor-revision | major-revision
- Chapter arc: <one-sentence assessment>
- Strongest transition: <section or paragraph>
- Weakest transition: <section or paragraph>
- Repetition to keep: <why it helps students>
- Repetition to compress: <what to replace with cross-reference>
- Case-thread action: <none or specific handoff edit>
Editing Rules
- Preserve citations, figure references, equation labels, and NeqSim traceability markers.
- Do not move figures away from their discussion blocks.
- When removing repeated text, keep one canonical explanation and replace the
secondary copy with a short cross-reference.
- Prefer one clean bridge sentence over a long transitional paragraph.
1---2name: paperlab-chapter-flow-editor-23description: |4 Edit PaperLab book chapters for narrative flow, chapter arc, section order,5 transitions, recurring case threads, and controlled repetition. Use when a6 chapter is technically correct but still feels like assembled lecture notes.7metadata:8 source: https://skillmd.com/skills/equinor/paperlab-chapter-flow-editor-29---1011# PaperLab Chapter Flow Editor1213## When to Use1415USE WHEN: improving chapter structure, transitions, case continuity, or the16overall reading path of a PaperLab book. This skill is useful after source17coverage, figure generation, and notebook execution have already produced enough18material, but before final typesetting.1920DO NOT USE for: rewriting scientific claims without validation, changing21numerical results, or deleting pedagogical repetition without review.2223## Chapter Arc2425Each chapter should have a visible arc:26271. **Opening contract**: what engineering decision or student capability the28 chapter supports.292. **Concept foundation**: the minimum theory, terminology, and physical logic.303. **Engineering method**: equations, workflow, or design procedure.314. **Computational or case example**: a worked use of the method.325. **Decision consequence**: what the result changes for concept selection,33 operation, risk, or economics.346. **Transfer forward**: how the output is reused in later chapters.3536## Flow Checks3738Review the chapter for:3940- abrupt section starts that need a one-sentence bridge,41- equations introduced before variables or intuition,42- figures placed before the concept needed to read them,43- repeated background that should become a cross-reference,44- case-study material that conflicts with the canonical case thread,45- summaries that repeat headings instead of synthesizing decisions,46- generated source or lecture-checkpoint texture in the main reading path.4748## Case Thread Pattern4950When a recurring case is used across chapters, keep a small handoff pattern:5152```markdown53**Case handoff.** This chapter uses <input> from Chapter N, calculates <result>,54and carries <output> forward to Chapter M where it becomes <later use>.55```5657Use this sparingly. One handoff per case-heavy chapter is usually enough.5859## Repetition Policy6061Some repetition is useful for students; uncontrolled repetition is not. Keep:6263- definitions that prevent a chapter from becoming inaccessible,64- summaries in review and exam-preparation chapters,65- short reminders before major calculations.6667Compress or move:6869- duplicate background paragraphs,70- repeated slide-topic inventories,71- repeated captions or figure explanations,72- repeated "NeqSim implementation" boilerplate that does not add chapter-specific value.7374## Output Pattern7576```markdown77## Chapter Flow Review: <chapter>7879- Status: ready | minor-revision | major-revision80- Chapter arc: <one-sentence assessment>81- Strongest transition: <section or paragraph>82- Weakest transition: <section or paragraph>83- Repetition to keep: <why it helps students>84- Repetition to compress: <what to replace with cross-reference>85- Case-thread action: <none or specific handoff edit>86```8788## Editing Rules8990- Preserve citations, figure references, equation labels, and NeqSim traceability markers.91- Do not move figures away from their discussion blocks.92- When removing repeated text, keep one canonical explanation and replace the93 secondary copy with a short cross-reference.94- Prefer one clean bridge sentence over a long transitional paragraph.