experience-packlisted

Two-layer experience system for any project: keep a per-project EXPERIENCE.md ledger (dated entries: what happened, what we did, what it cost), then distill it through an experience-vs-decision boundary test into portable, noun-free lessons that other projects can safely reuse — experience inherits, decisions die. Ships a reference pack distilled from a real 5-rebuild contamination saga (source-lock bundles, planner/executor/ verifier role isolation, zero-context probes, quarantined banned-noun lists, bounded repair loops, multi-AI reference-not-instruction triage) plus five prevention advices. Use when the user says 经验包 / 记录经验 / 复盘 / 经验文件 / 沉淀经验 / experience pack / lessons learned / post-mortem / record this experience / distill experience / "what did we learn" / wants a project to learn from another project's history, or after any expensive incident worth recording. NOT for closing an iteration (use iteration-close) and NOT a decision register — decisions stay in the project's own truth files.
m1nga/skill-builder · ★ 0 · AI & Automation · score 72

Install: claude install-skill m1nga/skill-builder

# Experience Pack One sentence: every project keeps its own experience ledger; a boundary test distills the portable part; only the portable part travels between projects. ## The two layers | Layer | File | Owner | Content rules | |---|---|---|---| | Ledger | `EXPERIENCE.md` in the project root | the project | dated, concrete, project specifics allowed; process experience only — never product truth, never a decision register | | Portable | the project's portable-lessons file (e.g. `LESSONS.md`) and/or this skill's reference pack | travels | abstract, product-noun-free, true in a DIFFERENT project read by a stranger | Pipeline: something happens → ledger entry (same day, while it hurts) → periodic distillation pass → portable lessons. Strategy and product decisions never travel: **experience inherits, decisions die.** ## Protocol A — RECORD (ledger) Create `EXPERIENCE.md` at the project root on day one (or on first use). Append an entry when any of these happen: an incident cost real time/money/ trust; a method visibly worked; an independent reviewer caught something the author missed; a collaboration pattern succeeded or failed; the user corrected the agent's course. Entry format: ``` ### YYYY-MM-DD — title **What happened:** facts, concrete. **What we did:** the response, concrete. **What worked / what failed:** both, honestly. **Cost:** time / tokens / trust / rework. **Portable?** yes → <lesson-slug> | not yet | no (project-specific). ``` Rules: record process exp