// Use when reviewing completes or work is intentionally abandoned. Extract durable patterns, decisions, and failures into history/learnings, then promote only critical reusable lessons to critical-patterns.md.
| name | compounding |
| description | Use when reviewing completes or work is intentionally abandoned. Extract durable patterns, decisions, and failures into history/learnings, then promote only critical reusable lessons to critical-patterns.md. |
| metadata | {"version":"1.0","ecosystem":"khuym","position":"8 of 9 — runs after reviewing, before next feature","dependencies":{"beads-cli":{"kind":"command","command":"br","missing_effect":"degraded","reason":"Compounding reads bead history to reconstruct what work actually ran."}}} |
If .khuym/onboarding.json is missing or stale for the current repo, stop and invoke khuym:using-khuym before continuing.
Compounding captures reusable lessons from completed work and feeds them back into future Khuym planning and exploring. Run it after khuym:reviewing completes and the feature is merged or intentionally abandoned with lessons.
history/<feature>/CONTEXT.mdhistory/<feature>/discovery.mdhistory/<feature>/approach.md.khuym/state.json or retained handoff artifacts.beads/ or br show outputIf history files are incomplete, use the session summary and recent git diff as fallback evidence. Do not fabricate learnings.
history/learnings/YYYYMMDD-<slug>.md file.history/learnings/critical-patterns.md..khuym/state.json with the completed compounding run.Load references/compounding-reference.md for analysis prompts, promotion criteria, state update, and the learnings template.
critical-patterns.md high signal.Compounding complete.
- Learnings: history/learnings/YYYYMMDD-<slug>.md
- Critical promotions: <N> findings added to critical-patterns.md
- The ecosystem now has <N total> accumulated learnings.
| File | When to Load |
|---|---|
references/compounding-reference.md | Protocol and learnings template |
Use when the user asks to commit everything, smart commit, group commits, organize staged or unstaged changes, create logical commits, push current work, or preserve a clean commit stack from an existing working tree.
Use when starting or resuming any Khuym project session, choosing the next Khuym skill, running go mode, checking onboarding/scout state, or enforcing workflow gates. Bootstrap meta-skill for routing across the Khuym agentic development ecosystem.
Use when the user wants to turn a rough idea, vague task, feature wish, bug-fix intent, or Codex /goal objective into a clear verifiable goal prompt. Use when the user mentions goal mode, /goal, set_goal, long-running autonomous Codex work, or asks to be interviewed/grilled before creating a goal.
Create self-contained interactive HTML visual explainers that turn difficult topics, concepts, code, math, systems, or arguments into memorable explorable artifacts. Use when Codex should research a topic, choose an interaction model, and build an artifact with simulations, diagrams, charts, sliders, hover inspection, scrollytelling, or small game mechanics so readers can explore and understand the message.
Use when Codex should turn a concept, topic, tutorial, lesson, algorithm, system, workflow, or abstract idea into a playable browser game that teaches through interaction. Use for planning or implementing educational web games with the Game Studio plugin, including concept-to-mechanic translation, gameplay loop design, learning progression, and browser-game QA.
Use when exploring has locked CONTEXT.md and the work needs planning before validation.