plannotator-compound

# 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)** — Determine the Plannotator data directory: use `$PLANNOTATOR_DATA_DIR` if set, otherwise `~/.plannotator`. Check the `plans/` subdirectory there. If it exists and contains `*-denied.md` files, use this mode. The entire workflow below is written for Plannotator data. 2. **Claude Code fallback mode** — If the Plannotator archive is absent or contains no denied plans, check `~/.claude/projects/`. If present, read [references/claude-code-fallback.md](references/claude-code-fallback.md) before continuing. That reference explains how to use the bundled parser at [scripts/extract_exit_plan_mode_outcomes.py](scripts/extract_exit_plan_mode_outcomes.py) to extract denial reasons from Claude Code JSONL transcripts. Every phase below has a short note explaining what changes in fallback mode — the reference file has the details. 3. **Neither available** — Ask the user for their Plannotator plans directory or Claude...