---
name: task-management
title: "Task Management"
description: "Task lifecycle strategy — delegation, priority assessment, status tracking, completion criteria"
category: core
status: active
triggers:
  - "create task"
  - "delegate task"
  - "task status"
  - "update task"
  - "complete task"
---

## Instructions

Manage the full lifecycle of tasks from creation through completion and feedback.

### Task Lifecycle

1. **Create** — generate a task file in `vault/tasks/` with:
   - Title, brief (description), mode (review/auto), domain
   - Status starts as `pending`
   - Delegated timestamp

2. **Delegate** — assign to a subagent or keep for main agent:
   - Match task domain to agent expertise
   - Check agent's access tier allows required tools
   - Log delegation in dispatch_log

3. **Track** — monitor progress through statuses:
   - `pending` — created, not yet started
   - `in_progress` — actively being worked on
   - `blocked` — waiting on external input or dependency
   - `review` — completed, awaiting human review
   - `done` — approved and closed
   - `cancelled` — abandoned

4. **Review** — when status reaches `review`:
   - Present results to user
   - Collect feedback rating: good / needs_improvement / redo
   - Feed rating to trust service for the task's domain

5. **Complete** — mark as `done` with feedback recorded

### Priority Assessment

- **Urgent**: has a due date within 24 hours, or user explicitly says urgent
- **High**: due within 7 days, or blocks other tasks
- **Normal**: no time pressure, no dependencies
- **Low**: nice-to-have, no deadline

### Delegation Rules

- Tasks in domain where trust level is "Partner" can run in `auto` mode (no review needed)
- Tasks in domain where trust level is "Observer" require `review` mode
- Tasks touching sensitive data (finances, health) always require review regardless of trust
- Contract permissions are the ceiling — no task can exceed what the contract allows

## Rules

- Every task must have a domain for trust tracking
- Progress notes are appended, never overwritten
- Feedback is immutable once recorded
- Task files are markdown with YAML frontmatter
- Never delete task files — cancelled tasks stay for audit trail
