opentasks-recall

OpenTasks Recall

Use this skill for context loading and previous-session recall. This is separate from task lifecycle writes, memory writes, repository index maintenance, and repo-map maintenance.

When To Use

Use this skill when the user asks:

• what tasks are active
• what happened recently
• what was done before
• where a task left off
• for handoff/status
• to continue from previous context
• to search prior OpenTasks sessions

Workflow

1. Load current task and memory context:

opentasks context

2. If previous session archive may matter, inspect recent archived sessions:

opentasks recall

3. If the CLI is unavailable, read:

info-for-agent/tasks.md
info-for-agent/memories.md
info-for-agent/repo-index.md
info-for-agent/repo-map.md

4. If repository location matters, route that part to opentasks-repo-index before asking the user. If durable repo relationships matter, route that part to opentasks-repo-map.
5. Summarize evidence-backed context to the user. Preserve task IDs and task directories when reporting status.

Safety

• Do not invent session history.
• Distinguish current task table state from archived session hints.
• If recall has no archived sessions, say that and fall back to tasks.md / memories.md / repo-index.md / repo-map.md.
• Do not modify task, memory, repo-index, or repo-map files from this skill.
• Do not prune, archive, or checkpoint from this skill.
• Route lifecycle writes to opentasks-task-lifecycle, durable memories to opentasks-memory, repository index changes to opentasks-repo-index, and durable repo relationships to opentasks-repo-map.
• Session archive is a recall aid, not durable memory. Summarize durable lessons into opentasks-memory only when appropriate.