compound

# Compound — Capture Solutions as Knowledge After fixing a problem, capture the solution as searchable institutional documentation. ## Usage ``` /phx:compound Fixed N+1 query in user listing /phx:compound Resolved LiveView timeout in dashboard /phx:compound # Auto-detects from recent session context ``` ## Philosophy > Each unit of engineering work should make subsequent units > easier — not harder. ## Workflow ### Step 1: Detect Context 1. If `$ARGUMENTS` provided, use as description 2. If no args, check scratchpad DEAD-END/DECISION entries, `git diff`, `.claude/plans/{slug}/progress.md` for recent completions 3. If unclear, ask: "What problem did you just solve?" **Only document non-trivial problems** that required investigation. ### Step 2: Search Existing Solutions Create `.claude/solutions/` directory if it doesn't exist (run `mkdir -p .claude/solutions`). Then search `.claude/solutions/` for relevant keywords using Grep. If found: **Create new** (different root cause), **Update existing** (same root cause, new symptom), or **Skip**. ### Step 3: Gather Details and Create Solution Extract from session context: module, symptoms, investigation steps, root cause, solution code, and prevention advice. Validate frontmatter against `${CLAUDE_PLUGIN_ROOT}/skills/compound-docs/references/schema.md`, then create file using `${CLAUDE_PLUGIN_ROOT}/skills/compound-docs/references/resolution-template.md`. **Write-blocked fallback**: if writing to `.claude/solution...