# /agenda Produce a prioritized overview of all open tasks with agent-assist inference. ## Behavior 1. **Read all task files** in `todo/`, `ongoing/`, and `blocked/` folders at `~/Workspace/Personal/Tasks/` 2. **Read all recurring definitions** in `meta/recurring/` 3. **Sort tasks:** - Priority: High > Medium > Low - Within same priority: overdue first, then soonest due date, then TBD last 4. **Infer agent-assistability** for each task based on description and context: - `Yes` -- task involves research, writing, analysis, code, document creation, data gathering - `Partial` -- task has agent-doable components mixed with human-only parts (meetings, decisions, calls) - `No` -- purely human tasks (meetings, calls, approvals, external dependencies with no prep work) 5. **Output the agenda** in the format below ## Output Format ``` ## High Priority | Task | Initiative | Due | Effort | Agent | |------|-----------|-----|--------|-------| | [task title] | [initiative] | [due or OVERDUE] | [effort] | [Yes/Partial/No] | ## Other Open Tasks | Task | Initiative | Due | Priority | Effort | Agent | |------|-----------|-----|----------|--------|-------| | [task title] | [initiative] | [due] | [priority] | [effort] | [Yes/Partial/No] | ## Blocked | Task | Initiative | Blocker | Agent | |------|-----------|---------|-------| | [task title] | [initiative] | [blocker summary from Notes] | [Yes/Partial/No] | ## Recurring | Task | Frequency | Next | Agent | |------|-----------|------|-------| | [task title] | [frequency] | [next occurrence] | [Yes/Partial/No] | ## Summary - X open tasks (Y high priority, Z overdue) - A in progress, B blocked - N tasks where agent can assist ``` ## Rules - **High Priority table** includes all tasks with Priority: High from `todo/` and `ongoing/` - **Other Open Tasks table** includes Medium and Low priority tasks from `todo/` and `ongoing/` - **Blocked table** shows all tasks in `blocked/` regardless of priority - Tasks in `ongoing/` show their folder status as context (mention "in progress" in the row or table header) - **Overdue detection:** if Due date is before today's date, mark as OVERDUE in the Due column - Do NOT read `done/` or `cancelled/` folders - Keep output concise -- no descriptions, just the table fields - If a task's due date is relative (e.g., "Before integration testing"), display it as-is