plan-section
Skill1 starsChanged 3 months agoMITView on GitHub
Create a detailed writing plan for a section before drafting it. Use when the user wants to plan, outline, structure, or prepare a section before writing. Triggers on "plan the", "outline the", "what should I cover in", "how should I structure", "prepare to write".
In this repository13 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- factsSkill
- figureSkill
- full-reviewSkill
- ingestSkill
- onboardSkill
- researchSkill
- reviewSkill
- save-materialSkill
- statusSkill
- teachSkill
- verify-sourcesSkill
- writeSkill
The file
Files
/plan-section — Decide what to write before writing it
A plan is worth making because it exposes what is missing while the fix is still cheap. Its most valuable output is usually the list of gaps, not the outline.
Steps
- Read the context
.claude/rules/structure.md— the section's role and budgetdocs/requirements.md— what the institution expects here, and the assessment criteria this section is graded againstdocs/facts.md— the evidence available- The target file and both adjacent sections — what is already covered, so the plan does not duplicate it
docs/research/andresources/— the material on handdocs/feedback/— anything the supervisor already said about this section
Write the plan
- Argument — one paragraph stating what this section establishes and how it advances the document's central claim. If you cannot write this paragraph, the section is not ready to plan.
- Outline — subsections in order, with the point each one makes.
- Evidence and citations — for each claim, the specific source or the specific piece of the author's own analysis that supports it. Name files.
- Figures and tables — what is needed, what each shows, and its cost against the character budget if images count.
- Budget — the section total from
structure.md, split across subsections. - Dependencies — what must be written or decided first, and which cross-references to plan for.
- Gaps — claims with no source yet, analyses not yet run, decisions not yet made. Be concrete about what would close each one.
- Save to
docs/plans/plan_<section>_<YYYY-MM-DD>.md. - Report the plan in brief and lead with the blockers. If research is needed before drafting can start, say which
/researchquery to run.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

