# Plannotator Annotate

Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml...

- Repository: https://github.com/backnotprop/plannotator (9810 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add backnotprop/plannotator --skill plannotator-annotate -g -a claude-code -y`
Codex: `npx skills add backnotprop/plannotator --skill plannotator-annotate -g -a codex -y`
Cursor: `npx skills add backnotprop/plannotator --skill plannotator-annotate -g -a cursor -y`
Gemini CLI: `npx skills add backnotprop/plannotator --skill plannotator-annotate -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add backnotprop/plannotator`

## Description

Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml, .json, .toml, .ini, .csv, .log, …), HTML file, URL, or folder and then respond to the returned annotations.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Plannotator Annotate (Qwen Code)

Use this skill when the user wants to annotate a document in Plannotator instead of reviewing it inline in chat.

Run for ordinary annotation/feedback:

```bash
plannotator annotate <path-or-url>
```

Run when the user asks to review, approve, accept, or gate a generated plan/spec/document:

```bash
plannotator annotate <path-or-url> --gate --json
```

Run it with the shell tool's `is_background: true`, and no trailing `&`. The command waits until the person finishes in the browser, which often takes longer than the shell tool's foreground limit (2 minutes by default, 10 at most); a foreground run would be stopped and the annotations lost. Then end your turn without stopping the task. When the task finishes, read its output (the tool result names the output file) and act on it.

Plain `annotate` has no **Approve** button; it only supports feedback or closing the session. Never promise an approval action unless `--gate` is present. `--json` only changes the output format and does not enable approval by itself.

Behavior:

1. If annotations are returned, address them directly.
2. If the session closes without feedback (the output is empty, or a JSON object with `"decision": "dismissed"`), acknowledge it in one sentence and stop. Do not begin any work: closing the session is not approval.
3. In a `--gate` session, an approval may still carry notes, a `"decision": "approved"` result with a
   `"feedback"` field (without `--json`, an "Approved with Notes" message). Read those notes and carry them into subsequent work, but
   do not revise the document over them: they are guidance, not a change request.
4. If the command reports that the arguments could not be resolved to a file,
   URL, or folder, work out which target the user means and re-run the command
   yourself with that concrete path or URL.

Do not ask the user to paste a shell command into the chat. Run the command yourself.