plannotator-compound

Analyze denied plan archives to extract feedback patterns and generate an HTML dashboard report.

9|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/Yassimba/loom --skill plannotator-compound-yassimba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plannotator-compound
Source: https://github.com/Yassimba/loom/tree/main/drafts/plannotator-compound
Command: npx skills add https://github.com/Yassimba/loom --skill plannotator-compound-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Repeated plan rejections contain valuable feedback, but that signal is buried across dozens or hundreds of archived files. This Skill reads every denied plan, clusters the reviewer's feedback into a taxonomy, and turns it into concrete prompt instructions that reduce future denials. ## Core Features & Use Cases - Map-reduce pattern analysis: Parallel extraction agents read every denied plan file, then reduction agents build a denial taxonomy, recurring phrase counts, and evolution-over-time analysis. - HTML dashboard report: Produces a self-contained, versioned report with narrative findings, KPIs, taxonomy bars, and a copyable corrective prompt derived from real denial data. - Dual data sources: Works with Plannotator plan archives first, falling back to Claude Code ExitPlanMode denial reasons extracted from JSONL transcripts via a bundled parser. - Use Case: After months of rejecting agent plans, run this Skill to discover that 25% of your denials are for missing narrative overviews, then install an improvement hook that injects corrective instructions into every future planning session. ## Quick Start Analyze my Plannotator plan archive and generate a compound planning report of my denial patterns.

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?

Point the Skill at your Plannotator data directory (PLANNOTATOR_DATA_DIR or ~/.plannotator) containing *-denied.md files. It inventories the archive, extracts feedback from every denied file in parallel, and produces an HTML report with a denial taxonomy and corrective prompt instructions.

Can I analyze Claude Code plan rejections without Plannotator?

Yes. If no Plannotator archive exists, the Skill falls back to scanning ~/.claude/projects/ JSONL transcripts using the bundled extract_exit_plan_mode_outcomes.py parser, which normalizes ExitPlanMode denial reasons into clean JSON for the same analysis pipeline.

Does the analysis support incremental reports?

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

What does the improvement hook do?

The optional improvement hook writes the corrective prompt instructions to hooks/compound/enterplanmode-improve-hook.txt in the Plannotator data directory. Plannotator's EnterPlanMode hook then injects those instructions into every future planning session automatically.

Why does the analysis read every denied file instead of sampling?

Sampling would distort taxonomy percentages and miss rare but recurring patterns. The Skill enforces full coverage by batching files across parallel extraction agents and verifying processed counts against the inventory before reduction begins.