Distillation
Turn execution experience into a concise retrospective and, only when justified, durable skill guidance.
Approach
- Reconstruct what was attempted, what happened, what changed, and what evidence is available.
- Summarize outcomes, effective choices, friction, failures, corrections, and unresolved issues.
- Identify causes and reusable lessons rather than merely repeating the timeline.
- Decide whether each lesson is one-off, project-local, or broadly reusable.
- Check existing skills before proposing a new one.
- Update a skill only when the evidence reveals missing, misleading, duplicated, or repeatedly improvised guidance.
- Propose a new skill only when the capability has a distinct trigger, boundary, and recurring user value.
- Prefer the smallest useful change; do not add process weight without evidence that it prevents recurring friction.
If the user requested only a retrospective, recommend skill changes but do not edit skills without approval. When changing skills, check overlap, trigger confusion, duplication, bundle scope, references, language, and repository validation rules.
Output
In the user’s language, provide a short retrospective, reusable lessons, and one of: no skill change, update an existing skill, or propose a new skill. Support the decision with concrete evidence and name the smallest next change.