Time Estimation

Input Pattern	Estimate
"quick", "small", "minor"	`~15m`
"short", "simple"	`~30m`
"medium", "regular"	`~1h`
"large", "significant"	`~2h`
"big", "complex", "deep work"	`~4h`

Due Date Extraction

Input Pattern	Action
"today", "EOD"	Add to today.md
"tomorrow"	Add to today.md with note
"this week", "by Friday"	Add to backlog, Do First
"next week", "soon"	Add to backlog, Schedule
"someday", "eventually"	Add to someday.md

Project Detection

Look for explicit @project-name mentions
Infer from context: "for the API project" → @api
Work-related defaults to @work
Personal items get #personal tag

Tag Extraction

Common tags to apply:

#code - Programming tasks
#docs - Documentation
#meeting - Meetings and calls
#research - Research and learning
#bug - Bug fixes
#feature - New features
#review - Code/document reviews

Examples

Input: "Review John's PR for the auth feature, it's blocking the release" Output: - [ ] Review John's PR for auth feature @work #review #code !high ~30m

Input: "Eventually learn Kubernetes" Output: - [ ] Learn Kubernetes #learning !low ~4h → someday.md

Input: "Need to fix the login bug today" Output: - [ ] Fix login bug @work #bug !high ~1h → today.md

Processing Steps

Extract the core action (verb + object)
Detect priority from urgency words
Estimate time from complexity hints
Extract or infer project
Add relevant tags
Determine destination file
Format as markdown checkbox

Input Pattern	Priority
"urgent", "ASAP", "critical", "blocking"	`!high`
"important", "should", "need to"	`!medium`
"when possible", "eventually", "nice to have"	`!low`

task-parsing

Task Parsing

Task Format

Parsing Rules

Priority Detection

More from aviz85/claude-tasks

priority-matrix

time-estimation