---
name: recall
description: "Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work."
disable-model-invocation: true
---

# Recall

**Before you start or resume work, you rebuild the user's recent working context and hand back a tight capsule of where things stand now and what to do next.**

Keep it tight and on-topic. Read only what the in-scope threads need, then stop.

Your context lives in two records. Your own chat history holds what you did and decided. The shared record holds everything that happened around the same code under other names: the symptoms users keep reporting, the fixes that shipped and got reverted, the errors still firing in prod. That second record is what the **why** skill searches, across source control, the issue tracker, chat and issue channels, long-form docs, and error tracking. A feature with a long bug tail keeps most of its story there, so don't reconstruct it from your transcripts alone.

Read [Codex execution](../poteto-mode/references/codex-execution.md) before dispatching subagents. For history, resolve `scripts/codex-history.mjs` from this skill's installed directory, then run `node "<absolute-helper>" list --project "<active-project>" --since "<window-start>"`. It scopes Codex rollouts by `session_meta.cwd`, including this repository's current worktrees and archived sessions. Each UUID selects its current rollout; superseded files remain available for inherited prefixes. Results use the selected rollout's modification time. Use `--query "<topic>"` to search that same reconstructed conversation, including older inherited content, and `read --project "<active-project>" --id <uuid>` for its full JSONL. A JSONL line is a metadata, message, tool, or event record, not always a chat message. If a required prefix is missing, use the host's full thread-history API instead of claiming a complete transcript.

Include existing Claude runner evidence by repeating `--claude-runs "<absolute-known-run-directory-or-root>"` on the list command. Find those locations in task artifacts and the project's existing `.local/` run directories; the runner has no universal run root. Only supplied roots inside the project or its worktrees are searched, and `request.json.cwd` must also match that scope before result or transcript content is read. `--query` searches the prompt, raw stdout, and receipt. Results identify the executor, session UUID, exact receipt path, cwd, time, and raw artifact paths. Read an exact run with `read --project "<active-project>" --source claude-code --claude-runs "<known-root>" --receipt "<exact-result.json>"`, then open its returned `requestPath`, `promptPath`, `stdoutPath`, and `stderrPath` as needed. Read the raw stream when reconstructing attempts, failures, or tool use; the final result alone can omit them. Resumed runs retain distinct receipt paths even when their session UUID matches. Keep the executor and receipt path with each finding. Scope metadata before topic searches; do not scan Codex or Claude home directories for unrelated transcript bodies.

1. Classify, then route. One specific prior chat to resume is the `session-pickup` playbook, not this. Turning habits into a durable skill is `automate-me`. A human-readable summary of your work is a different task. Recall loads working context across recent chats before you act. If the user already gave you a full state capsule (paths, branch, the change), use it and skip the mining.
2. Lock the scope before searching. Pin the window ("recent" is a real range, default the last 7 days), the topic if named, and the workspace (default the active one. Never read another project's transcripts without being asked). State the scope back. Never quietly turn "all" into "recent N".
3. Fan out across your chat history. Resolve the existing `swarm workers` role through the setup helper's `models.mjs resolve --role "swarm workers"` command per **Codex execution**, then launch parallel general-purpose miners through Codex execution on that saved entry (default `gpt-6.1-sol`), selecting `agent_type: "pstack-general-purpose"` on the native path, each taking a slice of the corpus. Give miners the scoped Codex UUIDs and exact Claude receipt paths with their run roots. Order candidates by returned activity time, query the topic first, then read the matching chats or raw runner evidence and their relevant regions. Skip the current chat plus obvious noise (subagent, eval, and test chats). Each returns the same schema, one block per chat or run: topic, the user's goal, decisions, open threads, struggles and corrections, and artifacts (PRs, tickets, branches), citing the executor and chat UUID or exact receipt path. For one or two chats, skip the fan-out and search directly. The raw transcripts stay in the subagents. The main thread gets only their findings. Pick each subagent's reasoning level and fast or standard speed for the job, per the Subagents section of the **poteto-mode** skill.
4. Sweep the shared record whenever the topic names a feature, file, subsystem, area, or bug. This is the default, not a judgment call, and "my work on X" does not exempt it. Hand it to the **why** skill's source investigators, but steer their question from "why was this built this way" to "what's the current state, what's been tried and didn't hold, and what are users still reporting". Reuse its per-source playbooks, run the investigators in parallel with the chat-history mining, and inherit its posture: one investigator per source, null results are findings, skip an unavailable MCP and say so. Fold what comes back into the brief. Skip this step only for pure activity recall with no named target ("what did I do this week"), where your own history and live state are the entire answer.
5. Verify against live state. Take the PRs, branches, and tickets that the mining and the sweep surfaced and check them with `git` and `gh`. When the answer hinges on what an agent actually did (the tools it ran, files it read, errors it hit), read the full transcript, not just a trimmed local copy.
6. Write the brief to the contract below. Group by thread. Stay on the named topic.

## Output contract

Lead with the capsule, then the thread status, then the problems, then the next move. Deeper detail goes below or gets cut.

- **Capsule.** At most 5 bullets. What this work is and where it stands overall.
- **Threads.** One line each, prefixed with exactly one status tag: `[merged #N]`, `[open PR #N]`, `[in flight <branch>]`, `[verified, uncommitted]`, `[reverted #N]`, or `[planned, not started]`. A thread with no tag is not done yet, so tag it.
- **Problems.** At most 5, the recurring ones. Include the symptoms users keep reporting and any fix that shipped and was reverted, so the next attempt starts where the last one failed.
- **Next move.** The single most useful next action, concrete.

An adjacent feature or ticket stays out unless it blocks this one. When the capsule and thread lines outgrow a screen, cut detail before you cut threads. Write the brief through the **unslop** skill, cite chat findings by UUID and shared-record findings by their source (PR #, ticket ID, chat permalink, error-tracker issue), and sanitize private context before any public output.

**Reply:** the brief, to the contract above.