compound

Document solved problems with root cause and AS-IS/TO-BE states.

Updated Mar 28, 2026

Search Tags:#context #problem-solving #learnings #root-cause #document #knowledge-base #learning-capture

Ready to run

npx skills add https://github.com/jimiryquai/pi-agent --skill compound-jimiryquai

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures problem solutions while context is fresh, creating structured documentation in experts/learnings using the save_learning tool.

Core Features & Use Cases

Structured capture of the root cause, AS-IS and TO-BE states, and verified fix
Automatic archival into experts/learnings for cross-project reference
Supports optional context hints to enrich future learnings and prevent regressions

Quick Start

Execute the compound command to document the latest solved problem and add optional context.

Frequently Asked Questions about compound

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

FAQPage Schema

How do I document a solved debugging incident and capture the root cause?▼

To document a solved debugging incident, you capture the root cause, AS-IS and TO-BE states, and verified fix into a structured learning entry. This records the problem context while it is fresh, creating a cross-project reference for future prevention.

What is the best way to create a knowledge base entry from an operational fix?▼

Creating a knowledge base entry from an operational fix involves archiving the verified solution and problem context into a structured format. This automatically stores the documentation in a dedicated learnings directory for future cross-project reference.

What information do I need to structure a learning entry for a resolved problem?▼

Structuring a learning entry for a resolved problem requires the module, problem type, tags, title, and content. You should also capture the AS-IS state, TO-BE state, and the verified fix to ensure the documentation prevents future regressions.

Can I add context hints when capturing a solved problem for future reference?▼

Yes, you can add optional context hints when capturing a solved problem. These hints enrich the structured learning entry, providing additional problem-solving context to help prevent similar incidents and regressions across projects.

Does this approach work for documenting both debugging sessions and operational fixes?▼

Yes, this documentation approach works for debugging sessions, incidents, and operational fixes. It captures the AS-IS and TO-BE states alongside the root cause, ensuring any verified solution is valuable for archival and cross-project reference.