mew

Re-enter mew planning or long-session work after context compression, interruption, or a user asks what to do next. Use to recover current work, durable product decisions, deferred decisions, and the next safe action from mew's own state and memory.

Run isolated mew side-project implementation as mew-first dogfood, update SIDE_PROJECT_ROADMAP_STATUS.md, and record structured M6.13.2 telemetry for M6.16 implementation-lane polish.

Evaluate mew as a passive AI product and as a shell/body that an AI model might want to inhabit. Use when asked whether mew is good enough, whether it feels usable as the next execution form, or what should improve next.

Update mew roadmap milestone status. Use when asked to assess progress against ROADMAP.md, refresh milestone statuses, decide the next roadmap target, or preserve roadmap progress across context compression.

Run bounded mew roadmap/coding tasks with mew as the first implementer and Codex as reviewer. Use when implementing mew tasks after M6.7, assessing mew-first success or failure, deciding whether to repair loop substrate immediately, or preserving autonomy-credit accounting across context compression.

Decide what to do immediately after a git commit in the mew repo. Use when a commit just landed and you must choose whether to report to the user or continue working under a long-session output gate.

Save durable mew context before a long session, context compression risk, interruption, or major handoff. Use to write current intent, next action, validation state, blockers, active work-session notes, and durable product decisions into mew's own memory/state before continuing.

Adversarially review proposed mew self-improvement loops for product-goal drift, M5 safety boundaries, weak evidence, missing verification, hidden rescue edits, and whether the loop should be approved, rejected, or revised.