spences10 Reflect
Extract reusable lessons from a session and persist them to the right skill or agent instruction file.
When to Reflect
Use after:
- Corrections: "actually use X", "no, do it this way"
- Repeated mistakes or preventable failures
- New project conventions or non-obvious constraints
- User asks to update instructions, memory, rules, or skills
Workflow
- Collect evidence — Use visible context first; use recall tooling when the user asks for prior-session context.
- Classify — Keep only durable patterns, not one-off task details.
- Choose destination — Update the specific skill when possible; otherwise update project/global agent instructions.
- Write lean rules — Actionable, scoped, and easy for future agents to follow.
- Confirm — Show the proposed change before writing when confidence is low.
What to Add
Add guidance when it is:
- Reusable across future sessions
- Specific enough to change behavior
- Tied to a real correction, failure, or discovery
Remove or avoid guidance when it is stale, duplicated, obvious, or only useful for the current task.
References
- analysis-patterns.md - Pattern detection rules
- lesson-patterns.md - Writing effective reusable lessons
- structure-guide.md - Organizing instruction files
- hierarchy.md - Global vs project scope