28 lines
1006 B
Markdown
28 lines
1006 B
Markdown
# Feature Plan: Task Automation from Chat
|
|
|
|
## Goal
|
|
Strengthen chat-to-task conversion with due dates, assignees, and conversation links.
|
|
|
|
## Why This Fits GIA
|
|
- Task extraction and command flows already exist and are active.
|
|
|
|
## Scope
|
|
- Parse due date/owner hints from task-like messages.
|
|
- Persist task-to-message and task-to-session links explicitly.
|
|
- Improve task status announcements and query commands.
|
|
|
|
## Implementation
|
|
1. Extend task parser with lightweight date/owner extraction rules.
|
|
2. Add fields (or payload keys) for due date and assignee identifier.
|
|
3. Add `.task list`, `.task show #id`, `.task complete #id` command aliases.
|
|
4. Add per-chat task digest message schedule option.
|
|
5. Add robust undo/audit entry for automated task creation.
|
|
|
|
## Acceptance Criteria
|
|
- Task extraction preserves source message context.
|
|
- Due date extraction is deterministic and tested for common phrases.
|
|
- Command UX remains lenient and case-insensitive.
|
|
|
|
## Out of Scope
|
|
- Full project management board UX.
|