compounding
Compounding Skill
If .khuym/onboarding.json is missing or stale for the current repo, stop and invoke khuym:using-khuym before continuing.
Research shows that engineering teams who systematically capture and re-inject learnings reduce time-to-complete on subsequent features by 30–50% (Compound Engineering, Every.to). This skill closes the loop. Each feature that runs through compounding makes the next one cheaper. Skip this step and the ecosystem stays flat. Run it and it gets smarter every cycle.
When to Use This Skill
Invoke after khuym:reviewing completes and the feature is merged (or abandoned with lessons).
Also invoke after any debugging session that surfaced a non-obvious root cause.
Skip only for trivial one-line changes where nothing reusable emerged.
Process
More from hoangnb24/skills
prompt-leverage
Strengthen a raw user prompt into an execution-ready instruction set for Codex or another AI agent. Use when the user wants to improve an existing prompt, build a reusable prompting framework, wrap the current request with better structure, add clearer tool rules, or create a hook that upgrades prompts before execution.
14khuym:using-khuym
Bootstrap meta-skill for the khuym agentic development ecosystem. Load first on any khuym project. Lists all 9+2 skills with routing logic, session scout/bootstrap, small-change vs standard-feature vs high-risk mode selection, go mode (full-auto pipeline with 4 human gates), priority rules, and state resume. Invoke when starting a new session, choosing which skill to use, running the full pipeline end-to-end, or resuming after a handoff.
7khuym:planning
>-
7khuym:executing
>-
6khuym:swarming
Orchestrates parallel worker agents for phase execution. Use after the khuym:validating skill approves the current phase for execution. Initializes the overseer/orchestrator context, spawns bounded worker subagents, monitors Agent Mail for completions/blockers/file conflicts, coordinates rescues and course corrections, and hands off either to planning for the next phase or to reviewing after the final phase. The orchestrator TENDS — it never implements beads directly.
6khuym:validating
|
6