Diagnose implementation plan estimate variance and generate evidence-based retrospectives.
npx skills add https://github.com/miethe/boxbrain-2 --skill plan-review-miethe
Please help me install this Agent Skill. Skill: plan-review Source: https://github.com/miethe/boxbrain-2/tree/main/.claude/skills/plan-review Command: npx skills add https://github.com/miethe/boxbrain-2 --skill plan-review-miethe
This Skill reveals why completed implementation plans over- or under-ran their estimates, separating estimation failures from scope changes, blockers, discovery work, and worthwhile quality investments.
Use the plan-review skill to create a retrospective for the completed implementation plan at the specified path or feature slug.
High-intent search queries and answers about installing and using this skill.
To run a retrospective on completed implementation plans, analyze plan metadata, git history, progress files, and optional CCDash reports. This process diagnoses feature effort and estimation variance by comparing estimated story points against actual implementation complexity.
Heuristic attribution maps estimation variance to specific planning heuristics like noun counting, dual-implementation overhead, algorithmic complexity, bundled estimates, anchors, and plumbing effort, separating genuine estimation failures from scope changes and blockers.
Feature implementations over-run estimates due to estimation failures, scope changes, blockers, discovery work, or quality investments. Analyzing git history and plan metadata reveals whether repository duplication, service complexity, or infrastructure plumbing caused the divergence.
Yes, you can use git history and progress files to generate evidence-based retrospectives. By performing phase-level variance analysis and scope classification, the retrospective produces anchor updates, heuristic tuning suggestions, and candidate memories.
You do not need CCDash reports to perform a plan review; they are optional. The analysis can diagnose estimation variance using plan metadata, git history, and progress files, while integrating CCDash reports adds optional provenance to the retrospective.
dobrinz123Generate consolidated project statistics from phases, plans, requirements, and git history.
adolfoaranaes12Estimate story points using a Complexity × Effort + Risk formula.
bitwardenGenerate structured retrospective reports from Claude Code session data.
packetalienAnalyze sprint and milestone data to generate a structured Markdown retrospective.
