Open the latest rendered assistant response in Plannotator’s annotation interface. Incorporate returned feedback into a follow-up response or revision, and carry approval notes forward as guidance when the review includes them.
Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
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 the latest assistant response in Plannotator.
Do not send a commentary/status message before running the command. The command targets the latest rendered assistant response, so a preamble can mistakenly become the thing being annotated.
Run:
plannotator last
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.
Behavior:
"decision": "dismissed"), acknowledge it in one sentence and stop. Do not begin any work: closing the session is not approval."decision": "approved" result with a
"feedback" field. Read those notes and carry them into subsequent work, but
do not redo the message over them: they are guidance, not a change request.Run the command yourself rather than telling the user to invoke shell syntax manually.
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.
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.
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 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.
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.