plannotator-last

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

Get it through your agent npx skills add backnotprop/plannotator@plannotator-last

Skill instructions

Rendered from the published SKILL.md, 14 lines.

!plannotator annotate-last $ARGUMENTS

The output above will be one of:

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.
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.
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.

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "plannotator-last"
  }
}

From backnotprop/plannotator via skills.sh

plannotator-annotate
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.
1,030 installs
plannotator-review
Open Plannotator's browser-based code review UI for the current worktree, another directory, or a pull request URL, then act on the feedback that comes back.
1,039 installs
plan-canvas
Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.
5,068 installs
bro
Restate the last message in plain human language, with no jargon.
9,834 installs
bro
Restate the last message in plain human language, with no jargon.
8,509 installs

plannotator-visual-explainer
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to nicobailon/visual-explainer.
13,924 installs
plannotator-compound
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.
12,806 installs
plannotator-setup-goal
Turn an idea or objective into a goal package for /goal. Interviews the user, builds a reviewed fact sheet via Plannotator, then explores the codebase to produce an execution plan.
12,569 installs
plannotator-review
Open Plannotator's browser-based code review UI for the current worktree, another directory, or a pull request URL, then act on the feedback that comes back.
1,039 installs
plannotator-annotate
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.
1,030 installs

Content is provided as published by its creators; you are responsible for how you use it.

To request removal, use the contact form.