compound

Analyze retro log files to identify recurring development frictions across work packages.

Updated Jun 12, 2026

Search Tags:#automation #workflow #optimization #analysis #process #retro

Ready to run

npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill compound-ambrovia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: compound
Source: https://github.com/ambrovia/agent-skills-pipeline/tree/main/skills/compound
Command: npx skills add https://github.com/ambrovia/agent-skills-pipeline --skill compound-ambrovia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the issue of recurring development friction by identifying systemic patterns in retro logs that would otherwise be ignored as isolated incidents.

Core Features & Use Cases

Pattern Mining: Automatically aggregates retro observations across multiple work packages to identify systemic issues.
Process Optimization: Proposes surgical changes to skill files or process documentation based on confirmed recurring patterns.
Use Case: If an agent repeatedly notes that a specific API integration is flaky across three different work packages, this skill surfaces that pattern and proposes a fix to the relevant documentation or skill file.

Quick Start

Run the compound skill to analyze all retro logs and propose process improvements based on recurring patterns.

Frequently Asked Questions about compound

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

FAQPage Schema

How do I identify systemic patterns from recurring development friction in retro logs?▼

To identify systemic patterns from recurring development friction in retro logs, you need pattern mining that aggregates observations across multiple work packages. This process detects issues exceeding a three-occurrence threshold, classifying isolated incidents into actionable process improvements.

What is the best way to automate process optimization from retrospective meeting notes?▼

Automating process optimization from retrospective notes involves analyzing retro log files to detect recurring frictions. Once a pattern is confirmed across sessions, the system proposes surgical modifications to skill files and process documentation for coordinator approval.

How many work package sessions are needed to detect a systemic development issue?▼

Detecting a systemic development issue requires a minimum of three occurrences across multiple work package sessions. This three-occurrence threshold ensures that isolated incidents are ignored while genuine recurring frictions are classified for process optimization.

Can I automatically update skill files based on recurring API integration issues?▼

Yes, you can automatically propose updates to skill files based on recurring API integration issues. When flaky integrations appear across three work packages, the analysis surfaces the pattern and generates surgical documentation fixes for coordinator approval.

Why do recurring development frictions often get ignored as isolated incidents?▼

Recurring development frictions get ignored as isolated incidents because they lack cross-session aggregation. Without pattern mining across multiple work packages, systemic issues remain hidden in individual retro logs, preventing teams from seeing the three-occurrence threshold needed for action.

When should I not use automated retro log analysis for process improvement?▼

You should not use automated retro log analysis when you lack multiple work package sessions or when isolated incidents have not yet reached the three-occurrence threshold. Without sufficient recurring patterns, the system cannot propose surgical modifications to process documentation.