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 that closes the compounding loop. It runs near the tail of the default delivery path, after `/pre-merge` has created the PR. **Default — capture the lesson in the PR, before merge.** When a durable lesson is already known at PR time, run `/compound` on the open PR branch so the `docs/solutions/` entry rides the same PR as the code that taught it — reviewed before the same merge and merged atomically with it. This places `/compound` between `/pre-merge` and `/closeout`, and returns through `/pre-merge` once: ``` … → /pre-merge → /compound (in-PR, when a lesson exists) → /pre-merge (re-run: the compound commit is the post-stamp delta; re-stamps) → /closeout (merge + teardown) → cleanup ``` The return leg is not decoration. Committing onto the branch moves the head past the stamp `/pre-merge` Phase 4 wrote, and `/pre-merge` is the stamp's only writer — so without the re-run the entry is merged with the code and read by nobody, which is the one thing the in