--- 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 starting or resuming work, rebuild the user's recent working context and return a tight capsule of current state and next action. 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](../why/SKILL.md) 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 [host capabilities](../../references/host-capabilities.md), [model roles](../../references/model-roles.md), [orchestration contract](../../references/orchestration-contract.md), and [workflow ownership](../../references/workflow-ownership.md) before retrieving history or assigning investigators. Invocation metadata is retained without assuming host enforcement. Discover authorized history reads through exposed tools or an explicitly supplied local transcript location. Observe actual reads and declare missing history coverage. Do not assume a host transcript directory, enumerate unrelated projects, or treat configured history access as successful retrieval. Preserve each chat UUID when available; if the host uses another stable record identifier, cite it and disclose that UUIDs are unavailable. For local transcripts, inspect the documented format before parsing. Keep private raw content within authorized investigators. 1. Classify, then route. One specific prior chat to resume is the [`session-pickup` playbook](../poteto-mode/playbooks/session-pickup.md), not this. Turning habits into a durable skill is [`automate-me`](../automate-me/SKILL.md). 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 with paths, branch, and the change, use it and skip history mining. Check its completeness; a partial capsule only replaces the covered history. This shortcut does not skip the named-target shared-record sweep or independent live-state verification. 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. When exposed and authorized, spawn independent parallel investigators, each taking a slice of the corpus. Prefer a fast, inexpensive supported model under the model-role contract. Retain inherited selection when enumeration is absent, record requested and actual models separately, and disclose rejection or fallback. Tell every subagent to order candidates by real modification time, using `ls -t` for local files or observed host timestamps, and never by UUID name, grep the topic first and then read only the matching chats and only their relevant regions, and skip the current chat plus obvious noise (subagent, eval, and test chats). Each returns the same schema, one block per chat: topic, the user's goal, decisions, open threads, struggles and corrections, and artifacts (PRs, tickets, branches), each citing the chat UUID. 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. Use immutable assignments with exact revisions, distinct owned outputs, and result inspection under the orchestration contract. If independent workers are unavailable, perform authorized sequential slices and label reduced capability. Missing history access blocks the affected history reconstruction; never invent retrieved chats. 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](../why/SKILL.md)'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 source and say so. Keep unavailable, denied, failed, and searched-empty results distinct. Preserve why's evidence-category coverage and citation checks. If workers are unavailable, use separately scoped authorized sequential source passes and disclose reduced capability. 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 independently using authorized available `git`, `gh`, or exposed source-control and ticket read tools. Verify file and branch state from the active workspace, including capsule-provided artifacts. Missing execution, repository, PR, or ticket access blocks the affected current-state conclusion. Historical or supplied state is not live verification. 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 ]`, `[verified, uncommitted]`, `[reverted #N]`, or `[planned, not started]`. A thread with no tag is not done yet, so tag it. Use a tag only when evidence supports it. For an unresolved status, report the gap without fabricating completion; the affected thread-status contract remains blocked. - **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](../unslop/SKILL.md), 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.