daily-task-manager

Daily Task Manager

Contract

This skill guarantees:

• Tasks stored as a brain page (ops/tasks.md) with structured format and a stable id per task
• Task lifecycle: add → in-progress → complete | defer | remove
• Priority levels: P0 (urgent), P1 (today), P2 (this week), P3 (backlog)
• Completed tasks archived with completion date; deferred tasks carry a target date + reason
• Mutations never drop unrelated tasks or unknown sections
• Every action returns the structured result below (Returns)

Returns

After every action, report a structured result so callers (including sub-agents) can chain reliably:

{action, task_id, status: ok|not_found|ambiguous|needs_confirmation, priority, date, page: "ops/tasks.md", saved: true|false}

For review, return the grouped active-task list instead of a single task_id. When invoked with the trigger "task list json", return a JSON array of task objects {id, description, priority, due, status} instead of markdown.

Tool Interface

Use ONLY the declared tools. get_page("ops/tasks.md") to read, put_page("ops/tasks.md", …) to write, add_timeline_entry for the audit trail, search for cross-referencing. Do not shell out to gbrain CLI verbs from this skill; the tools are the interface. (When the user runs this manually outside an agent, the CLI equivalents are gbrain get ops/tasks / gbrain put ops/tasks — equivalents only, not the skill's interface.)

Action Routing

Map user intent deterministically before touching state:

• "add / remind me to / put X on my list" → add
• "done with X / finished X / completed X / ✅ X" → complete
• "push X / defer X / move X to next week" → defer
• "delete X / remove X / kill task X" → remove (explicit delete words only — never infer remove)
• "what are my tasks / task list / what's on my plate (today)" → review ("today" filters to P0+P1)

Phases

1. Load. get_page("ops/tasks.md"). First run: if the page does not exist, create it from the Output Format template, then proceed.
2. Validate. Determine the action via Action Routing. If required fields are missing (see per-action rules), ask ONE concise clarification before mutating state. Never fabricate priorities, due dates, or defer reasons.
3. Identify the target task (complete/defer/remove): match by id when given; otherwise fuzzy-match description against ACTIVE tasks only. Zero matches → return not_found, do not mutate. Multiple matches → list candidates with IDs, return ambiguous, do not mutate.
4. Execute:
   • Add: Require a description. Priority: use the user's stated/clearly-implied level; otherwise default to P3 and say so in the reply + timeline entry. Due date only if supplied or explicit in the user's words. Mint a new task ID (t-YYYYMMDD-NN, NN = next free ordinal that day). Add a timeline entry.
   • Complete: Mark [x], move to Completed with (completed: YYYY-MM-DD).
   • Defer: Require a target date/timeframe AND a reason; ask if missing. Move to Deferred preserving original text, ID, and priority unless the user changes them.
   • Remove: Destructive — require explicit confirmation unless the user's message already contains it. Prefer suggesting complete or defer.
   • Review: Read-only. Never mutates. Active tasks grouped by priority, IDs shown.
5. Save. put_page("ops/tasks.md") after any mutation. Diff-mindset: touch only the affected lines; preserve all other content, including sections this skill doesn't recognize.