continue

Continue

Command Context

When to Reference DIP-0016

Always reference when:

• Resuming incomplete work from previous sessions
• Finding high-impact next actions
• Loading bootstrap context from continuation tasks
• Suggesting work based on system state

Key decisions this DIP informs:

• Bootstrap prompt retrieval from :continuation: tasks
• Session memory queries for context
• Task prioritization (impact vs effort)

Quick Reference

Question	Answer
When to run?	Start of session, or when looking for what to work on
Duration?	~1-2 minutes
Key output?	Loaded context, suggested next action
What DIPs govern this?	DIP-0016 (Session Memory), DIP-0009 (GTD)

Agents This Command Invokes

Integration Points

• DIP-0016 - Session memory retrieval
• DIP-0009 - Task scanning and prioritization
• /wrap-up - Creates continuation tasks this command consumes
• /today - Morning complement (broader scope)

---

Resume incomplete work or find the highest-impact next action.

CRITICAL: Task Access Pattern

ALWAYS use org-workspace for task operations. NEVER grep raw org files.

The GTD module's 11 MCP tools (listed in module.yaml) are NOT registered on any MCP server — they are phantom tools. Until they are wired into the datacore MCP server, access tasks via:

1. Python inline (preferred for structured queries):

   python3 -c "
   from org_workspace import OrgWorkspace, Query
   ws = OrgWorkspace()
   ws.load('/path/to/org/inbox.org')
   q = Query(ws)
   tasks = q.by_tag('continuation')  # or by_state, agenda, deadlines, etc.
   for t in tasks:
       print(f'[{t.todo}] {t.heading} scheduled={t.scheduled}')
   "
   

2. CLI adapter (for specific operations):

   python3 .datacore/lib/org_workspace_adapter.py list --file [path] --tags continuation --states TODO
   python3 .datacore/lib/org_workspace_adapter.py agenda --file [path] --days 7
   python3 .datacore/lib/org_workspace_adapter.py ensure-ids --file [path]