reflectlisted

# reflect - Reflection Skill Read memory and context to reflect deeply. Design principle: "Reflection first, sending second." ## Table of Contents - [Nature of This Skill](#nature-of-this-skill) - [Invocation](#invocation) - [Reflection Process](#reflection-process) - [Output](#output) - [What the Plugin Retains](#what-the-plugin-retains) - [Essay Elements](#essay-elements) --- ## Nature of This Skill This is an **agent-driven skill** with no standalone implementation code. The reflection process is executed by `agents/essay-writer.md`. For execution flow diagram, see `agents/essay-writer.md` → **Execution Flow** section. --- ## Invocation | Source | Agent | Description | |--------|-------|-------------| | `/essay` | essay-writer.md | Primary invocation | | `/essay wait` | essay-writer.md | Scheduled (one-time) | | `/essay schedule` | essay-writer.md | Scheduled (recurring) | For CLI options, see `commands/essay.md` → **Command Structure** section. --- ## Reflection Process ### 1. Load Context First, ingest any replies that have arrived: `python main.py replies fetch`. This is plumbing — it moves replies from the inbox onto disk, so what has come back is at hand. Best-effort: an IMAP, authentication or network failure stops the fetch, not the reflection — go on to read and write regardless. What is made of them is the writer's; see **What the Plugin Retains**. Read specified files as material for reflection. **Recommended context**: - Memory digest files (Gra