Skip to main content

plannotator-annotate

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.

Source facts

Repository
backnotprop/plannotator
Last source activity
October 6, 2026 at 03:38
Detected SKILL.md language
English
Stars
9,342
Forks
701

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer
2 files

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
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: ```bash plannotator annotate <path-or-url> ``` Run when the user asks to review, approve, accept, or gate a generated plan/spec/document: ```bash plannotator annotate <path-or-url> --gate --json ``` Plain `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: 1. Launch the command with Bash. 2. Wait for the browser review to finish. 3. If annotations are returned, address them directly. 4. If the session closes without feedback, say so briefly and continue. 5. In a `--gate` session, 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. 6. 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.
View on GitHub