Task

If the intent is ambiguous, infer the most likely action and proceed. Only ask if genuinely unclear.

Task System Reference

Storage

• Active task files: Tasks/T-NNN - Title.md (one file per task — only active tasks: inbox, backlog, in-progress, blocked)
• Archived tasks: Tasks/Archive/YYYY/MM-Month/T-NNN - Title.md (done/cancelled tasks, filed by completion/cancellation date)
• Counter: Tasks/_counter.md (frontmatter next_id field)
• Dashboard: Dashboard/Tasks.md (generated, not manually edited)

Statuses

inbox ↔ backlog → in-progress → done
                ↘ blocked (needs reason)
          any state → inbox (deprioritized/delayed)
          any state → cancelled (needs reason)

Fields

Template

See templates/task-note.md for the file structure.

Workflows

Create Task

1. Read Tasks/_counter.md → get next_id
2. Format ID: T- + zero-padded to 3 digits (e.g., T-001, T-012)
3. Create file Tasks/T-NNN - [Title].md using template:
   • Fill frontmatter: id, status=inbox, owner=[YOUR NAME], created=today
   • Fill any fields the user provided (deadline, priority, source, type)
   • Title as # heading
   • Description if provided (otherwise leave empty)
   • Changelog: - YYYY-MM-DD — Created (add source info if applicable)
4. Increment next_id in Tasks/_counter.md
5. Regenerate Dashboard/Tasks.md
6. Report: ✅ Created [[T-NNN - Title]] (inbox)

Minimal creation: Only a name is required. Everything else optional.

Batch creation: For multiple tasks, create all files, increment counter once at the end, regenerate dashboard once.

Update Status

1. Read the task file
2. Validate the transition:
   • blocked and cancelled require a reason (ask if not provided)
   • Moving to inbox from any state is always valid (deprioritization)
   • done can come from any active state
3. Update frontmatter status
4. Append to changelog: - YYYY-MM-DD — Status: [old] → [new] (include reason for blocked/cancelled)
5. If new status is done or cancelled: archive the task file:
   • Determine archive path: Tasks/Archive/YYYY/MM-Month/ based on today's date (the completion/cancellation date)
   • Create the archive folder if it doesn't exist
   • Move the task file from Tasks/ to the archive folder
6. If new status is done: update today's daily journal (see Daily Journal Updates below):
   • Strike through matching focus item
   • Append task to "Today I finished" section
7. Regenerate Dashboard/Tasks.md
8. Report: ✅ T-NNN: [old] → [new] (add (archived) if moved)

Update Fields

1. Read the task file
2. Update the specified frontmatter field(s)
3. Append to changelog: - YYYY-MM-DD — [Field]: [old] → [new]
4. Regenerate dashboard if priority changed (affects ordering)
5. Report: ✅ T-NNN: [field] updated

Add Comment

1. Read the task file
2. Append to changelog: - YYYY-MM-DD — [Comment text]
3. No dashboard regeneration needed
4. Report: ✅ Comment added to T-NNN

Query Single

1. Read the task file (check Tasks/ first, then Tasks/Archive/ if not found)
2. Display: title, status, priority, owner, deadline, source, type, last 3 changelog entries
3. If user wants full changelog, show all entries

Query List

1. Read active task files in Tasks/ (top-level only, skip _counter.md and Archive/)
2. Filter by the requested criteria (status, priority, owner, etc.)
3. If user explicitly asks for done/cancelled/archived/history tasks, also read Tasks/Archive/ recursively
4. Display as a compact list:

   📋 [Status] tasks (N):
   - [[T-001 - Title]] (P2, due Mar 15) — last: [latest changelog entry]
   - [[T-003 - Title]] (P1) — last: [latest changelog entry]
   

Dashboard Regeneration

When regenerating Dashboard/Tasks.md:

1. Read active task files in Tasks/ (top-level only, skip _counter.md and Archive/)
2. Group by status: in-progress, backlog, inbox, blocked
3. Within each group, sort by: deadline (earliest first, tasks with no deadline at bottom), then task ID (ascending) for tasks with the same or no deadline
4. Skip done and cancelled tasks — they're not shown on the dashboard
5. Write the dashboard with this structure:

---