compound-docs

compound-docs Skill

Purpose: Automatically document solved problems to build searchable institutional knowledge with category-based organization (enum-validated problem types).

Overview

This skill captures problem solutions immediately after confirmation, creating structured documentation that serves as a searchable knowledge base for future sessions.

Organization: Single-file architecture - each learning documented as one markdown file in the category directory its problem_type maps to (e.g., docs/solutions/performance-issues/n-plus-one-report-queries.md). Files use YAML frontmatter for metadata and searchability.

Two tracks: The problem_type decides the track. The bug track documents a defect that was diagnosed and fixed, and requires symptoms, root_cause and resolution_type. The knowledge track documents a practice, pattern, convention or workflow decision, and needs none of those. The track lists live in references/schema.yaml.

Prerequisites: The problem has been solved and the solution has been verified working, or the guidance has been confirmed. Do not document in-progress investigations as finalized solutions.

---

<critical_sequence name="documentation-capture" enforce_order="strict">

7-Step Process

Auto-invoke after phrases:

• "that worked"
• "it's fixed"
• "working now"
• "problem solved"
• "that did it"

OR manual: Invoke the ce:compound skill directly

Non-trivial problems only:

• Multiple investigation attempts needed
• Tricky debugging that took time
• Non-obvious solution
• Future sessions would benefit

Skip documentation for:

• Simple typos
• Obvious syntax errors
• Trivial fixes immediately corrected

Decide the track first: a fixed defect is the bug track, and a practice or decision worth keeping is the knowledge track. Then extract from conversation history: