recalllisted

# 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.** Use for "recall my work on X", "catch me up", "what have I been working on", or "where did I leave off". Keep it tight and on-topic. Read only what the in-scope threads need, then stop. The heavy reading fans out to parallel subagents. The main thread keeps only their findings and the final brief. 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. Use the active host's thread history, transcript API, or current-session context. Do not guess private filesystem paths or scan unrelated projects. If the host exposes no prior history, reconstruct from the repository and the context the user supplied. 1. Classify, then route. One specific prior chat to resume is the `session-pickup` playbook, not this. A human-readable summary of your work is a different task. Recall loads working context across recent chats bef