plannotator-compound

Analyze Plannotator plan denial archives and generate an HTML dashboard of feedback patterns.

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill plannotator-compound-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plannotator-compound
Source: https://github.com/mmnavarr/harness/tree/main/skills/plannotator-compound
Command: npx skills add https://github.com/mmnavarr/harness --skill plannotator-compound-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? When AI coding agents repeatedly produce plans that get denied, the feedback history contains valuable patterns that are hard to see manually. This Skill reads your entire Plannotator plan archive (or Claude Code ExitPlanMode logs as a fallback), extracts every denial reason, and turns them into a taxonomy, recurring-phrase analysis, and concrete prompt instructions that prevent future denials. ## Core Features & Use Cases - Map-reduce denial analysis: Parallel extraction agents read every denied plan file, then reduction agents cluster feedback into a taxonomy with real counts, quotes, and evolution over time. - HTML dashboard report: Produces a self-contained, editorial-style HTML report with 7 sections covering denial taxonomy, expectation evolution, what works vs. what fails, recurring phrases, and a copyable corrective prompt. - Claude Code fallback: Includes a bundled Python parser that extracts ExitPlanMode denial reasons from ~/.claude/projects JSONL transcripts when no Plannotator archive exists. - Incremental reports and improvement hook: Detects previous reports to analyze only new files, and can write corrective instructions to a hook file injected into future planning sessions. - Use Case: After months of reviewing AI-generated plans, run this Skill to discover that 25% of your denials are for missing narrative overviews, then get a ready-to-paste prompt that fixes it. ## Quick Start Analyze my Plannotator plan archive and generate a compound planning report showing my denial patterns and corrective prompt instructions.

Frequently Asked Questions about plannotator-compound

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze denied plans from Plannotator?▼

Run the Skill with access to your Plannotator data directory ($PLANNOTATOR_DATA_DIR or ~/.plannotator). It inventories all *-denied.md files, extracts feedback with parallel agents, and produces an HTML report with a denial taxonomy and corrective prompt instructions.

Can I analyze Claude Code plan rejections without Plannotator?▼

Yes. The Skill includes a fallback mode that runs a bundled Python parser over ~/.claude/projects JSONL transcripts to extract ExitPlanMode denial reasons. The same taxonomy, reduction, and HTML report phases then run on that dataset.

What does the compound planning report contain?▼

The report is a single self-contained HTML file with seven sections: a narrative summary with KPIs, a ranked denial taxonomy, expectation evolution over time, what works versus what fails, top actionable improvements, your most-used feedback phrases, and a copyable corrective prompt.

Does the analysis support incremental updates?▼

Yes. The Skill detects previous compound-planning-report HTML files and offers incremental mode, which only analyzes denied plans dated after the last report's cutoff. New reports use versioned filenames like compound-planning-report-v2.html.

What are the limitations of the denial pattern analysis?▼

Accuracy depends on denied files containing reviewer feedback below the separator; bare denials yield thinner analysis. Datasets under 20 files produce preliminary findings, and in Claude Code fallback mode some denials have no recoverable human reason.