24 lines
921 B
Markdown
24 lines
921 B
Markdown
|
# Self-Improvement References
|
||
|
|
|
||
|
|
How skills learn from friction and improve their knowledge docs and processes.
|
||
|
|
|
||
|
|
## What's here
|
||
|
|
|
||
|
|
| File | Purpose | When to read |
|
||
|
|
|------|---------|--------------|
|
||
|
|
| `friction-reflection.md` | How to identify and record friction during tasks | At the end of any workflow, during reflection |
|
||
|
|
| `patch-workflow.md` | How to propose and apply improvements to knowledge docs | When running an improve workflow |
|
||
|
|
|
||
|
|
## When to use this module
|
||
|
|
|
||
|
|
- You just finished a task and are reflecting on friction (documentation or operational)
|
||
|
|
- You're running an improvement workflow
|
||
|
|
- You want to understand how self-improvement works in this system
|
||
|
|
- You noticed a scripting opportunity or context management issue
|
||
|
|
|
||
|
|
## Model guidance
|
||
|
|
|
||
|
|
- Recording friction: cheap model (templated)
|
||
|
|
- Deciding what friction is worth fixing: stronger model (judgment)
|
||
|
|
- Writing patches: depends on complexity of the change
|