// Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.
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.
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.
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.
Open Plannotator's annotation UI for a markdown file, converted HTML file, URL, or folder and then respond to the returned annotations.
Open Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.
Audit and update npm/Bun dependencies with supply chain integrity checks — verifies maintainers, publish age, tarball diffs, and provenance before bumping. Defers risky packages to ~/.supply-chain/notes/.
| name | plannotator-last |
| description | Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue. |
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
Behavior:
Run the command yourself rather than telling the user to invoke shell syntax manually.