planview
SKILL.md
planview - Visual Plan Review with Plannotator
Use this skill when the user asks to review a coding plan visually, annotate a diff with feedback, or run an approval loop before implementation.
When to use this skill
- The user wants to review or refine an AI-generated implementation plan before coding starts
- The user asks for visual annotation of plans or diffs
- The user asks for a feedback loop: approve or request changes from the agent
- The user is using Claude Code or OpenCode and needs plannotator-based workflow guidance
Step 1: Install Plannotator CLI
Install the plannotator command first:
# macOS / Linux / WSL
curl -fsSL https://plannotator.ai/install.sh | bash
# Windows PowerShell
irm https://plannotator.ai/install.ps1 | iex
Step 2: Connect to Your Agent CLI
Claude Code
/plugin marketplace add backnotprop/plannotator
/plugin install plannotator@plannotator
Restart Claude Code after plugin installation so hooks are applied.
OpenCode
Add plugin:
{
"plugin": ["@plannotator/opencode@latest"]
}
Install command:
curl -fsSL https://plannotator.ai/install.sh | bash
Restart OpenCode after installation.
Step 3: Run the Plan/Diff Review Loop
- Ask your coding agent to produce a plan or create code changes.
- Open plannotator review flow (
/plannotator-reviewfor diff review, or hook-based plan review). - Annotate with clear intent:
delete: remove risky or unnecessary stepinsert: add missing stepreplace: revise incorrect approachcomment: clarify constraints or acceptance criteria
- Submit one of two outcomes:
- Approve: implementation proceeds
- Request changes: structured feedback returns to the agent for replanning
Step 4: Remote/Devcontainer Configuration (Optional)
For remote sessions, set fixed port and remote mode:
export PLANNOTATOR_REMOTE=1
export PLANNOTATOR_PORT=9999
Useful environment variables:
PLANNOTATOR_REMOTE: remote mode (no auto browser open)PLANNOTATOR_PORT: fixed local/forwarded portPLANNOTATOR_BROWSER: custom browser path/appPLANNOTATOR_SHARE_URL: custom share portal URL
Best practices
- Require explicit acceptance criteria in annotations (test/build/lint conditions).
- Prefer small, actionable comments over broad rewrites.
- For diff review, annotate exact line ranges tied to expected behavior changes.
- Keep one decision per annotation to reduce ambiguity for the agent.
Weekly Installs
1
Repository
supercent-io/sk…templateGitHub Stars
88
First Seen
Feb 20, 2026
Security Audits
Installed on
opencode1
gemini-cli1