Skip to content
cccskills
FreePublished on GitHub

plannotator-last

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.

OriginalShow the original description

Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.

See how to install

Good for

  • Annotate the assistant’s latest response for revision
  • Approve a response without requesting further work
  • Approve with notes to guide subsequent work
  • Close a review without requesting changes

Files included (1)

  • SKILL.md1.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Plannotator Last

Message annotations

!plannotator annotate-last $ARGUMENTS

Your task

The output above will be one of:

  1. The exact text The user approved., an "Approved with Notes" message, OR a JSON object with "decision": "approved". The user approved your last message. 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 message. Otherwise acknowledge with a single sentence ("Approved.") and stop. Either way, do not begin any work.
  2. Empty, OR a JSON object with "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.
  3. Plaintext annotation feedback, OR a JSON object with "decision": "annotated" and a "feedback" field. Address the feedback. The user has reviewed your last message and provided specific annotations and comments.

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

plannotator

FreeSummary

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.

  • Reviewing and approving plans or specifications
  • Reviewing local code changes or pull requests
  • Annotating documents or running local apps
backnotprop/plannotator9.5KUpdated Oct 18, 2026

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.

  • Reviewing a Markdown document
  • Collecting comments on HTML or web pages
  • Opening a folder for annotation
backnotprop/plannotator9.5KUpdated Oct 18, 2026

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.

  • Adding document feedback in a browser
  • Reviewing text configuration files or HTML
  • Approving a generated plan or specification
backnotprop/plannotator9.5KUpdated Oct 18, 2026

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.

  • Reviewing a Markdown document
  • Commenting on configuration files
  • Opening a folder for annotation
backnotprop/plannotator9.5KUpdated Oct 18, 2026

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.

  • Finding recurring reasons for plan rejection
  • Understanding how review expectations changed
  • Deriving planning instructions from past feedback
backnotprop/plannotator9.5KUpdated Oct 18, 2026

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.

  • Review code changes from Kiro
  • Review a separate working directory
  • Open a review for a pull request URL
backnotprop/plannotator9.5KUpdated Oct 18, 2026

See all skills by backnotprop

Report a problem with this skill