// Weekly self-audit playback. Surface patterns from the user's past week that they probably cannot see themselves.
| name | mirror |
| x-phantom-source | built-in |
| description | Weekly self-audit playback. Surface patterns from the user's past week that they probably cannot see themselves. |
| when_to_use | Use when the user says "mirror", "weekly review", "show me my week", "what did I actually do this week", "reflect on last week", "how did my week go", or any similar reflective request. Also fires automatically on a Friday evening schedule if the user has enabled the mirror ritual. |
| allowed-tools | ["mcp__phantom-reflective__phantom_memory_search","mcp__phantom-reflective__phantom_list_sessions","Read"] |
| context | inline |
Play back the last seven days to the user from memory. Not a task report. Not a highlight reel. A reflection that surfaces what the user could not see themselves: patterns, postponements, commitments made and broken, hours worked outside stated bounds, topics that consumed disproportionate mental energy, interpersonal frictions that recurred, decisions made without clear rationale.
The goal is honest, warm observation. Never moralize. Never prescribe. Offer what you saw and let the user decide what it means.
Call mcp__phantom-reflective__phantom_memory_search with days_back: 7, memory_type: "all", and a broad query like "this week" or the user's name. Return at least 20 episodes and 10 facts if available.
Success criteria: you have a list of episodes and facts from the last seven days. If the memory system is degraded and returns empty, tell the user honestly and stop.
Call mcp__phantom-reflective__phantom_list_sessions with days_back: 7, limit: 50. Note which channels were active, how many turns each conversation ran, and where cost clustered.
Success criteria: you can reference specific sessions by channel and day when you describe a pattern.
Read the episodes and facts for:
Success criteria: you have identified between three and five patterns that you can cite to specific memory episodes.
Write the response in three clearly labeled sections:
What I noticed. Three to five observations, each cited to memory references. Warm and direct. No moralizing. Example: "You brought up the pricing decision in four separate conversations across three channels this week. Each time you were the one who raised it. It seems to still be weighing on you."
What I am unsure about. One or two things you observed but cannot interpret without more context. This is honest humility, not filler. Example: "I noticed you declined two calls on Tuesday morning that you had previously accepted. I cannot tell from memory whether that was intentional re-prioritization or calendar drift."
One question for you. A single reflective prompt the user can take or leave. It should be specific to what you saw, not a generic coaching prompt. Example: "Is the pricing decision something you want to close this week, or is it a standing open question you are comfortable holding?"
Success criteria: under 500 words total, every observation anchored to a real memory episode, the closing question is specific and honest.
List the agent's current skills, memory files, plugins, subagents, hooks, and a settings summary plus dashboard URLs. The user-facing discovery path for everything the operator can edit.
List the Claude Code plugins currently enabled for the agent, read straight from settings.json.
Before answering a substantive question, quietly check whether the user has already resolved this question in the past.
Find commitments the user made in the last two weeks and did not follow through on. A promises audit.
Discover recurring behaviors from memory and offer to formalize them as scheduled jobs.
Show how the user's thinking on a specific topic has evolved over time. A chronological narrative with turning-point callouts.
