# Plannotator Compound

Analyze a user's Plannotator plan archive to extract denial patterns, feedback...

- Repository: https://github.com/backnotprop/plannotator (9810 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: yes, review before use

## Install

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

## Description

Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements, then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.

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

# Compound Planning Analysis

You are conducting a comprehensive research analysis of a user's Plannotator plan
archive. The goal: extract patterns from their denied plans, reduce
them into actionable insights, and produce an elegant HTML dashboard report.

This is a multi-phase process. Each phase must complete fully before the next begins.
Research integrity is paramount, every file must be read, no skipping.

## Source Selection

Before starting the analysis, determine which data source is available.

1. **Plannotator mode (first-class)**, Find the Plannotator data directory,
   called `<data-dir>` from here on. Run:

   ```
   plannotator data-dir
   ```

   It prints the folder's absolute path and creates nothing; use what it
   prints. If it prints nothing or fails (an older Plannotator), use `$PLANNOTATOR_DATA_DIR` if
   set, else whichever of `$XDG_DATA_HOME/plannotator` and the home folder's
   `.plannotator` holds `history/` or `sessions/` (the home one if both do),
   and ask the user if neither does.

   Never write into any other folder than `<data-dir>`. In particular, do not
   create a `.plannotator` folder in the home folder unless `<data-dir>` is
   that folder: on an install that keeps its data under `$XDG_DATA_HOME`, a
   new one can make Plannotator lose sight of the person's plans and history.
   Leave any other Plannotator folder you find alone, and do not suggest
   deleting it: it may hold older data.

   Check the `plans/` subdirectory of `<data-dir>`. If it exists and contains
   `*-denied.md` files, use this mode. The entire workflow below is written for
   Plannotator data.

The rest: https://github.com/backnotprop/plannotator/blob/HEAD/apps/skills/extra/plannotator-compound/SKILL.md