/compound

Extract and index learnings from completed tasks into reusable principles.

4|3|Updated Jan 22, 2026

Search Tags:#knowledge management #learning #retrospective #post-mortem #continuous improvement #organizational intelligence

Ready to run

npx skills add https://github.com/yohayetsion/product-org-os --skill compound-yohayetsion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /compound
Source: https://github.com/yohayetsion/product-org-os/tree/main/product-org-plugin/skills/compound
Command: npx skills add https://github.com/yohayetsion/product-org-os --skill compound-yohayetsion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams systematically capture, generalize, and index learnings from completed tasks and projects, preventing repeated mistakes and accelerating knowledge sharing.

Core Features & Use Cases

Structured Reflection: Guides users through a series of questions to analyze task outcomes, identify root causes, and generalize insights.
Learning Documentation: Provides a template for saving learnings with context, evidence, and application notes.
Knowledge Indexing: Ensures learnings are added to a central index for easy retrieval and cross-referencing.
Use Case: After a product launch, use this Skill to reflect on what worked well, what didn't, and why, then save these as reusable principles for future launches.

Quick Start

Reflect on the recent project completion and extract key learnings.

Frequently Asked Questions about /compound

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

FAQPage Schema

How do I capture organizational learnings from completed projects?▼

To capture organizational learnings, use structured reflection to analyze task outcomes, identify root causes, and generalize insights into reusable principles. The extracted knowledge is then saved with context and indexed for future cross-referencing and application.

What is the best way to run a project post-mortem for continuous improvement?▼

A project post-mortem for continuous improvement is best executed by guiding teams through structured questions to evaluate what worked and what failed. This process extracts generalized, reusable principles and systematically indexes them to build organizational intelligence.

How does systematic knowledge indexing prevent repeated mistakes?▼

Systematic knowledge indexing prevents repeated mistakes by saving extracted learnings with context, evidence, and application notes into a central repository. This ensures teams can easily retrieve past insights and apply generalized principles to future tasks.

Can I use structured reflection to document root cause analysis for product launches?▼

Yes, you can use structured reflection to document root cause analysis for product launches. It guides you through analyzing task outcomes and generalizing insights into reusable principles, which are then saved with application notes for future launches.

What should I do after extracting reusable principles from a retrospective?▼

After extracting reusable principles from a retrospective, you should document the learnings with context and evidence. The final step is adding these insights to a central knowledge index for easy retrieval and cross-referencing in future projects.