/gog-tasks

name: gog-tasks
description: Create, manage, and prioritize tasks and todo items. Convert emails to tasks, set priorities (P0-P3) and categories (Work/Personal/Errands/Admin), review daily priorities, track blocked and overdue tasks. Use when user mentions tasks, todos, action items, or wants to convert emails to tasks. Requires confirmation before creating or deleting tasks.
compatibility: Requires gog CLI tool with tasks access
metadata:
  author: gog-skills
  version: "1.0"
allowed-tools: Bash(gog:*) Read

Task Management & Prioritization

Create, organize, and track tasks with smart prioritization and daily review.

When to Use

Use this skill when:

• User mentions "create a task" or "add to my todo list"
• User wants to "convert this email to a task"
• User asks "what's on my task list" or "what should I do today"
• User mentions "task review" or "daily priorities"
• User wants to update or complete tasks

Dynamic Context

The following live data is available:

**Open tasks:**

!`TASKLIST_ID=$(gog tasks lists --json 2>/dev/null | jq -r '.tasklists[0].id' 2>/dev/null) && [ -n "$TASKLIST_ID" ] && gog tasks list "$TASKLIST_ID" --json 2>/dev/null || echo "GOG_NOT_CONFIGURED"`

**Important**: All task operations require a task list ID. Get it with:

TASKLIST_ID=$(gog tasks lists --json | jq -r '.tasklists[0].id')

Task Taxonomy

Priority Levels (P0-P3)

• **P0 (Critical)**: Drop everything, do now
• Blocking others' work
• System outages or emergencies
• Hard deadline within hours
• High-impact and high-urgency

• **P1 (High)**: Important, do soon
• Deadline within 1-3 days
• Stakeholder requests
• Significant impact if delayed
• Part of current sprint/focus

• **P2 (Medium)**: Normal priority
• Deadline within 1-2 weeks
• Routine work items
• Moderate impact
• Can be scheduled flexibly

• **P3 (Low)**: Nice to have
• No specific deadline
• Low impact if delayed
• Backlog items
• Ideas or improvements

Categories

• **Work**: Professional/job-related tasks
• Project work, meetings prep, emails, reports

• **Personal**: Personal life tasks
• Hobbies, self-care, family, learning

• **Errands**: Out-of-office tasks
• Shopping, appointments, calls, pickups

• **Admin**: Bureaucratic tasks
• Paperwork, taxes, bills, legal matters

Workflow

Creating Tasks

From Email

When user says "create a task for email [id]" or "turn this into a task":

1. **Fetch email if not in context**:

   gog gmail get <email_id> --json

2. **Extract task details**:

• Title: Email subject (may need shortening)
• Description: Key points from email body
• Priority: Infer from urgency (default: P2)
• Category: Infer from content (default: Work)
• Due date: Extract if mentioned, otherwise ask
• Related email ID: Store for reference

3. **Present proposed task**:

   ## Proposed Task

   **Title**: [Derived from email subject]
   **Description**: [Key points from email]
   **Priority**: [P0/P1/P2/P3] (rationale: [why])
   **Category**: [Work/Personal/Errands/Admin]
   **Due date**: [Date or "Not specified"]
   **Source**: Email from [sender] on [date]

   Does this look correct? Adjustments needed?

4. **Iterate** if user wants changes

5. **Request confirmation**: "Ready to create this task?"

6. **Create** when user confirms:

   # Get task list ID (first time or cache it)
   TASKLIST_ID=$(gog tasks lists --json | jq -r '.tasklists[0].id')

   # Create task
   gog tasks add "$TASKLIST_ID" \
     --title "Task title" \
     --notes "Task description" \
     --due 2026-02-05 \
     --json

**Note**: GOG CLI v0.9.0 task commands require a task list ID. Priority and category are tracked in the notes field or as custom metadata.

7. **Confirm creation**:

   ✅ **Task Created**

   Task ID: task_abc123
   Title: [title]
   Priority: [P1]
   Due: [date]

   View all tasks: "Show my tasks"

From Scratch

When user says "create a task to [X]":

1. **Gather details** by asking:

   Let me create that task. A few questions:

   1. **Title**: "[Suggested based on user input]" - is this good?
   2. **Priority**: P0 (critical), P1 (high), P2 (medium), or P3 (low)?
   3. **Category**: Work, Personal, Errands, or Admin?
   4. **Due date**: When does this need to be done?
   5. **Additional details**: Anything else to note?

2. **Accept shorthand answers**: e.g., "1: yes, 2: P1, 3: Work, 4: Friday"

3. **Present and confirm** before creating

Reviewing Tasks

Daily Task Review

When user says "task review" or "what should I do today":

1. **Fetch open tasks**:

   # Get task list ID
   TASKLIST_ID=$(gog tasks lists --json | jq -r '.tasklists[0].id')

   # List all tasks
   gog tasks list "$TASKLIST_ID" --json

2. **Analyze and categorize**:

• Today's priorities (P0/P1 tasks due soon)
• Overdue tasks
• Blocked tasks (if status indicates)
• Tasks waiting on others

3. **Present structured review**:

   # Daily Task Review — [Day], [Date]

   ## 🔥 Top 5 Tasks for Today

   1. **[Task Title]** (P0, due today)
      - Category: Work
      - Details: [Brief description]
      - Task ID: task_abc123

   2. [...]

   ## ⚠️  Overdue Tasks ([N] total)

   - **[Task Title]** (P1, due [date])
     - [Why it's overdue context]
     - Task ID: task_def456

   ## 🚧 Blocked / Waiting on Others ([N] total)

   - **[Task Title]** (P2)
     - Blocked by: [What/who]
     - Task ID: task_ghi789

   ## 📅 This Week (Non-urgent)

   [List of P2/P3 tasks due this week]

   ---

   **Suggested Focus**:
   1. Start with: [Task title] (highest priority)
   2. Then tackle: [Task title]
   3. If blocked, move to: [Task title]

   **Actions**:
   - To complete a task: "Mark task_abc123 as done"
   - To update priority: "Change task_def456 to P0"
   - To see task details: "Show task task_ghi789"