Collect comments on a Markdown or HTML document, plain-text configuration file, URL, or folder through Plannotator’s annotation interface. Use the returned notes to revise the material; with gated review, a plan or specification can also receive an approval decision.
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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
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 --json
Run it with the shell tool's is_background: true, and no trailing &. The command waits until the person finishes in the browser, which often takes longer than the shell tool's foreground limit (2 minutes by default, 10 at most); a foreground run would be stopped and the annotations lost. Then end your turn without stopping the task. When the task finishes, read its output (the tool result names the output file) and act on it.
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:
"decision": "dismissed"), acknowledge it in one sentence and stop. Do not begin any work: closing the session is not approval.--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.Do not ask the user to paste a shell command into the chat. Run the command yourself.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use Plannotator to review plans, code changes, documents, and running local apps in a browser. This reference covers returning feedback to agents, browsing past decisions, sharing guided code reviews, and leaving questions for later replies.
Open files, folders, or URLs in Plannotator’s annotation interface, then have the agent address the returned comments. Use it to review Markdown, plain-text configuration files, or HTML through a shared feedback workflow.
Review Markdown files, HTML files, URLs, or folders in Plannotator’s annotation interface. The agent responds to requested changes and distinguishes them from approvals, optional approval notes, and sessions closed without feedback.
Analyze rejected plans and reviewer feedback to identify recurring concerns, changing expectations, and concrete prompt improvements. Produce an HTML dashboard from Plannotator archives, or use Claude Code plan rejection reasons when those archives are unavailable.
Open the Plannotator Inbox in a browser, starting it in the background if needed, and give the user its address. Useful when they have closed the tab or need to find the Inbox again.
Open the Plannotator Inbox in a browser, starting it in the background if needed, and give the user its address. Useful when they have closed the tab or need to find the Inbox again.