meta-compound-analyze

Analyze PR retrospective compound learnings to generate a prioritized Markdown roadmap.

2|3|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/psd401/psd-claude-coding-system --skill meta-compound-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-compound-analyze
Source: https://github.com/psd401/psd-claude-coding-system/tree/main/plugins/psd-claude-coding-system/skills/meta-compound-analyze
Command: npx skills add https://github.com/psd401/psd-claude-coding-system --skill meta-compound-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing PR retrospectives and extracting actionable improvements is manual and error-prone. This Skill automates the discovery and prioritization of improvement opportunities from compound learnings.

Core Features & Use Cases

  • Theme aggregation: identifies frequent quality themes across PR retrospectives.
  • Suggestion clustering: groups recurring improvement ideas and surfaces high-impact gaps.
  • Quality-trend tracking: monitors review iterations, fix commits, and discussion activity over time.
  • Roadmap generation: outputs a prioritized improvement roadmap in Markdown (roadmap.md) for backlog planning.
  • Use Case: after merging multiple PRs, run this Skill to generate a focused backlog for team improvements.

Quick Start

/meta-compound-analyze --since 30d --min-confidence high --output roadmap.md

Frequently Asked Questions about meta-compound-analyze

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

FAQPage Schema
How do I generate a prioritized roadmap from PR retrospectives?

This Skill automates PR retrospective analysis by reading compound learnings from telemetry data, tracking quality trends like review iterations and fix commits, and producing a prioritized Markdown roadmap for backlog planning.

How do I track quality trends across merged pull requests?

Track quality trends across merged pull requests by analyzing telemetry data that records review iterations, fix commits, and discussion activity. The Skill aggregates this data to surface frequent quality themes and improvement opportunities over time.

Can I filter PR retrospective analysis by time window and confidence level?

You can filter PR retrospective analysis using the --since option to set a time window and --min-confidence to threshold the learnings. This ensures only relevant, high-quality improvement suggestions are clustered into the final roadmap.

What is the best way to aggregate recurring improvement ideas from pull request reviews?

Aggregating recurring improvement ideas is best handled by clustering compound learnings from PR retrospectives. This groups similar suggestions, surfaces high-impact gaps, and outputs a prioritized Markdown roadmap for team backlog planning.

Does PR retrospective analysis require specific telemetry data formats?

PR retrospective analysis requires compound learnings stored in meta/telemetry.json, typically generated by a clean-branch process after PR merges. This telemetry file provides the raw input for theme aggregation and quality trend tracking.