compound-docs

# compound-docs > Each documented solution compounds your team's knowledge. The first time > you solve a problem takes research. Document it, and the next occurrence > takes minutes. Knowledge compounds. This skill is inspired by [Every.to's compound-engineering plugin](https://github.com/EveryInc/compound-engineering-plugin). ## 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](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 `root_cause.values` (or add new) | | Solution | Yes | The fix that worked | | Prevention | No | ...