Task Lifecycle¶

Source: hooks/ways/ea/tasks/tasks.md

Frontmatter

Field	Value
`description`	the human's personal to-dos and obligations in their task manager app, due dates and reminders, marking items done, clearing stale ones
`vocabulary`	`to-do todos personal obligation errand chore commitment due date deadline overdue reminder nag done mark complete stale google tasks todoist things omnifocus eisenhower urgent important`
`refire`	`0.15`
`scope`	`agent, subagent`

Personal task management as the persistence layer closest to the user's brain. Tasks track obligations, deadlines, and commitments across all contexts.

Core Rule: Suggest, Never Auto-Execute¶

Every task mutation must be suggested and approved. Present the proposal, wait for confirmation, then execute.

Suggesting Task Creation¶

When any workflow surfaces a new obligation:

Suggested task: "Follow up with [person] on [topic]"
  Priority: medium
  Due: YYYY-MM-DD
  Source: email / meeting / chat / phone
  Client: [if applicable]
  Project: [if applicable]
Create this task?

Always populate: title (verb + object), source type and reference (creates traceability), priority (infer from urgency cues), due date (from content — don't fabricate if none mentioned).

For multiple items, present as a numbered list and offer bulk creation on approval.

Suggesting Task Updates¶

When intelligence indicates properties should change:

Suggested update to "[task title]":
  Priority: medium → high (meeting is tomorrow)
  Due: none → YYYY-MM-DD
Update this task?

Triggers: email sets/changes a deadline, meeting moves up, blocked task becomes unblocked, user starts working on something.

Suggesting Task Completion¶

When intelligence indicates a task is done:

Looks resolved: "[task title]"
  Evidence: [what indicates completion — sent email, meeting passed, explicit confirmation]
Mark as complete?

Signals: user sent a fulfilling email, tied calendar event has passed, user explicitly says "that's done."

Suggesting Task Cleanup¶

During briefings and reviews, identify stale tasks:

Possibly stale (no activity in 14+ days):
  "[task title]" — created [date], no related activity since
Archive, reschedule, or keep?

Triggers: no due date + 14 days old + no related activity. Due date 7+ days past with no updates. References a project with no recent activity.

Cross-Reference Pattern¶

Every intelligence-gathering workflow should cross-reference with tasks: - What emails relate to open tasks? - What tasks relate to upcoming meetings? - What's been resolved but not marked complete? - What new obligations aren't yet tracked?