Compound

Extract and store lessons learned from development cycles into a persistent knowledge base.

1|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/htxryan/claude-code-config-profiles --skill compound-htxryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Compound
Source: https://github.com/htxryan/claude-code-config-profiles/tree/main/.agents/skills/compound/compound
Command: npx skills add https://github.com/htxryan/claude-code-config-profiles --skill compound-htxryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development sessions produce valuable insights that are typically lost when the session ends, forcing teams to relearn the same lessons repeatedly. This Skill captures lessons, solutions, and patterns from each work cycle and stores them in a searchable knowledge base so future sessions start better equipped. ## Core Features & Use Cases - Multi-Agent Analysis Pipeline: Spawns a coordinated team of analyzer agents (context-analyzer, lesson-extractor, pattern-matcher, solution-writer) to review cycle artifacts like git diffs, test results, and spec drift. - Quality-Filtered Knowledge Capture: Applies novelty and specificity checks, deduplicates against existing lessons via search, and classifies items by type (lesson, solution, pattern, preference) and severity before storing them via the ca learn CLI. - Spec and Verification Drift Detection: Compares final implementation against original EARS requirements and the epic's Verification Contract to capture workflow-quality lessons. - Use Case: After completing a feature epic, run this Skill to analyze what changed versus the plan, confirm high-severity findings with the user, store concrete lessons, and deprecate outdated ADRs before closing the epic. ## Quick Start Ask the AI to run the compound phase to reflect on this cycle, extract lessons learned, and store them for future sessions.

Frequently Asked Questions about Compound

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

FAQPage Schema
How do I capture lessons learned from a development session?▼

Run the compound phase at the end of a cycle to analyze git diffs, test results, and plan context. The Skill spawns analyzer agents that extract concrete lessons, filters them for novelty and specificity, and stores them via the ca learn command.

How do I detect spec drift between requirements and implementation?▼

Compare the final implementation against the original EARS requirements in the epic description using bd show. The Skill flags divergences, evaluates whether they were justified, and captures wrong or incomplete specs as lessons.

Where are lessons stored and how do I avoid duplicates?▼

Lessons are stored in .Codex/lessons/index.jsonl through the ca learn CLI, never in MEMORY.md or markdown files. Before storing, run ca search to check for duplicates, and apply a novelty filter that skips items above 0.98 cosine similarity.

When should high-severity lessons require user confirmation?▼

High-severity items involving data loss, security issues, or contradictions require explicit user confirmation via AskUserQuestion before storage. Medium and low severity items such as workflow patterns and style notes are auto-stored without confirmation.

What happens if the verify-gates check fails before epic closure?▼

If ca verify-gates does not return PASS for both gates, a required phase was skipped and the epic cannot close. Go back and complete the missing phase, then rerun tests, lint, and any remaining Verification Contract evidence items.