Google Tasks Prioritize

Google Tasks Prioritize

Rank active Google Tasks by Eisenhower group (1 → 2 → 3), then by recent Gmail traffic on each topic.

Prerequisites

1. gws CLI installed and authenticated:

   gws auth status
   

2. If auth fails, run gws auth login (requires tasks and gmail scopes).
3. Read TEAM.md at the project root (if present) for team mission, programs, and current priorities.

Workflow

1. Read TEAM.md at the project root if it exists — who the team is, what we do, and current focus areas (use this to interpret and rank task importance beyond Eisenhower group and email traffic).
2. Run the prioritization script from the project root:

   python3 ~/.cursor/skills/google-tasks-prioritize/scripts/prioritize_tasks.py
   

   Optional flags:
   • --days 14 — email lookback window (default: 14)
   • --format markdown|json — output format (default: markdown)
   • --dry-run — fetch tasks only, skip Gmail scoring
3. Present the report to the user using the template below.
4. Add team context — in the Summary (or a short Team alignment note), call out when top tasks map to priorities in TEAM.md (if present). Do not invent alignment; only note clear matches.
5. If the script fails, follow the manual fallback in reference.md.

Output template

# Prioritized Tasks — {date}

## Summary
- {count} active tasks across groups 1/2/3
- Top focus: {top 3 task titles}
- Team alignment: {how top tasks relate to TEAM.md priorities, if applicable}

## Group 1 — Urgent and Important
| Rank | Task | Due | Email (14d) | Sources |
...

## Group 2 — Not Urgent / Important
...

## Group 3 — Urgent / Not Important
...

Within each group, tasks are ranked by email traffic score (desc), then due date (asc, overdue first), then title.

Scoring (summary)

• Group 1 = "1 Urgent and Important (DO!!)"
• Group 2 = "2 Not Urgent / Important (Consider)"
• Group 3 = "3 Urgent / Not Important (Delegate)"

Email score uses linked Gmail threads first (from links and notes), then falls back to a title search with newer_than:14d. See reference.md for details.

Additional resources

• TEAM.md at project root — team org, programs, and priorities (if present)
• reference.md — gws commands, URL parsing, scoring rules