prism-retro

Compare plan intent with execution using merge commits, PR reviews, and CI statuses.

Updated May 2, 2026

Search Tags:#feedback #software development #retrospective #plan analysis #performance assessment

Ready to run

npx skills add https://github.com/HunterMcGrew/PRISM --skill prism-retro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prism-retro
Source: https://github.com/HunterMcGrew/PRISM/tree/main/.cursor/skills/prism-retro
Command: npx skills add https://github.com/HunterMcGrew/PRISM --skill prism-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps analyze the effectiveness of software development plans by comparing intent with execution, enabling teams to learn and improve.

Core Features & Use Cases

Retro Analysis: Compares the planned objectives with the actual outcomes in a development plan.
Multi-voice Synthesis: Uses contributions from team members based on their work on the plan.
Actionable Insights: Provides action items based on the analysis, guiding future development practices.
Use Case: A development team can use this Skill after closing a plan to understand what went well and what didn't, based on actual PR activity and codebase changes.

Quick Start

Invoke the 'prism-retro' command to generate a retro report for your current development plan.

Frequently Asked Questions about prism-retro

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

FAQPage Schema

How do I run a software development retrospective comparing planned objectives with actual execution?▼

A software development retrospective compares plan intent with execution by analyzing merge commits, PR review threads, and CI statuses against the original plan. This process identifies gaps between objectives and actual outcomes to guide future improvements.

Can I generate a retrospective report for an individual ticket or a specific date range?▼

Yes, retrospective analysis supports individual tickets, specific date ranges, and entire epics. You can generate targeted retro reports by invoking the analysis command to evaluate CI statuses and PR activity against the plan for those specific scopes.

What data do I need to perform plan analysis and assess development performance?▼

Plan analysis requires your development plan data structures alongside accessible merge commits, PR review threads, and CI statuses. This data allows the assessment to compare intended objectives with actual codebase changes and team contributions.

How does multi-voice synthesis work when analyzing a development plan retro?▼

Multi-voice synthesis aggregates feedback and contributions from individual team members based on their actual work on the plan. It correlates this input with PR activity and codebase changes to provide a comprehensive view of plan effectiveness.

What is the best way to get actionable insights from a closed development plan?▼

The best way to get actionable insights is to compare planned objectives with actual outcomes after closing a plan. Analyzing actual PR activity and codebase changes against the original intent generates specific action items to guide future development practices.

Do I need a specific directory structure to analyze PR review threads and CI statuses?▼

Yes, retrospective analysis requires the .ai-skills/skills/prism-retro directory and its associated data structures to be present. This setup ensures the tool can properly access and evaluate your plan against merge commits and CI statuses.