distill

Files (1)

• SKILL.md

SKILL.md (first lines)

# distill

The curator step. Small deltas, never rewrites. Nothing you write here changes a live skill directly.

1. Read `build/12-retro.md` (the numbers and votes), `10-build-log.md`, `07-best-of-best.md`, `11-verify.md`, and review findings on this run's cards.
2. **Lessons** (≤5, the high-value path). Each is one concrete, checkable sentence tied to one skill, with evidence:
   `hbs lessons add --skill harvest --text "Check license via gh api before scoring Safe; README badges were wrong twice" --source <repo>:<node>`
   hbs merges near-duplicates into the existing bullet (+1 helpful) instead of adding noise. Future cards for that skill get the top lessons injected as evidence.
3. **Skill proposals** (only when a lesson is really a procedure change). Write a full candidate:
   ```
   ~/.build-framework/learning/proposals/<YYYYMMDD>-<skill>-<slug>/
     SKILL.md     # the whole candidate skill, edited minimally
     meta.yaml    # skill: <name>, rationale: <one line>, evidence: [<run/card ids, verify lines>]
   ```
   A brand-new skill (a reusable procedure that emerged) uses the same layout with a new name.
   Do not run the eval yourself; `skill-evolve` grades it on a different vendor.
4. Write `build/13-distill.md`: lessons added/merged (ids), proposals written (paths), and what you chose *not* to keep.
5. Append the build-log line. Complete the card (chat mode: mark distill done in STATUS).

Never:
- edit `~/.build-framework/skills/*` or `evals/*` directly;
- dump the transcript into AGENTS.md or a skill;
- store secrets, customer data, or raw logs in lessons.

From Kshintak/new-build-framework, MIT.

More from Kshintak/new-build-framework