Open documents, text configuration files, HTML, URLs, or folders in Plannotator for browser review. The agent responds to returned annotations and can use an approval session when you need to accept a plan, specification, or document.
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.
Review 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
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:
--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 assistant’s latest rendered message in Plannotator and return specific annotations for revision. The skill distinguishes requested edits from approval, approval with notes, and a closed session, so each review result receives the appropriate response.
Review code changes in Plannotator’s browser interface and have the agent address returned comments. Choose the current working directory, another checkout, or a pull or merge request URL, with options to focus on a specific comparison base.