Show Me Your Work Decision Log
cursor/plugins
Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.
Opens Plannotator's browser annotation view for a markdown, config, HTML, URL or folder target and acts on the feedback you leave, with an optional approval gate.
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/core/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/core/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/core/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/core/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/core/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/core/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/core/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/core/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/core/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/core/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/core/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/core/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/core/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/core/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
- ~427 tokens
- SKILL.md length
- 214 words
- Files
- 2
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Opens Plannotator's browser annotation view for a markdown, config, HTML, URL or folder target and acts on the feedback you leave, with an optional approval gate.
- Works in 6 steps: Launch the command with Bash. → Wait for the browser review to finish. → If annotations are returned, address… → …
- Annotating a plan, spec or README visually rather than in chat
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Gating a generated plan on your approval before work continues
What it does
Instead of reviewing a document inline in chat, you annotate it in Plannotator and the agent responds to what comes back. The agent runs the plannotator annotate command itself with a file path, URL or folder, waits for the browser review to finish, and then addresses any returned annotations directly. The target can be a markdown file, a plain-text config file such as YAML, JSON, TOML, INI, CSV or a log, an HTML file, a URL or a folder.
For reviewing, approving or gating a generated plan or spec, the command is run with the --gate and --json flags. Plain annotate has no Approve button and supports only feedback or closing the session, and --json alone does not enable approval, so the agent never promises an approval action unless the gate flag is present.
If a session closes without feedback, the agent says so briefly and continues. An approval can still carry notes, which are read as guidance for later work and not as a request to revise the document. When the command cannot resolve its arguments to a file, URL or folder, the agent works out the intended target and re-runs it, and never asks you to paste a shell command.
When your agent uses it
- Annotating a plan, spec or README visually rather than in chat
- Gating a generated plan on your approval before work continues
- Reviewing a config file or a folder of notes with inline comments
Example prompts
- “Open docs/architecture.md in Plannotator so I can annotate it.”
- “Gate the implementation plan in PLAN.md behind my approval.”
- “Annotate the staging config.yaml and then apply my comments.”
Requirements
- The plannotator command line tool
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Launch the command with Bash.
- Wait for the browser review to finish.
- If annotations are returned, address them directly.
- If the session closes without feedback, say so briefly and continue.
- In a --gate session, an approval may still carry notes — a "decision": "approved" result with a
- If the command reports that the arguments could not be resolved to a file,
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 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 (its code samples are bash).
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 427 tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 214 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). 214 words, ~427 tokens.
Download SKILL.mdSave it as
.claude/skills/plannotator-annotate/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- plannotator-annotate
- description
- Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml, .json, .toml, .ini, .csv, .log, …), HTML file, URL, or folder and then respond to the returned annotations.
- disable-model-invocation
- true
Plannotator Annotate
Use this skill when the user wants to annotate a document in Plannotator instead of reviewing it inline in chat.
Run for ordinary annotation/feedback:
plannotator annotate <path-or-url>Run when the user asks to review, approve, accept, or gate a generated plan/spec/document:
plannotator annotate <path-or-url> --gate --jsonPlain annotate has no Approve button; it only supports feedback or closing the session. Never promise an approval action unless --gate is present. --json only changes the output format and does not enable approval by itself.
Behavior:
- Launch the command with Bash.
- Wait for the browser review to finish.
- If annotations are returned, address them directly.
- If the session closes without feedback, say so briefly and continue.
- In a
--gatesession, an approval may still carry notes — a"decision": "approved"result with a"feedback"field (without--json, an "Approved with Notes" message). Read those notes and carry them into subsequent work, but do not revise the document over them: they are guidance, not a change request. - If the command reports that the arguments could not be resolved to a file, URL, or folder, work out which target the user means and re-run the command yourself with that concrete path or URL.
Do not ask the user to paste a shell command into the chat. Run the command yourself.
© 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
SKILL.md and 1 other file in apps/skills/core/plannotator-annotate of backnotprop/plannotator.
- SKILL.md
- agents/openai.yaml
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 | — | ~427 | Automated safety check: Pass | Apache-2.0 | |
| Show Me Your Work Decision Logcursor/plugins | 10k | 9 repos | ~1.6k | Automated safety check: Pass | None | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Loop Constraints Enforcercobusgreyling/loop-engineering | 11k | 1 repos | ~475 | Automated safety check: Notes | MIT | |
| Ask User QuestionMemTensor/MemOS | 12k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| PUA High-Agency Governancetanweai/pua | 20k | — | ~502 | Automated safety check: Pass | MIT |
Similar skills
- Official
Darwin Skill Optimizer
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
Loop Constraints Enforcer
cobusgreyling/loop-engineering
Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.
Ask User Question
MemTensor/MemOS
Shows a question as a modal in the interface to clarify a task, collect a preference or get approval, since the user cannot see terminal output.
PUA High-Agency Governance
tanweai/pua
Pushes an agent to keep verifying and changing approach after repeated failures, using a diagnosis line, evidence-based completion and confirmation before risky edits.
Agentmemory Forget
rohitg00/agentmemory
Deletes chosen memories from agentmemory only after showing the matches and getting an explicit yes, for privacy requests and cleanup of outdated notes.
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 browser annotation view for a markdown, config, HTML, URL or folder target and acts on the feedback you leave, with an optional approval gate. Instead of reviewing a document inline in chat, you annotate it in Plannotator and the agent responds to what comes back. The agent runs the plannotator annotate command itself with a file path, URL or folder, waits for the browser review to finish, and then addresses any returned annotations directly.
When should I use Plannotator Annotate?
Plannotator Annotate fits situations like: annotating a plan, spec or README visually rather than in chat; gating a generated plan on your approval before work continues; reviewing a config file or a folder of notes with inline comments.
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/core/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/core/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.
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 427 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: Show Me Your Work Decision Log (cursor/plugins, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars), Loop Constraints Enforcer (cobusgreyling/loop-engineering, 11k stars) and Ask User Question (MemTensor/MemOS, 12k 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.