writing-article-plans

Solid

Produce a detailed .md plan for an academic article that a separate drafter agent then writes section-by-section in LaTeX. This is the academic-writing analog of the superpowers brainstorming → writing-plans workflow: it first interviews the user one question at a time (thesis, contribution, article type, structure, scope), gets approval on a skeleton, then emits a task-decomposed plan that hands off to a fresh section-drafter subagent and downstream to lit-review-orchestrator, cite-placement, and, when it is installed, style-emulation. Use this whenever the user wants to plan, outline, structure, or scaffold a paper before drafting, or asks for 'a plan for a drafter', 'an article plan', 'a paper outline to draft from', 'plan this paper', or 'write up a plan for this article' — even if they don't say the skill name. Also use it in REVISION MODE when the user wants an existing draft restructured or substantively revised (reorganize sections, change or sharpen the argument, conform a manuscript to a genre struc

AI & Automation 24 stars 0 forks Updated 5 days ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
47
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# 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) │ ...

Details

Author
kennethkhoocy
Repository
kennethkhoocy/legal-scholarship-skills
Created
6 days ago
Last Updated
5 days ago
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category