56 lines
1.4 KiB
Markdown
56 lines
1.4 KiB
Markdown
---
|
|
name: task-capture-and-followup
|
|
description: Capture requests as structured tasks, track status over time, and send low-noise follow-ups for due/overdue/blocked items. Use when users ask to remember tasks, convert chat asks into todos, track commitments, or request reminders/check-ins.
|
|
---
|
|
|
|
# Task Capture and Follow-up
|
|
|
|
## Storage policy
|
|
|
|
- Keep active state in `memory/tasks.json`.
|
|
- Append notable updates to daily note `memory/YYYY-MM-DD.md` when useful for continuity.
|
|
- Never store secrets unless user explicitly asks.
|
|
|
|
## Task schema
|
|
|
|
Required fields:
|
|
- `id`
|
|
- `created_at`
|
|
- `title`
|
|
- `owner`
|
|
- `priority` (`low|med|high`)
|
|
- `status` (`open|in-progress|blocked|done`)
|
|
|
|
Optional fields:
|
|
- `details`
|
|
- `due_at`
|
|
- `next_check_at`
|
|
- `notes`
|
|
|
|
## Capture workflow
|
|
|
|
1. Detect action-oriented request.
|
|
2. Infer missing fields conservatively.
|
|
3. Ask only for critical missing info (typically due date or priority).
|
|
4. Persist task.
|
|
5. Return compact confirmation with id + next check moment.
|
|
|
|
## Follow-up policy
|
|
|
|
Nudge only when high signal:
|
|
- due within 24h,
|
|
- overdue,
|
|
- blocked,
|
|
- or explicit user-requested reminder window.
|
|
|
|
Anti-spam:
|
|
- no repeated nudge inside a short window,
|
|
- batch multiple items in one update,
|
|
- suppress low-importance repeats.
|
|
|
|
## Completion policy
|
|
|
|
- Mark done only on explicit user confirmation.
|
|
- Preserve short completion note for future context.
|
|
- Keep historical records unless user asks to prune.
|