Skip to content
Agentmart
Submit a tool

writing-plans

Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified.

Skill by Optima-CityU

IndexedBSD-3-Clause★ 677
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/optima-cityu-writing-plans

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified.

Use cases: documents, devops, writing, productivity, documentation, writing-editing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/writing-plans

What's inside

Skill name
writing-plans
Description
Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified.
License
BSD-3-Clause
Instructions
13 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Writing Plans

Before changing files, make a concise internal plan based on the user's requested output and the complete source document.

1. Identify the document's purpose, audience, main claims, constraints, causal relationships, examples, and reusable guidance.
2. Decide whether one coherent document is sufficient. Create child documents only for themes that can stand alone and are useful independently.
3. Map every important source section to the planned output so information is not silently dropped.
4. Preserve uncertainty and provenance. Never invent dates, facts, or conclusions.
5. Review the planned structure for repetition and fragmentation before writing.

The user's instructions override output-location conventions. If the user says not to create a plan file, keep the plan internal and write only the requested deliverables.

From Optima-CityU/LLM4AD_Next, BSD-3-Clause.

More from Optima-CityU/LLM4AD_Next

Signals

Stars
677
Forks
44
Open issues
1
Last commit (this folder)
Sep 20, 2026 (1 month ago)
Last release
Sep 29, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
BSD-3-Clause
Repository
github.com/Optima-CityU/LLM4AD_Next
Website
llm4ad-next.cn
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from Optima-CityU

Cite this page

writing-plans skill. Agent Mart. https://agentmart.dev/skills/optima-cityu-writing-plans (last updated 2026-10-24)