recall
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.
来源信息
- 仓库
- enekesabel/dev-flow
- 最近来源活动
- 2026年10月19日 12:47
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 2
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- 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.
在 GitHub 查看