compounding
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.
What this skill does
# Compounding 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. ## Required Inputs - `history/<feature>/CONTEXT.md` - `history/<feature>/discovery.md` - `history/<feature>/approach.md` - `.khuym/state.json` or retained handoff artifacts - `.beads/` or `br show` output - review findings and debugging notes, if they exist - feature commit history If history files are incomplete, use the session summary and recent git diff as fallback evidence. Do not fabricate learnings. ## Operating Contract 1. Gather the feature context and reconstruct what actually ran. 2. Launch three analysis subagents in parallel: patterns, decisions, failures. 3. Synthesize findings into one dated `history/learnings/YYYYMMDD-<slug>.md` file. 4. Promote only genuinely critical, reusable lessons to `history/learnings/critical-patterns.md`. 5. Optionally integrate with CASS/CM when repo config enables it. 6. Update `.khuym/state.json` with the completed compounding run. Load `references/compounding-reference.md` for analysis prompts, promotion criteria, state update, and the learnings template. ## Hard Gates - Do not skip compounding for meaningful feature work just because the session feels done. - Do not promote everything as critical; keep `critical-patterns.md` high signal. - Do not write generic lessons. Each entry needs a concrete situation, root cause, and future rule. - Do not let subagents write final learnings files; the orchestrator synthesizes. ## Handoff ```text 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. ``` ## Reference Files | File | When to Load | |---|---| | `references/compounding-reference.md` | Protocol and learnings template |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.