Install and Manage Plannotator Skills

The standard Plannotator installer already installs three core skills: plannotator-review, plannotator-annotate, and plannotator-last. Run a separate npx skills command only when you want the extra skills or an explicit subset of them.

Core and extra skills

Skill	Set	Installed by the standard installer	Purpose
`plannotator-review`	Core	Yes	Open code review for local changes or a pull request.
`plannotator-annotate`	Core	Yes	Annotate a file, folder, or web URL.
`plannotator-last`	Core	Yes	Annotate the latest assistant message.
`plannotator-compound`	Extra	No	Analyze denied plans and produce a compound-planning report.
`plannotator-setup-goal`	Extra	No, except for Kiro CLI	Set up the files used by a goal workflow.
`plannotator-visual-explainer`	Extra	No, except for Kiro CLI	Create a visual HTML explanation for a plan, change, or pull request.

The full installer places the core skills in Claude Code’s skill directory and the shared Agent Skills directory used by Codex. Kiro CLI is the exception to the normal extra-skill rule: when Kiro is detected, the installer adds its Kiro-specific review and annotation skills plus plannotator-setup-goal and plannotator-visual-explainer. A minimal installation skips every skill, command file, hook, agent integration setup, and optional runtime.

Install the core skills

Use the standard installer. It installs the binary and the host-specific skill bodies together, then replaces those managed copies when you run it again. If you previously used a minimal installation, rerun the installer without --minimal. You do not need to remove the existing binary first. The installer manages all three core skills together. It does not provide a flag for installing only one core skill.

Install all extra skills

The guided installer can launch the Agent Skills CLI for you. You can also run it directly:

npx skills add backnotprop/plannotator/apps/skills/extra --global

The interactive flow lets you choose which supported agents receive the skills.

Install a specific set

Repeat --skill to select only the extras you want:

npx skills add backnotprop/plannotator/apps/skills/extra \
  --global \
  --skill plannotator-compound \
  --skill plannotator-visual-explainer

Add one or more --agent values for a repeatable host-specific install:

npx skills add backnotprop/plannotator/apps/skills/extra \
  --global \
  --skill plannotator-compound \
  --agent claude-code \
  --yes

Omit --agent and --yes when you want the interactive host selector. The Agent Skills CLI README documents its current --skill, --agent, --global, and --yes options.

Choose whether the model can start a skill

Plannotator’s Claude Code and shared Agent Skill copies are user-started by default. During a guided install, you can choose which of those installed skills the model may start without an explicit skill command. Run the guided questions again:

macOS, Linux, or WSL
Windows PowerShell
Windows Command Prompt

curl -fsSL https://plannotator.ai/install.sh | bash -s -- --reconfigure

& ([scriptblock]::Create((irm https://plannotator.ai/install.ps1))) -Reconfigure

curl -fsSL https://plannotator.ai/install.cmd -o install.cmd
install.cmd --reconfigure
del install.cmd

For an automated install, pass a comma-separated list:

curl -fsSL https://plannotator.ai/install.sh | bash -s -- \
  --non-interactive \
  --model-invocable plannotator-review,plannotator-compound

--model-invocable changes how an installed Claude Code or shared Agent Skill may be started. It does not install a missing extra skill. Use --model-invocable none to keep those managed copies user-started.

Understand host-specific files

The same /plannotator-* command name can refer to different host features. Check the host before editing or removing files.

Host	What provides the command	Location or package
Claude Code	Claude-specific agent skills that also appear as slash commands	`~/.claude/skills/plannotator-`, or `$CLAUDE_CONFIG_DIR/skills/plannotator-` when set
Codex	Shared Agent Skills, started with `$plannotator-*`	`~/.agents/skills/plannotator-*`
Kiro CLI	Kiro-specific skills and an example custom agent	`~/.kiro/skills/plannotator-*` and `~/.kiro/agents/plannotator.json`
OpenCode	Native Markdown command files plus the separately configured OpenCode plugin	On macOS, Linux, and WSL: `${XDG_CONFIG_HOME:-$HOME/.config}/opencode/commands`. On Windows PowerShell and Command Prompt: `%USERPROFILE%\.config\opencode\commands`. The plugin is `@plannotator/opencode`.
Gemini CLI	Native TOML command files plus a policy and hook	`~/.gemini/commands`, `~/.gemini/policies`, and `~/.gemini/settings.json`
Claude Code, Copilot CLI, and Droid	Host marketplace plugins can add hooks or commands	Managed by that host’s plugin system
Pi	Commands and plan mode come from the Pi extension	`@plannotator/pi-extension`
Amp	Command-palette actions come from an Amp plugin file	`~/.config/amp/plugins/plannotator.ts` or `.amp/plugins/plannotator.ts`

Claude Code’s skill-backed slash commands and Codex’s shared skills call the installed plannotator binary. OpenCode and Gemini use native command files. Copilot CLI, Droid, Pi, and Amp get their commands from plugins or extensions. Installing an agent skill does not install or update those separate host packages.

Distinguish skills from Plannotator packages

Item	What it is	How users install it
`plannotator`	The local executable that starts the review server and browser UI	The Plannotator installer
Agent skill	A `SKILL.md` instruction package that tells an agent how to run a Plannotator workflow	The Plannotator installer or `npx skills add`
Slash command	A host-visible command. In Claude Code it can be backed by a skill; in other hosts it can be a native command file or plugin command	The installer, a plugin, or an extension
Plugin or extension	Host integration code for hooks, tools, plan mode, or command registration	The host’s plugin or package manager
`@plannotator/ui`	React components, hooks, and styles for embedding Plannotator’s document UI in another application	`npm install @plannotator/ui @plannotator/core`
`@plannotator/core`	Browser-safe types and utilities used by `@plannotator/ui`	Installed as an npm library, normally with `@plannotator/ui`

Normal Plannotator users do not need @plannotator/ui or @plannotator/core. Those reusable npm packages are for application developers. They do not install the plannotator command, agent skills, or host plugins. The standard installer downloads the plannotator executable from GitHub Releases. It does not install either reusable npm package. Update @plannotator/ui and @plannotator/core through the package manager for the application that embeds them.

Update skills

Rerun the standard Plannotator installer to replace its managed core skills with the copies from the selected Plannotator release. This also refreshes the binary and other installer-managed files. Update extra skills installed through the Agent Skills CLI:

npx skills update plannotator-compound plannotator-setup-goal \
  plannotator-visual-explainer --global

You can name one skill instead. Updating an extra skill does not update the Plannotator binary or a host plugin.

Remove skills

If you enabled extras through the guided installer, first save no extras as the installer preference. Otherwise a later installer run can offer to add them again:

macOS, Linux, or WSL
Windows PowerShell
Windows Command Prompt

curl -fsSL https://plannotator.ai/install.sh | bash -s -- --no-extras

& ([scriptblock]::Create((irm https://plannotator.ai/install.ps1))) -NoExtras

curl -fsSL https://plannotator.ai/install.cmd -o install.cmd
install.cmd --no-extras
del install.cmd

Then remove extras installed through the Agent Skills CLI:

npx skills remove --global \
  plannotator-compound \
  plannotator-setup-goal \
  plannotator-visual-explainer

To remove installer-managed core skills manually, delete only these directories:

Copy	macOS, Linux, or WSL	Windows PowerShell or Command Prompt
Claude Code	`plannotator-review`, `plannotator-annotate`, and `plannotator-last` under `$CLAUDE_CONFIG_DIR/skills` when that variable is set, or under `~/.claude/skills` otherwise	The same three directories under `%CLAUDE_CONFIG_DIR%\skills` when that variable is set, or under `%USERPROFILE%\.claude\skills` otherwise
Shared Agent Skills for Codex and compatible hosts	The same three directories under `~/.agents/skills`	The same three directories under `%USERPROFILE%\.agents\skills`

A later full installer run restores all three managed core skills. For Kiro CLI, remove only the Plannotator skill directories under ~/.kiro/skills. Remove ~/.kiro/agents/plannotator.json separately if you no longer want the example agent. Removing a skill does not remove the Plannotator binary, a host plugin, or saved Plannotator data. See Installation to remove the executable or local data. Last verified against Plannotator OSS v0.25.1 on July 31, 2026. Maintained by the Plannotator project.

Start

Plans and documents

Code review

Reference

Agents

Editors and notes

Troubleshooting

Related project

Install and Manage Plannotator Skills

Core and extra skills

Install the core skills

Install all extra skills

Install a specific set

Choose whether the model can start a skill

Understand host-specific files

Distinguish skills from Plannotator packages

Update skills

Remove skills

​Core and extra skills

​Install the core skills

​Install all extra skills

​Install a specific set

​Choose whether the model can start a skill

​Understand host-specific files

​Distinguish skills from Plannotator packages

​Update skills

​Remove skills

Core and extra skills

Install the core skills

Install all extra skills

Install a specific set

Choose whether the model can start a skill

Understand host-specific files

Distinguish skills from Plannotator packages

Update skills

Remove skills