compound

Extract reusable patterns, pitfalls, and decisions from completed development cycles into structured knowledge documents.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill compound-ab300819
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compound
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/compound
Command: npx skills add https://github.com/ab300819/keel-workflow --skill compound-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a development cycle ends, valuable lessons—what worked, what broke, and why decisions were made—are usually lost. This Skill captures those insights from completed keel development cycles and turns them into reusable pattern documents so future iterations avoid repeated mistakes. ## Core Features & Use Cases - Pattern Extraction: Reviews verify reports, dev task documents, and git history to identify positive patterns, pitfalls, key decisions, and workflow improvements. - Deduplication & Confirmation: Scans existing patterns in docs/devdocs/patterns/ to avoid duplicates and confirms each candidate with the user before writing. - Verify Blindspot Loop: Records issues that verification missed into verify-blindspots.md, feeding back into future verification runs. - System Learning Check: Every run answers whether lessons should become rules, templates, or automated checkers. - Use Case: After finishing a feature with /sync and /verify, run /compound to distill two reusable patterns and one template gap into docs/devdocs/patterns/ for the next iteration. ## Quick Start Ask the AI to run the compound skill to extract reusable patterns and lessons from the just-completed development cycle.

Frequently Asked Questions about compound

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

FAQPage Schema
How do I extract lessons learned from a completed development cycle?

Run the compound skill after finishing a development iteration. It reviews verify reports, dev task documents, and git history, then proposes candidate patterns, pitfalls, and decisions for you to confirm before writing them to docs/devdocs/patterns/.

What is the difference between compound and sync skills?

The sync skill updates documentation status and traceability matrices, handling document-level completion. The compound skill extracts experience and reusable patterns, handling knowledge-level retention. Run sync first, then compound.

Can I preview extracted patterns without writing files?

Yes, run compound with the --extract-only flag to preview candidate patterns without writing any files. Use --check to only evaluate whether unrecorded lessons exist.

What kinds of patterns are worth extracting?

Worth extracting: solutions to recurring problems, pitfalls with fixes, decisions with non-obvious tradeoffs, improved workflows, and verification blindspots. Not worth extracting: project-specific details, obvious best practices, or temporary workarounds.

Does compound modify my code or existing project documents?

No. It only creates or updates files under docs/devdocs/patterns/. It never modifies code files, existing keel documents, or AGENTS.md directly; for AGENTS.md updates it suggests running the agent-memory skill instead.