| name | plannotator |
| description | Routing-first visual approval gate for AI agent plans, markdown specs, and diffs. Use when a human needs to review a concrete plan before execution, inspect a targeted diff in a browser, mark up a spec/PRD/architecture note, or set up the review loop on Claude Code, Gemini CLI, Codex CLI, or OpenCode. Route planning/spec creation to `task-planning` or `ralph`, broad PR-policy review to `code-review`, rendered-UI critique to `agentation`, and fresh-session browser verification to `browser-harness`.
|
| allowed-tools | Read Bash Write |
| compatibility | Best for Claude Code, Gemini CLI, Codex CLI, OpenCode, and orchestration flows like JEO where an agent already produced a plan, spec artifact, or diff and a human wants a browser-based approval loop. Not for creating the plan itself, owning merge policy, or doing generic UI screenshot review.
|
| license | MIT |
| metadata | {"tags":"plan, plannotator, plan-review, diff-review, spec-review, markdown-review, claude-code, codex, gemini, opencode, annotation, visual-review, obsidian, bear-notes","platforms":"Claude, OpenCode, Codex, Gemini","keyword":"plan","version":"1.1.0","source":"backnotprop/plannotator","modernization":"2026-04-13T00:00:00.000Z","hardening":"2026-04-19T00:00:00.000Z"} |
plannotator
Use this skill when the job is to classify one review packet, open the smallest honest visual review path, and leave broad planning / PR policy / UI critique work outside the front door.
plannotator is not the planner.
It is the human approval gate that sits between:
- plan/spec creation (
task-planning, ralph)
- orchestration/runtime ownership (
jeo, task-planning, bmad)
- broader PR/code judgment (
code-review)
- rendered-UI bug markup (
agentation)
- clean browser verification (
browser-harness)
Read these support docs first:
When to use this skill
- A coding agent already produced an implementation plan and a human must approve or request changes before coding starts.
- A concrete git diff, commit range, or PR exists and the reviewer wants browser-based line-targeted feedback.
- A markdown artifact such as a spec, PRD, architecture note, or generated plan package needs visual review and revision feedback.
- The user needs to connect
plannotator to Claude Code, Gemini CLI, Codex CLI, or OpenCode and the main job is setup for the review loop.
- The review flow exists but remote mode, stable URLs/ports, or platform-specific behavior is flaky and needs targeted troubleshooting.
When not to use this skill
- The main job is writing or refining the plan/spec itself →
task-planning, ralph, or survey
- The main job is broad PR policy, merge criteria, risk judgment, or code-owner approval →
code-review
- The main job is exact rendered-UI critique that should drive frontend fixes →
agentation
- The main job is clean disposable browser automation or deterministic website verification →
browser-harness
- The main job is task orchestration, board state, or multi-agent routing → , ,
