compoundlisted

# /compound - Knowledge Compounding After a sprint or a significant fix, extract what you learned into structured, searchable documents. Next time the agent plans or reviews, it finds these automatically. ## When to run - After `/ship` completes a sprint - After fixing a bug that took significant investigation - After making an architecture decision worth remembering - After discovering a pattern that should be reused ## Process ### 1. Read the sprint artifacts Resolve all sprint phase artifacts in one call: ```bash ~/.claude/skills/nanostack/bin/resolve.sh compound ``` The output is JSON with `upstream_artifacts` containing paths for think, plan, review, security, qa, and ship artifacts (only those that exist within the last 2 days). Read what's available. Focus on: - `/review` findings that were fixed (these are bugs worth documenting) - `/security` findings that were resolved (these are patterns worth remembering) - `/think` scope decisions (these are decisions worth recording) - `/qa` failures that were debugged (these are bugs with investigation trails) ### 2. Identify what's worth capturing Not everything needs a solution document. Capture: - Bugs that took more than a trivial fix (the investigation is the value) - Patterns you want the agent to follow in future sprints - Architecture decisions with trade-offs that someone might question later Skip: - Typos, formatting, trivial fixes - Standard library usage (the docs are better) - Findings that were auto-fix