telum-ai speck-learn
Capture the smallest durable truth and apply it where it is already binding.
- Classify it as
PATTERN,GOTCHA,PERF,ARCH,RULE, orDEBT. - Record context, evidence, scope, and the next application in the current story artifact or commit body. A
DEBTalso names its owner and trigger. - Update affected specs, plans, tests, decisions, or code now; do not create a second source of truth just to preserve the observation.
- A first occurrence stays local and is harvested by
story-retrospective. Repeated, independently useful occurrences may be promoted by epic or project retrospective into project-owned.speck/patterns/learned/. - Route a Speck template, script, or methodology defect to
speck-feedback; it is not a project pattern.
Promotion requires evidence of recurrence and a named consumer. Vanilla Speck ships no learned project patterns.