Setting the file. One moment.
Use this path when improving a skill based on outcomes and examples.
Read references/iteration-evidence.md when examples should be persisted across future skill revisions.
Capture example records with:
- label (
positive or negative)
23.10
Example Hook Backed Skill
example kind (true-positive, false-positive, fix, regression, edge-case)evidence origin (human-verified, mixed, synthetic)anonymized contentsource provenance pointer (where the example came from)
- Review behavior against working set.
- Review behavior against holdout set.
- Record improved/unchanged/regressed outcomes.
- Confirm both positive and negative behavior changed in the expected direction.
- Prioritize fixes for repeated negative patterns.
- Preserve behavior that consistently succeeds on positives.
- Update transformed examples when guidance changes.
- Record deltas in
SOURCES.md changelog.
- Expand input collection when failures indicate coverage gaps.
- Store durable positive/negative examples in
references/evidence/ instead of overloading SKILL.md, SOURCES.md, or a generic reference file.
- Keep holdout examples separate from working examples until validation is complete.
- Update
SPEC.md when iteration changes the skill’s intended scope, evidence model, validation expectations, or known limitations.
- Example intake summary
- Behavior deltas
- Updated artifacts
- Replay summary
references/iteration-path.md