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.
Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.
Review the instructions the agent will receive before you install.
!plannotator annotate $ARGUMENTS
The output above will be one of:
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."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."decision": "annotated" and a "feedback" field. Address the feedback. The user has reviewed the markdown file(s) and provided specific annotations and comments.plannotator annotate <path-or-url> yourself with that concrete target (keeping any flags the message echoes), then handle its output per cases 1-3.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.
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.
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.
Open Plannotator’s browser-based code review interface from Kiro and address the returned feedback. Review the current directory, another working directory, or a pull request URL, and optionally choose a comparison base to focus the changes shown.