plannotator_skill

Overview

This skill provides an interactive visual UI to review and annotate AI agent plans and git diffs before or after code execution. Use it to approve, request changes, or send structured feedback back to the agent, and optionally auto-save approved plans to Obsidian or Bear Notes. It integrates with Claude Code and OpenCode and supports image annotation and team sharing links.

How this skill works

When an agent finishes planning or produces a diff, the UI displays the plan or unified/split diff for visual annotation. You mark steps or line ranges with structured intents (delete, insert, replace, comment), then submit a single outcome: approve or request changes. Annotations are sent back to the agent as structured feedback; approved plans can be auto-saved to note apps. The CLI includes scripts to install, configure hooks or plugins, run reviews, and set remote/devcontainer modes.

When to use it

• Review an agents implementation plan before it starts coding
• Annotate and give feedback on a generated git diff after coding
• Create a feedback loop to request concrete replanning from the agent
• Share a plan review with teammates via a link for collaborative sign-off
• Auto-save approved plans to Obsidian or Bear Notes for documentation
• Run reviews from remote environments (SSH, devcontainer, WSL) without opening a browser locally

Best practices

• Run plan review before implementation to catch design or safety issues early
• Keep each annotation targeted to one concrete, actionable change
• Include acceptance criteria when requesting changes so the agent can replan accurately
• Annotate exact line ranges in diffs and attach screenshots for UI/UX feedback
• Use the CLI status and hook checks to verify integration before relying on automatic triggers

Example use cases

• Trigger automatic plan review when exiting Claude Code plan mode to block risky implementations
• Launch a visual diff review for all uncommitted changes or a specific commit
• Configure remote mode for a headless server and forward the UI to your local browser
• Save approved implementation plans into an Obsidian vault for team documentation
• Use image annotation to mark UI issues in a feature branch before merge