// Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
| name | reflect |
| description | Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this". |
Review the conversation and persist learnings — to docs/, to skill files, or as structural enforcement.
docs/index.md to understand what notes already existdocs/index.md if any brain files were added or removedNot everything belongs in the brain. Route each learning to where it will have the most impact.
Before routing a learning to docs/, ask: can this be a lint rule, script, metadata flag, or runtime check? If yes, encode it structurally and skip the brain note. See docs/principles/encode-lessons-in-structure.md.
docs/)Codebase knowledge, principles, gotchas — anything that informs future sessions. This is the default destination. Use the brain skill for writing conventions.
[[wikilinks]]..agents/skills/<skill>/)If a learning is about how a specific skill works — its process, prompts, or edge cases — update the skill directly.
Follow-up work that can't be done during reflection — bugs, non-trivial rewrites, tooling gaps. File as a todo or backlog item.
## Reflect Summary
- Brain: [files created/updated, one-line each]
- Skills: [skill files modified, one-line each]
- Structural: [rules/scripts/checks added]
- Todos: [follow-up items filed]
Read/write brain files (Obsidian vault at docs/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers: docs/ modifications, "add to brain".
Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".
Break down medium-to-large tasks into phased plans in docs/plans/. Planning only — does not implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".
Principle-grounded review of code changes, PRs, or plans. Use when asked to review, critique, or assess quality of work — "review", "review this", "code review", "check this".
Mine past Claude Code conversations for uncaptured patterns, corrections, and knowledge. Cross-references with existing brain content. Triggers: "ruminate", "mine my history".