writing-article-plans

Writing Article Plans

Overview

Write a comprehensive article plan assuming the drafter has zero context for the project and will write the manuscript one section at a time. The plan carries the whole argument down to the level of individual argument moves, so the drafter produces prose that realizes a decided argument rather than inventing one. This is the planning half of an academic-writing pipeline that mirrors the superpowers writing-plans → subagent-driven-development pattern.

Structure is first order here: the plan inherits its architecture — section skeleton, proportions, intro moves, footnote policy — from a per-genre structural profile extracted from a candidate manuscript (see "Genre Structural Profiles"). Prose style is entirely downstream: the drafter writes plain, correct prose and style-emulation restyles it later. A structural mistake, unlike a stylistic one, cannot be fixed downstream. In standalone mode there is no later restyle, so the drafter's plain, correct prose is the final prose: it still avoids authorial-voice mimicry, but its clarity and polish must reach delivery quality rather than a draft awaiting a restyle.

Position in the pipeline:

spec ──▶ [writing-article-plans]  ──▶ plan.md
                                        │
                                        ▼
                          section-drafter subagents ──▶ draft .tex (with % CITE slots)
                                        │
                                        ▼
                          lit-review-orchestrator   (find the literature; keyed pipeline, defaults)
                                        │
                                        ▼
                          cite-placement               (fill every % CITE slot; mode per the profile's citation architecture)
                                        │
                                        ▼
                          style-emulation           (restyle to author voice — the refinement)

The plan is always Markdown. The manuscript the drafter writes is LaTeX (main.tex + \input{sections/<name>.tex}), so it drops straight into the existing estout / latex-results pipeline.