Recall

Required Visible Completion Note

Before moving on, produce an explicit completion note in your reasoning or user update using one of these forms:

• Recall complete: searched .evolve/entities/, read <files>, applicable guidance: <summary>
• Recall complete: searched .evolve/entities/, no relevant entities found

Minimum Acceptable Procedure

1. List or search files under .evolve/entities/.
2. Identify candidate entities relevant to the task.
3. Open and read those entity files.
4. Summarize what applies, or state that nothing applies.

Failure Conditions

The skill is not complete if any of the following are true:

• You only read this SKILL.md
• You did not inspect .evolve/entities/
• You did not read the relevant entity files
• You proceeded without stating whether guidance was found

How It Works

1. If Codex hooks are enabled in ~/.codex/config.toml with [features] codex_hooks = true, the Codex UserPromptSubmit hook runs before the prompt is sent.
2. The helper script reads the prompt JSON from stdin.
3. It loads stored entities from .evolve/entities/.
4. It prints formatted guidance to stdout.
5. Codex adds that text as extra developer context for the turn.

Entities Storage

Entities are stored as markdown files in .evolve/entities/, nested by type:

.evolve/entities/
  guideline/
    use-context-managers-for-file-operations.md
    cache-api-responses-locally.md

Each file uses markdown with YAML frontmatter:

---