Reflect

Reflect is an orchestrator-only workflow for learning from repeated work. It looks back over recent sessions, project notes, and existing agent assets, then recommends the smallest useful improvement: a skill, custom agent, command, configuration change, prompt rule, documentation playbook, or no change.

The goal is to identify real repeated friction and suggest practical improvements with evidence.

Branch: lines marked [branch: --sessions] run only with that flag; plain /reflect skips Session Mode.

When to Use

Use Reflect when the user asks to:

• run /reflect or /reflect <focus>;
• run /reflect --sessions for session archaeology;
• learn from recent sessions or repeated workflows;
• find work they keep doing manually;
• improve their oh-my-opencode-slim setup based on actual usage using oh-my-opencode-slim skill;
• review whether a recurring process should become a reusable playbook;
• turn repeated workflow friction into a safer future default.

Do not use Reflect for ordinary implementation work, one-off debugging, broad architecture review, or speculative agent creation without workflow evidence.

Session Mode [branch: --sessions]

When the user includes --sessions in their reflect command, shift to session archaeology: analyze historical OpenCode sessions across all repos to find repeated patterns, friction, and improvement opportunities.

Session Discovery

1. Detect the schema, then load recent sessions. OpenCode v2 keeps live data in session_v2 + session_message; legacy v1 databases keep session
   • message (on v2 hosts those may still exist but are empty leftovers). Detect by probing session_v2 in sqlite_master and select the pair together, never per-table: session_message can exist on v1 hosts holding only metadata rows.