Use when you are the DevFlow Coordinator and the Ledger is missing or incomplete in your context: after compaction, on resuming a conversation, or when it feels thin. Otherwise use only when explicitly told to.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Recall?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/enekesabel-recall)
---
name: recall
description: "Use when you are the DevFlow Coordinator and the Ledger is missing or incomplete in your context: after compaction, on resuming a conversation, or when it feels thin. Otherwise use only when explicitly told to."
---
# Recall
The Ledger schema and all definitions are in the [Coordinator's agent definition](../../agents/devflow.md).
## Procedure
1. **Assess.** Check whether a Ledger block exists in your current context. Note what is present and what is missing.
2. **Find sources.** Scan for readable conversation history: prior turns in context, transcript files on disk, agent transcript files, prior compaction summaries.
3. **Extract.** From each source, identify Attention Surfaces and Proposals. Classify using the tells and statuses defined in the [Coordinator](../../agents/devflow.md). Preserve each Proposal's Content at its established Specificity.
4. **Reconstruct.** Build the Ledger block in the [sentinel format](../../agents/devflow.md#the-ledger). Preserve prior IDs where they exist.
5. **Report.** One or two sentences: what you recovered and any specific gap.
## Hard rules
- Never invent a Proposal you cannot substantiate from the sources you read.
- An empty recovery stated plainly is correct. A plausible reconstruction is not.
- Ambiguous status defaults to Open.
