refine

Refine, Clear Confusions & Re-sync

Make the content in $ARGUMENTS clear, tight, and internally consistent — and keep every platform asset faithful to the locked master content. Most "this is lousy" complaints are a structure problem, not an ideas problem — so preserve the thinking and the voice; fix how it's organized and whether it holds together.

Restructure a rough or overlong draft

When the complaint is "too long, no sections, people get lost":

• Add ## section headers across the major beats so a scanner always knows where they are. Headers are the single biggest fix for lost readers.
• Give enumerated history or steps bold one-line lead-ins so the section scans when skimmed.
• Break long reflective runs into shorter paragraphs with breathing room.
• Pull the single most quotable line into a > blockquote.
• Do not touch a strong ending. If the last line lands, leave it exactly as is.
• Keep first-person voice, distinctive phrasing, and the person's own metaphors intact.

Confirm the rewrite level first — light polish, restructure-keep-ideas, or aggressive rework — and stay within it.

Clear confusions in the argument

• Catch contradictions and self-undercutting lines — e.g. a framing that fights the thesis.
• Hunt duplicate transitions and leftover lines from earlier edits (two stacked "Then came X…" sentences doing the same job is the classic tell).
• Resolve muddled or contestable claims — tighten anything imprecise; strip pedantry-bait (hard figures, contestable dates) unless load-bearing.
• Keep the running example identical — the same concrete example must appear in every snippet and every platform. A swapped or half-swapped example is a classic drift bug; if the example changes, change it everywhere.

Consistency & change-protocol pass across assets

This is the step most often skipped, and it's where the "content first" rule is enforced.

• When framing or wording changes, propagate it across every asset, not just the one being edited. The common failure: fixing a phrase on one carousel slide but leaving the same rejected phrase in the caption, the essay title, and the essay body. The package only feels coordinated if the spine reads identically everywhere — hook, caption, title, and closing all in agreement.
• A content change is a master-content change. If the person asks to alter the substance after platform posts already exist, do not patch a single platform. Update the locked master content first (back in explore), re-confirm it with the person, then regenerate the LinkedIn, Substack, and Medium assets from the new master so all three stay in sync.
• Re-check the design hand-off too. If sections were added, removed, or reordered, the per-section image briefs from design-brief are now stale — flag that they need regenerating.
• Series continuity: confirm the call-back to the previous piece and the tease for the next still read correctly after edits.