Agent skill · writing content · aiskillstore
compound-docs
Capture solved problems as searchable documentation with pattern detection. This skill auto-triggers when users confirm a fix worked ("that worked", "it's fixed", "working now") or manually via /compound command.
Why this skill is useful
Adds a structured documentation workflow for capturing and categorizing problem-solving patterns that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Auto-Invoke Triggers This skill auto-triggers when the user says: "that worked" "it's fixed" "working now" "problem solved" "that did it" Manual command: /compound Workflow Step 1: Detect Trigger When a trigger phrase is detected or /compound is invoked: 1. Confirm the problem is actually solved (not still in progress) 2. Check if the fix is worth documenting Skip documentation for trivial fixes: Simple typos Obvious syntax errors (missing semicolon, bracket) Single-line fixes that were immediately obvious If skipping, briefly explain why: "This was a simple typo fix - skipping documentation." Step 2: Gather Context Read schema.yaml to get valid enum values, then extract from the conversation: Field Required Description ---------- -------- ------------------------------------------------- Symptom Yes Error message or observable behavior Category Yes From schema.yaml category.values (or add new) Component No From schema.yaml component.values (or add new) Root cause No From schema.yaml rootcause.values (or add new) Solution Yes The fix that worked Prevention No How to avoid this in the future If a value doesn't exist in schema.yaml: 1. Add the new value to the appropriate enum in schema.yaml 2. If it's a new category, create the directory: mkdir -p {outputdir}/{new-category} If critical info is missing, ask: Step 3: Check for Similar Issues Before creating a new doc, search for similar existing issues: 1. Keyword match - Search {outputdir}/ for error message fragments or key symptom phrases 2. File path match - Check if the same files are involved in existing docs 3. Import/dependency match - Check if the same libraries or modules are mentioned If potential matches found: If related, add to the related field in frontmatter. Step 4: Create Documentation Validate against schema.yaml: 1. Read schema.yaml for current valid enum values 2. Ensure all required fields are present 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/compound-docs