Writing Draft

Writing Draft

Expand detailed section outlines into prose, one section at a time, using domain-specific style rules.

Prerequisites: PRECIS.md, OUTLINE.md, ACTIVE_WORKFLOW.md, and at least one section outline in outlines/ must exist.

Shared Enforcement

Read the constraint index: ${CLAUDE_PLUGIN_ROOT}/references/writing-common-constraints.md

Then load these phase-specific files:

Constraints:

• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/progressive-expansion-hierarchy.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/constraint-loading-protocol.md — CRITICAL: load domain skill + ai-anti-patterns before writing prose
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/flowchart-authority.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/no-pause-between-phases.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/progress-gating.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/topic-change-protocol.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/writing-stop-triggers.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/drive-aligned-default.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/context-monitoring.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/deviation-rules.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/constraints/claim-id-traceability.md

Conventions:

• Read ${CLAUDE_PLUGIN_ROOT}/references/conventions/gate-function-standard.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/conventions/phase-summary-frontmatter.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/conventions/checkpoint-type-classification.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/conventions/autonomous-phase-chaining.md
• Read ${CLAUDE_PLUGIN_ROOT}/references/conventions/iteration-topology.md

Draft Flowchart (This IS the Spec)

START (all section outlines in outlines/ exist)
  │
  ├─ Step 1: Load context (PRECIS, OUTLINE, ACTIVE_WORKFLOW)
  │
  ├─ Step 2: Load domain skill (legal/econ/general)
  │
  ├─ Step 3: Choose strategy (sequential/parallel/key-first)
  │
  ├─ Step 4: For each section with outline:
  │  ├─ Read outline from outlines/[Section].md
  │  ├─ Cross-reference with PRECIS claim
  │  ├─ Expand ALL outline points into prose
  │  │  └─ Every POINT → paragraph(s)
  │  │  └─ Every EVIDENCE → cited in prose
  │  │  └─ Every TRANSITION → explicit bridge
  │  ├─ Save to drafts/[Section] (Draft).md
  │  ├─ Self-check: covers all outline points? cursory or developed?
  │  └─ 5+ iterations same section? → ESCALATE to user
  │
  ├─ Step 5: Update ACTIVE_WORKFLOW.md
  │
  └─ GATE: All OUTLINE sections have drafts/ files with substance?
     ├─ NO → Identify gap, re-draft (no pause)
     └─ YES → Load writing-validate → Validate claim coverage → Then /writing-review

If text and flowchart disagree, the flowchart wins.

NO PROSE WITHOUT OUTLINE. Every section must have a detailed outline in outlines/ BEFORE you write prose for it. This is not negotiable.

If you find yourself drafting without a matching outline file:

1. STOP immediately
2. DELETE what you wrote
3. Create the outline first using writing-outline
4. THEN draft the prose

Writing without an outline produces incoherent, wandering prose that requires complete rewriting.

Reporting sections complete without verifying every outline point was expanded is NOT HELPFUL — the user publishes a draft with gaps that reviewers catch.

Before claiming a section is drafted:

1. Open the outline file for that section
2. Check off EVERY subsection point — is it in the prose?
3. Check off EVERY evidence item — is it cited in the prose?
4. Check the word count — does it match the outline's estimate?

If ANY point or evidence is missing, the section is NOT complete. Saying "draft done" when outline points were skipped wastes the user's time — they discover gaps during review that should never have survived drafting. The outline is a contract; the draft must fulfill it.

EACH SECTION DESERVES FULL ATTENTION. Do not rush through sections to "finish" the draft. This is not negotiable.

The failure mode: a single agent writes cursory 2-paragraph versions of every section to reach "draft complete" as fast as possible. This is reward hacking - optimizing for the appearance of completion without the substance.

Each section must:

• Expand EVERY point from the outline (not a subset)
• Include EVERY piece of evidence mapped in the outline
• Develop transitions between subsections
• Meet the word count target from the outline

If you catch yourself writing a section significantly shorter than the outline implies, STOP. You are being cursory. Go back to the outline and expand every point.

Session Resume Detection

Before starting, check for an existing handoff:

1. Check if .planning/HANDOFF.md exists
2. If found: Read it and present to user:
   • Show the phase, section in progress, and Next Action
   • Ask: "Resume from handoff, or start fresh?"
   • If resume: skip to the recorded section
   • If fresh: proceed normally
3. If not found: Proceed normally

Process

Step 1: Load Context

Read(".planning/ACTIVE_WORKFLOW.md")
Read(".planning/PRECIS.md")
Read(".planning/OUTLINE.md")

Step 2: Load Domain Skill

Based on style in ACTIVE_WORKFLOW.md, load the domain skill that governs prose style (relative to this skill's base directory):

When style: legal is detected:

1. MUST Read the full skill file: Discover path: ${CLAUDE_PLUGIN_ROOT}/skills/writing-legal/SKILL.md, then Read() the output.

2. MUST use template for .docx export:

   ../writing-legal/templates/law_review_template.docx
   

3. Iron Laws from writing-legal:

   • NO DOCX WITHOUT TEMPLATE - Copy template first, then add content
   • NO CLAIM WITHOUT COUNTERARGUMENTS - Confront objections
   • NO SECONDARY CITATIONS - Read original sources

If you create a legal docx without reading the skill and using the template, DELETE IT and START OVER.

When style: econ is detected:

1. MUST Read the full skill file: Discover path: ${CLAUDE_PLUGIN_ROOT}/skills/writing-econ/SKILL.md, then Read() the output.

2. Iron Laws from writing-econ:

   • NO BOILERPLATE - Delete "This paper discusses...", roadmap paragraphs
   • NO ELEGANT VARIATION - One concept = one word, always
   • HOOK WITH FINDING - Start with compelling result, not background

3. Delete & Restart triggers:

   • "This paper discusses..." → DELETE, start with finding
   • Table-of-contents paragraph → DELETE
   • "As we shall see..." → DELETE

If you write boilerplate in an econ paper, DELETE THE SECTION and START OVER with a hook.

Step 2b: Load Universal Constraints

Skill(skill="workflows:ai-anti-patterns")

You MUST load ai-anti-patterns before drafting. Domain skills catch domain-specific issues; ai-anti-patterns catches AI writing smell (hedging, filler, false balance, weasel words). Both layers are required — see constraints/constraint-loading-protocol.md for why.

Step 3: Choose Drafting Strategy

Use AskUserQuestion to determine approach:

AskUserQuestion(questions=[
  {
    "question": "How should we draft the sections?",
    "header": "Strategy",
    "options": [
      {"label": "Sequential (Recommended)", "description": "Draft sections one at a time in order. Best for maintaining argument flow."},
      {"label": "Agent team (parallel)", "description": "Spawn teammate per section for parallel drafting. Best for long documents with independent sections. Requires reconciliation pass afterward."},
      {"label": "Key section first", "description": "Start with the core argument section, then build outward. Best when the central claim needs to be strongest."}
    ],
    "multiSelect": false
  }
])

Sequential Drafting (Default)

For each section with a completed outline, in order:

1. Read the section outline: Read("outlines/[Section] (Outline).md")
2. Cross-reference with PRECIS: Which claim does this section advance?
3. Write prose: Expand the outline into full paragraphs, following domain style rules
   • Every outline point becomes at least one paragraph
   • Every piece of evidence from the outline appears in prose
   • Transitions between subsections are explicit
4. Save to drafts/: Write("drafts/[Section] (Draft).md", content)
5. Self-check: Does the draft cover every point in the outline? Is it cursory or developed?

After completing each section, IMMEDIATELY start the next section. Do NOT:

• Ask "should I continue?"
• Summarize what you just wrote
• Wait for confirmation

Pausing between sections is procrastination disguised as courtesy.

Agent Team Drafting (Parallel)

For parallel drafting using agent teams, read the full protocol:

Read ${CLAUDE_PLUGIN_ROOT}/skills/writing-draft/references/parallel-drafting.md and follow its instructions.

When to use: Document has 5+ substantive sections, sections are relatively independent, and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is enabled. Falls back to Sequential if unavailable.

Key Section First

1. Identify the core argument section (usually the "Proof" or main claim section)
2. Draft it first with full attention
3. Then draft surrounding sections that support it
4. Introduction and conclusion last (they frame the core)

Step 4: Update Workflow State

After each section, update .planning/ACTIVE_WORKFLOW.md:

phase: draft
current_section: [section name]
sections_drafted:
  - [list of completed sections]
edits_since_verify: 0

Gate: Exit Draft

Before proceeding to edit/verify (see conventions/gate-function-standard.md for the full 6-step gate including SUMMARY):

1. IDENTIFY: Draft files in drafts/ for all sections listed in OUTLINE.md
2. RUN: List files in drafts/, compare against OUTLINE.md sections
3. READ: Check each draft exists and has substantial content (not cursory stubs)
4. VERIFY: All sections have drafts, each draft covers all outline points
5. CLAIM: Only if steps 1-4 pass, proceed to writing-validate

Reporting "all sections drafted" without checking each file is NOT HELPFUL — the user moves to review with missing sections that force a return to drafting. You must verify every draft exists and has real content.

Staged Draft Verification (If Gate Fails)

If a section fails the gate:

Re-draft WITHOUT pausing. Agent re-opens outline, re-reads PRECIS.md, expands section with full depth.

No iteration limit at draft stage. Cheap iterations here prevent expensive rework later.

Skipping the subsection expansion check is NOT HELPFUL — the user publishes a stub where a full section should be. A 2-paragraph section with a 5-subsection outline is a stub, not a draft.

Progress Gating

If 5+ iterations on the same section without meaningful progress, STOP and escalate to the user for scope adjustment.

Signs you are stuck:

• Redrafting the same section repeatedly without quality improvement
• Failing the gate check on the same points across iterations
• Outline points that resist expansion (evidence may be insufficient)
• Section keeps growing without advancing the PRECIS claim

When escalating, present:

• What you've tried (briefly)
• Where the section is stuck
• Options: simplify the section, return to outline phase, merge with adjacent section, or gather more sources

Spinning without progress is anti-helpful. Five iterations is the threshold for asking the user if scope needs adjustment.

Deviation Rules

When drafting reveals unplanned issues, follow this 4-rule system:

Priority: R4 (STOP) > R1-R3 (auto) > unsure → R4.

Edge cases:

• Missing footnote for existing claim → R2 (add evidence)
• Entire section doesn't fit the argument → R4 (restructuring)
• Cross-reference to nonexistent section → R3 (structural blocker)
• Claim contradicts evidence found during drafting → R4 (argument restructuring)
• Typo in citation → R1 (factual error)
• Section too long, needs splitting → R3 (structural) unless it changes the argument flow → R4

Tracking format per section: Each section's draft summary should include: Deviations: N auto-fixed (R1: X, R2: Y, R3: Z). R4 escalations: [list or "none"].

Rationalization Table

Red Flags - STOP If You Catch Yourself:

Why Skipping Hurts the Thing You Care About Most

Next Phase

After all sections are drafted:

Read ${CLAUDE_PLUGIN_ROOT}/skills/writing-validate/SKILL.md and follow its instructions. Follow its instructions to validate claim coverage before review.