Compound

/compound

The compound engineering flywheel for Guitar Alchemist. Run this after shipping a feature to extract lessons and identify what should be promoted into a higher-level abstraction.

When to Run

• After merging or completing a feature branch
• When you notice yourself writing similar code for the third time
• Before planning the next feature (to see if new vocabulary has emerged)
• On a cadence: weekly or after every 3–4 commits

What It Does

Seven-step loop — every completed feature feeds back into the language and the docs:

Work → Reflect → Compound → Promote → Encode → Govern → Document

Step	Who	What
Work	—	Feature is done; git diff is the input
Reflect	compound-researcher	Mine changed files for repeated patterns
Compound	compound-researcher	Rank patterns by recurrence + impact
Promote	fsharp-architect	Decide tier (helper / DU / CE / DSL / MCP tool) per pattern
Encode	fsharp-architect	Produce concrete F# design sketch with usage examples
Govern	grammar-governor	Audit stability; block or clear each promotion
Document	codebase-documenter	Snapshot current system state as .md files

Recent work
    └─► compound-researcher  (Reflect + Compound)
            └─► fsharp-architect   (Promote + Encode)
                    └─► grammar-governor  (Govern)
                              └─► codebase-documenter  (Document)
                                          └─► Compound Report + Snapshots

How to Invoke

/compound

No arguments needed. The skill reads git log and recent file changes automatically.

---

Execution Steps

Step 1 — Scope the work

git log --oneline -10
git diff --stat HEAD~5..HEAD

Identify which files changed. Focus the rest of the analysis on those files and their immediate neighbours.

Step 2 — Run compound-researcher

Delegate to the compound-researcher agent:

"Mine these changed files for repeated patterns that are candidates for abstraction. Files: [list]. Report the top 3–5 patterns."