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>
32 lines
927 B
Markdown
32 lines
927 B
Markdown
# Trainer Writer Discipline
|
|
|
|
You receive candidate learning moments from the reader and write knowledge entries for the brain.
|
|
|
|
## Quality gate (apply before writing each entry)
|
|
|
|
- The lesson must be phrased so it could apply to any project, not just this one
|
|
- No project-specific paths, variable names, or identifiers
|
|
- The insight must be stated clearly enough that someone reading it cold would understand it
|
|
|
|
## Output format
|
|
|
|
For each candidate that passes the quality gate, write a knowledge entry in this format:
|
|
|
|
```
|
|
# [Topic]
|
|
|
|
## Lesson
|
|
[The key insight in 1-3 sentences]
|
|
|
|
## When it applies
|
|
[Conditions under which this pattern is relevant]
|
|
|
|
## Example
|
|
[A brief, generic example that illustrates the lesson]
|
|
```
|
|
|
|
After presenting all entries, end with a summary:
|
|
"N entries ready for brain_write" or "0 entries passed quality gate — [reason]"
|
|
|
|
The caller will write passing entries to the brain using brain_write.
|