Command
Development
Command
/plannotator-annotate
Open interactive annotation UI for a markdown file
Install
> /plugin marketplace add backnotprop/plannotator > /plugin install plannotator@plannotator
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/plannotator-annotate
Context preview
What this command does when you run it.
Open interactive annotation UI for a markdown file
Command definition
plannotator-annotate.mddescription: Open interactive annotation UI for a markdown file
allowed-tools: shell(plannotator:*)
Markdown Annotations
!`plannotator annotate $ARGUMENTS`
Your task
The output above will be one of:
1. The exact text `The user approved.`, OR a JSON object with `"decision": "approved"`. The user approved the markdown file. If 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 file. Otherwise acknowledge with a single sentence ("Approved.") and stop. Either way, do not begin any work. 2. 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. 3. Plaintext annotation feedback, OR a JSON object with `"decision": "annotated"` and a `"feedback"` field. Address the feedback. The user has reviewed the markdown file and provided specific annotations and comments. 4. A message that the arguments could not be resolved to a file, URL, or folder. The user described what to annotate in natural language: work out which file, URL, or folder they mean, run `plannotator annotate <path-or-url>` yourself with that concrete target (keeping any flags the message echoes), then handle its output per cases 1-3.
Read more
description: Open interactive annotation UI for a markdown file allowed-tools: shell(plannotator:*)
Markdown Annotations
!`plannotator annotate $ARGUMENTS`
Your task
The output above will be one of:
1. The exact text `The user approved.`, OR a JSON object with `"decision": "approved"`. The user approved the markdown file. If 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 file. Otherwise acknowledge with a single sentence ("Approved.") and stop. Either way, do not begin any work. 2. 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. 3. Plaintext annotation feedback, OR a JSON object with `"decision": "annotated"` and a `"feedback"` field. Address the feedback. The user has reviewed the markdown file and provided specific annotations and comments. 4. A message that the arguments could not be resolved to a file, URL, or folder. The user described what to annotate in natural language: work out which file, URL, or folder they mean, run `plannotator annotate <path-or-url>` yourself with that concrete target (keeping any flags the message echoes), then handle its output per cases 1-3.
Ships withplannotator
Plannotator is a local, browser-based review surface for AI coding agents: Claude Code, Codex, Copilot CLI, Gemini CLI, OpenCode, Kiro, Droid, Amp, and Pi. It plugs directly into your agent through its hooks and commands.
Get the whole plugin
Stats
8,712
Stars
653
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
19h ago
Last commit
8mo ago
Created
Repo: backnotprop/plannotator
Other commands on plannotator.
Command
plannotator-review
Open interactive code review for current changes or a PR URL; --base <ref> / --diff-type <type> pin the session's opening diff (session-only, git-only)
@backnotpropView Command