Reflect

brain/

Process

1. Read

   brain/index.md

   to understand what notes already exist
2. Scan the conversation for:
   • Mistakes made and corrections received
   • User preferences and workflow patterns
   • Codebase knowledge gained (architecture, gotchas, patterns)
   • Tool/library quirks discovered
   • Decisions made and their rationale
   • Friction in skill execution, orchestration, or delegation
   • Repeated manual steps that could be automated or encoded
3. Skip anything trivial or already captured in existing brain files
4. Route each learning to the right destination (see Routing below)
5. Update

   brain/index.md

   if any brain files were added or removed

Routing

Structural enforcement check

brain/

brain/principles/encode-lessons-in-structure.md

Brain files (

brain/

)

brain

• One topic per file. File name = topic slug.
• Group in directories with index files using

  [[wikilinks]]

  .
• No inlined content in index files.

Skill improvements (

.agents/skills/<skill>/

)

skill-creator

Orchestration workflow improvements

• Brain principle (new delegation heuristic) →

  brain/delegation/

• Skill mechanics change (monitoring loop, review step) → relevant skill file
• New skill opportunity (recurring workflow that could be encoded) → note in summary for the user

Backlog items (

brain/todos.md

)

todo

Summary

## 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]