Planning
championswimmer/pi-context-prune
Create and execute phased implementation plans stored in .agents/plans using numbered markdown files with YAML front matter and checklist steps.
Opens Plannotator's annotation UI on a markdown file, HTML file, URL or folder, then reads the decision and feedback you send back and acts on it.
Install Plannotator Annotate
$ npx skills add backnotprop/plannotator --skill plannotator-annotate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install backnotprop/plannotator plannotator-annotate --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/backnotprop/plannotator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/apps/skills/claude/plannotator-annotate .claude/skills/plannotator-annotate && 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 "plannotator-annotate" agent skill from https://github.com/backnotprop/plannotator/tree/main/apps/skills/claude/plannotator-annotate into .claude/skills/plannotator-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-annotate", 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/backnotprop/plannotator/tree/main/apps/skills/claude/plannotator-annotateType 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 backnotprop/plannotator --skill plannotator-annotate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install backnotprop/plannotator plannotator-annotate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/plannotator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/apps/skills/claude/plannotator-annotate .agents/skills/plannotator-annotate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plannotator-annotate" agent skill from https://github.com/backnotprop/plannotator/tree/main/apps/skills/claude/plannotator-annotate into .agents/skills/plannotator-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-annotate", 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 backnotprop/plannotator --skill plannotator-annotate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install backnotprop/plannotator plannotator-annotate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/plannotator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/apps/skills/claude/plannotator-annotate .cursor/skills/plannotator-annotate && 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 "plannotator-annotate" agent skill from https://github.com/backnotprop/plannotator/tree/main/apps/skills/claude/plannotator-annotate into .cursor/skills/plannotator-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-annotate", 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/backnotprop/plannotator.git --path apps/skills/claude/plannotator-annotate--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 backnotprop/plannotator --skill plannotator-annotate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install backnotprop/plannotator plannotator-annotate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/plannotator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/apps/skills/claude/plannotator-annotate .gemini/skills/plannotator-annotate && 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 "plannotator-annotate" agent skill from https://github.com/backnotprop/plannotator/tree/main/apps/skills/claude/plannotator-annotate into .gemini/skills/plannotator-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-annotate", 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 backnotprop/plannotator plannotator-annotateInstalls 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 backnotprop/plannotator --skill plannotator-annotate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/backnotprop/plannotator.git skills-src && mkdir -p .github/skills && cp -r skills-src/apps/skills/claude/plannotator-annotate .github/skills/plannotator-annotate && 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 "plannotator-annotate" agent skill from https://github.com/backnotprop/plannotator/tree/main/apps/skills/claude/plannotator-annotate into .github/skills/plannotator-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-annotate", 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 backnotprop/plannotator --skill plannotator-annotate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install backnotprop/plannotator plannotator-annotate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/backnotprop/plannotator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/apps/skills/claude/plannotator-annotate .opencode/skills/plannotator-annotate && 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 "plannotator-annotate" agent skill from https://github.com/backnotprop/plannotator/tree/main/apps/skills/claude/plannotator-annotate into .opencode/skills/plannotator-annotate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plannotator-annotate", 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
plannotator-annotate- GitHub stars
- 9.2k
- Token cost
- ~413 tokens
- SKILL.md length
- 216 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Opens Plannotator's annotation UI on a markdown file, HTML file, URL or folder, then reads the decision and feedback you send back and acts on it.
- Works in 4 steps: The exact text The user approved., an… → Empty, OR a JSON object with "decision":… → Plaintext annotation feedback, OR a JSON… → …
- Reviewing a markdown plan or document visually before the agent acts on it
- SKILL.md covers Markdown annotations and Your task
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill runs the plannotator annotate command on whatever file, URL or folder you name, which opens a visual annotation page. When you finish, the agent reads what came back and branches on four cases. An approval, with or without notes, means no new work starts, and any notes are kept as non-blocking guidance for later. A dismissed or empty result means the session was closed without changes, so the agent acknowledges it in one sentence and stops.
Plain-text feedback, or an annotated result with a feedback field, is treated as specific comments from you on the file, and the agent addresses them. If the arguments could not be resolved to a file, URL or folder, the agent works out the target from your description, runs the command again with a concrete path and handles that output the same way. The only tool it may call is the plannotator command line.
When your agent uses it
- Reviewing a markdown plan or document visually before the agent acts on it
- Annotating an HTML page, URL or whole folder and sending comments back to the agent
- Approving a plan with notes that should guide later work
Example prompts
- “Open plan.md in Plannotator so I can annotate it.”
- “Annotate the docs folder with Plannotator and address my comments.”
- “Annotate the design spec at docs/spec.html and fix whatever I flag.”
Requirements
- The plannotator command-line tool
- Pre-approved tools (allowed-tools): Bash(plannotator:*)
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- The exact text The user approved., an "Approved with Notes" message, OR a JSON object with "decision": "approved". The user approved the…
- Empty, OR a JSON object with "decision": "dismissed". The user closed the session without requesting changes. Acknowledge with a single…
- Plaintext annotation feedback, OR a JSON object with "decision": "annotated" and a "feedback" field. Address the feedback. The user has…
- A message that the arguments could not be resolved to a file, URL, or folder. The user described what to annotate in natural language…
What it can do on your machine
Read from SKILL.md and the folder at commit 1d9fe3f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(plannotator:*)
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
Plannotator Annotate loads about 413 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 216 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 backnotprop/plannotator at commit 1d9fe3f, republished under its Apache-2.0 licence (© backnotprop). 216 words, ~413 tokens.
Download SKILL.mdSave it as
.claude/skills/plannotator-annotate/SKILL.md (or your agent's skills folder).- name
- plannotator-annotate
- description
- Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.
- allowed-tools
- Bash(plannotator:*)
- disable-model-invocation
- true
Plannotator Annotate
Markdown annotations
!plannotator annotate $ARGUMENTS
Your task
The output above will be one of:
- The exact text
The user approved., an "Approved with Notes" message, OR a JSON object with"decision": "approved". The user approved the markdown file(s). If it is the Approved with Notes message, or that object also carries a"feedback"field, the user approved with notes: read them and carry them into subsequent work — they are non-blocking guidance, not a request to revise the file. Otherwise acknowledge with a single sentence ("Approved.") and stop. Either way, do not begin any work. - Empty, OR a JSON object with
"decision": "dismissed". The user closed the session without requesting changes. Acknowledge with a single sentence ("Annotation session closed.") and stop. Do not begin any work. - Plaintext annotation feedback, OR a JSON object with
"decision": "annotated"and a"feedback"field. Address the feedback. The user has reviewed the markdown file(s) and provided specific annotations and comments. - A message that the arguments could not be resolved to a file, URL, or folder. The user described what to annotate in natural language: work out which file, URL, or folder they mean, run
plannotator annotate <path-or-url>yourself with that concrete target (keeping any flags the message echoes), then handle its output per cases 1-3.
© backnotprop, Apache-2.0. 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 apps/skills/claude/plannotator-annotate of backnotprop/plannotator.
Open the folder on GitHubat commit 1d9fe3f
Compare with similar skills
Plannotator Annotate 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 |
|---|---|---|---|---|---|---|
| Plannotator Annotate this skillbacknotprop/plannotator | 9.2k | — | ~413 | Automated safety check: Pass | Apache-2.0 | |
| Planningchampionswimmer/pi-context-prune | 245 | — | ~779 | Automated safety check: Pass | None | |
| Grill With UIjasonku09/grill-with-ui | 246 | — | ~7.9k | Automated safety check: Pass | MIT | |
| Gstack Autoplan Review Pipelinegarrytan/gstack | 136k | — | ~16k | Automated safety check: Notes | MIT | |
| Plan and Implement Workflowmp-web3/claude-starter-kit | 109 | — | ~913 | Automated safety check: Notes | MIT | |
| Implement Incrementalrsmdt/the-startup | 536 | — | ~1.7k | Automated safety check: Pass | MIT |
Similar skills
Grill With UI
jasonku09/grill-with-ui
Moves a design-grilling interview from the terminal to a local web page, where each question, recommendation and discussion thread can be handled in any order.
Gstack Autoplan Review Pipeline
garrytan/gstack
Runs the gstack CEO, design, engineering and DX review skills on a plan file in sequence and makes borderline taste decisions automatically using six stated decision principles.
Plan and Implement Workflow
mp-web3/claude-starter-kit
Runs new features, scripts and structural changes through explore, design, approval, implementation and verification phases, with a tool search and an explicit plan sign-off.
Implement Incremental
rsmdt/the-startup
Linear phase-loop orchestrator for single-feature implementation plans.
Specify Incremental
rsmdt/the-startup
Decompose a single-feature specification into a linear, phase-by-phase implementation plan.
More from backnotprop/plannotator
All 13 skills in this repoPlannotator Visual Explainer
backnotprop/plannotator
Builds self-contained HTML explainers for plans, pull requests and technical concepts in Plannotator's theme, then opens them in its annotation view.
Plannotator Release Preparation
backnotprop/plannotator
Drafts Plannotator release notes with full contributor credit, bumps versions in dependency order, builds, and starts the tag-driven release pipeline, in four reviewed phases.
Plannotator Planning Analysis
backnotprop/plannotator
Mines a Plannotator archive of denied plans for feedback patterns and prompt improvements, then writes an HTML dashboard report, with a Claude Code fallback.
Renovate Actions PR Review
backnotprop/plannotator
Reviews Renovate pull requests that bump GitHub Actions by checking pinned SHAs against upstream tags, scanning changelogs and confirming workflows stay compatible.
Plannotator Goal Setup
backnotprop/plannotator
Guides the agent from a vague objective to a written goal package under goals/, using a confirmed restatement, a browser interview, a fact sheet and a codebase pass.
Dependency Update Audit
backnotprop/plannotator
Audits outdated npm and Bun packages for supply chain integrity before bumping them, deferring risky ones and logging every decision.
Related
Categories
Questions about Plannotator Annotate
What does Plannotator Annotate do?
Opens Plannotator's annotation UI on a markdown file, HTML file, URL or folder, then reads the decision and feedback you send back and acts on it. This skill runs the plannotator annotate command on whatever file, URL or folder you name, which opens a visual annotation page. When you finish, the agent reads what came back and branches on four cases.
When should I use Plannotator Annotate?
Plannotator Annotate fits situations like: reviewing a markdown plan or document visually before the agent acts on it; annotating an HTML page, URL or whole folder and sending comments back to the agent; approving a plan with notes that should guide later work.
How do I install Plannotator Annotate in Claude Code?
Run `npx skills add backnotprop/plannotator --skill plannotator-annotate -a claude-code`. Or copy the skill folder (apps/skills/claude/plannotator-annotate in backnotprop/plannotator) into .claude/skills/plannotator-annotate in your project. Claude Code loads it when a task matches its description.
How do I install Plannotator Annotate in Codex?
Run `npx skills add backnotprop/plannotator --skill plannotator-annotate -a codex`. Or copy the skill folder (apps/skills/claude/plannotator-annotate in backnotprop/plannotator) into .agents/skills/plannotator-annotate in your project. Codex loads it when a task matches its description.
Can I use Plannotator Annotate 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 backnotprop/plannotator --skill plannotator-annotate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plannotator-annotate, .gemini/skills/plannotator-annotate, .github/skills/plannotator-annotate and .opencode/skills/plannotator-annotate in your project.
What does Plannotator Annotate need to run?
SKILL.md names no scripts, command-line tools or credentials: Plannotator Annotate is instructions for the agent only. Our summary lists: The plannotator command-line tool. Its frontmatter pre-approves these tools: Bash(plannotator:*).
Does Plannotator Annotate 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 Plannotator Annotate 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 Plannotator Annotate use?
Plannotator Annotate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plannotator Annotate use?
About 413 tokens (SKILL.md is roughly 1.7k 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 Plannotator Annotate?
Skills that share tags, products or a category with Plannotator Annotate: Planning (championswimmer/pi-context-prune, 245 stars), Grill With UI (jasonku09/grill-with-ui, 246 stars), Gstack Autoplan Review Pipeline (garrytan/gstack, 136k stars) and Plan and Implement Workflow (mp-web3/claude-starter-kit, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plannotator Annotate?
backnotprop (a GitHub user) maintains it in backnotprop/plannotator, which has 9,185 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.
Source: backnotprop/plannotator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.