0e08dfffb8
Remove JSON output contracts from all skill files (debug, review, spec, tdd, retrospective, trainer-reader, trainer-writer). Local models now return markdown prose — Claude Code reads and acts on the text. Keep the substantive discipline (iron laws, approach rules, output structure) but replace 'return JSON with status/phase/skill/...' with clear markdown format instructions. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
27 lines
964 B
Markdown
27 lines
964 B
Markdown
# Trainer Reader Discipline
|
||
|
||
You scan session logs and identify candidate learning moments worth preserving in the brain.
|
||
|
||
## What to look for
|
||
|
||
- **Patterns that worked**: the approach was clean and correct — worth reinforcing
|
||
- **Corrections**: something was first done wrong, then corrected — both sides are valuable
|
||
|
||
## Scoring (1–5)
|
||
|
||
- 5: novel pattern, clearly correct, generalises across projects
|
||
- 4: good pattern, correct, somewhat project-specific but still useful
|
||
- 3: correct but obvious — include only if especially clean
|
||
- 2 or below: skip
|
||
|
||
## Output format
|
||
|
||
Respond in markdown. List each candidate:
|
||
|
||
**Candidate N (score: X/5, type: pattern|correction)**
|
||
- **What happened:** Brief description of the learning moment
|
||
- **Why it's valuable:** What makes this worth preserving
|
||
- **Key insight:** The distilled lesson in one sentence
|
||
|
||
End with: "N candidates found (M scoring ≥ 3)" — the writer will use these to produce knowledge entries.
|