Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified.
Install Writing Plans
$ npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Optima-CityU/LLM4AD_Next writing-plans --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Optima-CityU/LLM4AD_Next.git skills-src && mkdir -p .claude/skills && cp -r skills-src/docker/knowledge-parser/skills/writing-plans .claude/skills/writing-plans && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "writing-plans" agent skill from https://github.com/Optima-CityU/LLM4AD_Next/tree/main/docker/knowledge-parser/skills/writing-plans into .claude/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Optima-CityU/LLM4AD_Next/tree/main/docker/knowledge-parser/skills/writing-plansType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Optima-CityU/LLM4AD_Next writing-plans --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Optima-CityU/LLM4AD_Next.git skills-src && mkdir -p .agents/skills && cp -r skills-src/docker/knowledge-parser/skills/writing-plans .agents/skills/writing-plans && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "writing-plans" agent skill from https://github.com/Optima-CityU/LLM4AD_Next/tree/main/docker/knowledge-parser/skills/writing-plans into .agents/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Optima-CityU/LLM4AD_Next writing-plans --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Optima-CityU/LLM4AD_Next.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/docker/knowledge-parser/skills/writing-plans .cursor/skills/writing-plans && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "writing-plans" agent skill from https://github.com/Optima-CityU/LLM4AD_Next/tree/main/docker/knowledge-parser/skills/writing-plans into .cursor/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Optima-CityU/LLM4AD_Next.git --path docker/knowledge-parser/skills/writing-plans--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Optima-CityU/LLM4AD_Next writing-plans --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Optima-CityU/LLM4AD_Next.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/docker/knowledge-parser/skills/writing-plans .gemini/skills/writing-plans && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/Optima-CityU/LLM4AD_Next/tree/main/docker/knowledge-parser/skills/writing-plans into .gemini/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Optima-CityU/LLM4AD_Next writing-plansInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Optima-CityU/LLM4AD_Next.git skills-src && mkdir -p .github/skills && cp -r skills-src/docker/knowledge-parser/skills/writing-plans .github/skills/writing-plans && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/Optima-CityU/LLM4AD_Next/tree/main/docker/knowledge-parser/skills/writing-plans into .github/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Optima-CityU/LLM4AD_Next writing-plans --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Optima-CityU/LLM4AD_Next.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/docker/knowledge-parser/skills/writing-plans .opencode/skills/writing-plans && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "writing-plans" agent skill from https://github.com/Optima-CityU/LLM4AD_Next/tree/main/docker/knowledge-parser/skills/writing-plans into .opencode/skills/writing-plans/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-plans", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
writing-plans- GitHub stars
- 574
- Token cost
- ~262 tokens
- SKILL.md length
- 122 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified.
- Works in 5 steps: Identify the document's purpose,… → Decide whether one coherent document is… → Map every important source section to… → …
- Tasks that involve Planning
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Writing Plans is an agent skill from Optima-CityU/LLM4AD_Next. Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified.
Its SKILL.md is about 260 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Planning. The repository describes itself as: A next-generation automatic algorithm design platform, making automated algorithm design more accessible and easier to use. The licence is BSD-3-Clause.
When your agent uses it
- Tasks that involve Planning
Example prompts
- “/writing-plans”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Identify the document's purpose, audience, main claims, constraints, causal relationships, examples, and reusable guidance.
- Decide whether one coherent document is sufficient. Create child documents only for themes that can stand alone and are useful…
- Map every important source section to the planned output so information is not silently dropped.
- Preserve uncertainty and provenance. Never invent dates, facts, or conclusions.
- Review the planned structure for repetition and fragmentation before writing.
What it can do on your machine
Read from SKILL.md and the folder at commit e3d3f7b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Writing Plans loads about 262 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 122 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Optima-CityU/LLM4AD_Next at commit e3d3f7b, republished under its BSD-3-Clause licence (© Optima-CityU). 122 words, ~262 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-plans/SKILL.md (or your agent's skills folder).- 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.
Writing Plans
Before changing files, make a concise internal plan based on the user's requested output and the complete source document.
- Identify the document's purpose, audience, main claims, constraints, causal relationships, examples, and reusable guidance.
- Decide whether one coherent document is sufficient. Create child documents only for themes that can stand alone and are useful independently.
- Map every important source section to the planned output so information is not silently dropped.
- Preserve uncertainty and provenance. Never invent dates, facts, or conclusions.
- 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.
© Optima-CityU, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in docker/knowledge-parser/skills/writing-plans of Optima-CityU/LLM4AD_Next.
Open the folder on GitHubat commit e3d3f7b
Compare with similar skills
Writing Plans next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Writing Plans this skillOptima-CityU/LLM4AD_Next | 574 | — | ~262 | Automated safety check: Pass | BSD-3-Clause | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 105k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 72k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 58 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 38 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Writing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Planning With Files
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
More from Optima-CityU/LLM4AD_Next
All 24 skills in this repoProposal Foundation Layout
Optima-CityU/LLM4AD_Next
A skill your agent uses when establishing a research proposal's project foundation, submission constraints, and presentation system before section drafting begins.
Llm4ad Task Builder
Optima-CityU/LLM4AD_Next
A skill your agent uses when a user wants to build an LLM4ADNext task package — a runnable directory that lets the LLM4AD platform evolve an algorithm for their problem.
Document Knowledge Organizer
Optima-CityU/LLM4AD_Next
Organize one or more Markdown source documents into high-fidelity, editable knowledge blocks.
Proposal Final Review
Optima-CityU/LLM4AD_Next
A skill your agent uses when assembling a completed staged Typst proposal and checking its evidence, logic, citations, structure, and export readiness.
Proposal Foundation Feasibility
Optima-CityU/LLM4AD_Next
A skill your agent uses when documenting a proposal's research foundation, available conditions, team support, feasibility, and risk controls from author-supplied facts.
Proposal Innovation Plan
Optima-CityU/LLM4AD_Next
A skill your agent uses when distilling a proposal's innovations and defining milestones, annual plans, contingency points, and expected outcomes.
Related
Categories
Questions about Writing Plans
What does Writing Plans do?
Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified. Writing Plans is an agent skill from Optima-CityU/LLM4AD_Next. Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide whether child documents are justified.
When should I use Writing Plans?
Writing Plans fits situations like: tasks that involve Planning.
How do I install Writing Plans in Claude Code?
Run `npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a claude-code`. Or copy the skill folder (docker/knowledge-parser/skills/writing-plans in Optima-CityU/LLM4AD_Next) into .claude/skills/writing-plans in your project. Claude Code loads it when a task matches its description.
How do I install Writing Plans in Codex?
Run `npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a codex`. Or copy the skill folder (docker/knowledge-parser/skills/writing-plans in Optima-CityU/LLM4AD_Next) into .agents/skills/writing-plans in your project. Codex loads it when a task matches its description.
Can I use Writing Plans in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Optima-CityU/LLM4AD_Next --skill writing-plans -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/writing-plans, .gemini/skills/writing-plans, .github/skills/writing-plans and .opencode/skills/writing-plans in your project.
What does Writing Plans need to run?
SKILL.md names no scripts, command-line tools or credentials: Writing Plans is instructions for the agent only.
Does Writing Plans access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Writing Plans safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Writing Plans use?
Writing Plans is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Writing Plans use?
About 262 tokens (SKILL.md is roughly 1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Writing Plans?
Skills that share tags, products or a category with Writing Plans: Executing Plans Inline (obra/superpowers, 297k stars), Interview Me (addyosmani/agent-skills, 105k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 72k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Plans?
Optima-CityU (a GitHub organization) maintains it in Optima-CityU/LLM4AD_Next, which has 574 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 9, 2026.
Source: Optima-CityU/LLM4AD_Next on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.