compoundlisted

# Compound Document a recently solved problem or shipped feature to compound your project's knowledge. Each documented solution makes future planning and implementation faster — the agent consults `docs/solutions/` during `/research` and `/write-a-prd`, so lessons learned today prevent mistakes tomorrow. When the work surfaced planning or estimation surprises, capture those too. McConnell-style calibration only happens if actual work feeds back into future shaping. ## Invocation Position This is a primary pipeline skill at the end of the default delivery loop. Use `/compound` after a feature ships, after a high-value bug fix lands, or after a meaningful QA or review cycle exposes a lesson that future work should reuse. The merge and worktree teardown are owned by `/closeout`, not `/compound` — "shipped" means `/closeout` has merged the reviewed PR. `/compound` runs after that and never performs the merge itself. Do not use it for trivial edits or for lessons that belong entirely in a higher-fidelity artifact like a test, linter rule, or code comment without any durable project-level learning. ## Why This Exists Without this step, you've done traditional engineering with AI assistance. The first three steps of the workflow (plan, work, review) produce a feature. This fourth step produces a system that builds features better each time. ## When to Use - After shipping a feature (the happy path) - After fixing a tricky bug where the root cause was non-obvious - After a