knowledge-compound

Knowledge-Compound — Extract and Persist Cycle Learnings

Goal: Turn ADR Part 10 (Cycle Retrospective) + code diff patterns into structured knowledge that shapes future brainstorming and planning sessions automatically.

Core insight: ADRs are read when you remember to search for them. Compound wiki entries are read automatically at the start of every planning session. The difference is compounding vs. archiving.

Trigger: Invoke immediately after adr-commit completes. One run per merged branch.

Announce: "Using knowledge-compound to extract cycle learnings."

---

Pre-Check

# Detect mode: DPS or legacy?
DPS_ADR=".dps/spec/ADR.md"
if [ -f "$DPS_ADR" ]; then
  echo "DPS MODE — reading ADR from $DPS_ADR"
  grep -c "Cycle Retrospective" "$DPS_ADR" | xargs echo "DPS ADR Part 10 entries:"
  # Get last ADR entry header for context:
  grep "^## ADR-" "$DPS_ADR" | tail -3
else
  echo "LEGACY MODE — reading from docs/superskills/adrs/"
  ls -t docs/superskills/adrs/*.md 2>/dev/null | head -3
  grep -l "Cycle Retrospective" docs/superskills/adrs/*.md 2>/dev/null | tail -1
fi

If no ADR with Part 10 found (in either mode) → prompt: "Run adr-commit first with Part 10 filled in."

---

Extraction Protocol

Read the most recent ADR. Extract into four categories:

Category 1: New Domain Terms

Read ADR Part 2 (Context) and Part 3 (Decision). Find terms used that are NOT in CONTEXT.md.

For each new term:

# Check if term exists:
grep -i "[term]" docs/superskills/CONTEXT.md 2>/dev/null | wc -l

• Exists → skip
• Missing → add to CONTEXT.md Ubiquitous Language with source: <!-- from ADR: [filename] -->

Category 2: Bug Patterns

Read ADR Part 5 (Consequences) and Part 10 (Cycle Retrospective). Find any bug class mentioned.

For each bug pattern:

# Check if already tracked:
grep -i "[pattern-slug]" docs/superskills/pattern-debt.md 2>/dev/null | wc -l

• Tracked → update actual_outcome field if this cycle resolved it
• New pattern (not yet a PATTERN-DEBT) → create entry if it recurred ≥ 2 cycles