instruction-management

Read STATE.md and maintain it: move completed items from WIP/ToDo into a timestamped Completed section, create STATE.md if absent, and surface durable decisions back to the caller as AGENTS.md candidates. Invoke via Agent tool and pass the current timestamp in your prompt. Runs on Haiku so the main session does not burn tokens on bookkeeping.

Audit and improve AGENTS.md project instructions (and legacy CLAUDE.md). Use when the user asks to check, audit, update, improve, fix, restructure, or clean up AGENTS.md / CLAUDE.md, or mentions "agent memory", "project memory", "project instructions", "instruction file", "instruction maintenance", "instruction structure", or filenames like AGENTS.md, agents.md, CLAUDE.md. Scans the repo, evaluates quality against a rubric, prints a report, and proposes targeted edits. When the repo still uses CLAUDE.md only, also proposes migrating to AGENTS.md.

Restructure project instruction files (AGENTS.md / legacy CLAUDE.md) to move content closer to where it is needed, reducing context bloat in the root file. Use when the user asks to restructure, reorganize, rebalance, or clean up instruction-file depth, or when root AGENTS.md content only applies to a specific subdirectory and should live there instead.

Update AGENTS.md (or legacy CLAUDE.md) with learnings from this session — discovered commands, patterns, gotchas, or configuration quirks worth capturing for future sessions. Use when the user asks to capture, save, remember, or record session learnings into project instructions, or after a session that surfaced non-obvious context a fresh agent would benefit from.

1 hook across 1 event