writing-plans
Writing Plans
Overview
Convert an approved IMRAD outline into an executable task list for drafting. Input: .writing/outline.md (structure + key claims), .writing/metadata.yaml (reporting guideline + Zotero config), .writing/claims/section_*.md (stub claims per section). Output: .writing/plan.md — the single source of truth for drafting. The plan enumerates per-section prose tasks, per-figure generation tasks, per-table assembly tasks, an explicit dependency table, and a Parallelism Groups analysis that the drafting skill consumes when deciding how many sections to draft in parallel.
Write comprehensive plans assuming the drafter has zero context for the paper's argument and questionable taste. Document everything they need: which files to read and write for each task, which claims back each paragraph, how to verify. Bite-sized tasks. Claim-first. Frequent commits.
Announce at start: "I'm using the writing-plans skill to decompose the outline into an executable plan."
Context: Optionally runs in a dedicated worktree (user chooses during brainstorming).
Save plan to: .writing/plan.md
Claim-first protocol: see
superpower-writing:main§Claim-First Protocol.