gtd-next

Automatically select the next actionable tasks and generate a time-blocked agenda based on calendar context and task priority. The agent decides — no user interaction required.

CLI Tool

Run Swift source directly (no build step required):

swift ${CLAUDE_PLUGIN_ROOT}/scripts/productivity-cli.swift <command>

Step 1: Check Calendar

1. Get current date and time:

   date "+%Y-%m-%d %H:%M"
   

2. Query today's remaining events:

   swift ${CLAUDE_PLUGIN_ROOT}/scripts/productivity-cli.swift calendars today
   

3. Parse the JSON response and find the next event (after current time). Skip all-day events.

4. If a next event exists, calculate available minutes until it starts. This becomes the time constraint. If no events remain today, there is no time constraint — proceed without one.

Step 2: Query All Actionable Tasks

1. Query actions from all context lists:

   swift ${CLAUDE_PLUGIN_ROOT}/scripts/productivity-cli.swift reminders incomplete "@quick"
   swift ${CLAUDE_PLUGIN_ROOT}/scripts/productivity-cli.swift reminders incomplete "@1pomo"
   swift ${CLAUDE_PLUGIN_ROOT}/scripts/productivity-cli.swift reminders incomplete "@2pomo"
   swift ${CLAUDE_PLUGIN_ROOT}/scripts/productivity-cli.swift reminders incomplete "@deep"
   

2. Query overdue reminders:

   swift ${CLAUDE_PLUGIN_ROOT}/scripts/productivity-cli.swift reminders overdue
   

3. Parse and combine results, noting for each action:

   • Context list (@quick, @1pomo, @2pomo, @deep)
   • Project reference from notes field (#{ProjectName})
   • Priority value
   • Due date
   • Whether overdue

If no actionable tasks found, report "No actionable tasks found. Add tasks to @quick, @1pomo, @2pomo, or @deep lists." and exit.

Step 3: Rank and Select Tasks

Rank all tasks by priority order:

1. Overdue items first
2. High priority (priority=1)
3. Due date approaching (soonest first)
4. Medium priority (priority=5)
5. Remaining items

If there is a time constraint (next event found in Step 1):

Select tasks from the top of the ranked list that fit within the available time. Use task durations based on context (@quick=15min, @1pomo=25min, @2pomo=50min, @deep=90min). Account for buffer time and pomodoro breaks when calculating fit. Skip tasks that exceed remaining time and try the next one.

If there is no time constraint:

Select the top 10 actionable tasks from the ranked list.

Step 4: Generate Agenda

If there is a time constraint:

1. Calculate buffer time before next event:

   • Buffer = available_minutes / 6 (roughly 10 min per hour)
   • Round to nearest 5 minutes
   • Minimum 5 minutes, maximum 20 minutes

2. Usable work time = Available time - Buffer time

3. Arrange selected tasks into pomodoro blocks:

   • Each pomodoro = 25 min work + 5 min break
   • Multiple short tasks within 25 min: group without breaks
   • After each 25 min of work, schedule a 5 min break
   • No break needed before the final buffer
   • Longer tasks (@2pomo, @deep): treat as single focused blocks, break after completing

4. Present a time-blocked agenda:

## Your Agenda (until [Event] at [Time])

[Start Time] - [End Time]  [Task A] (@quick) #[ProjectName]
[Start Time] - [End Time]  [Task B] (@1pomo)
[Start Time] - [End Time]  Break
[Start Time] - [End Time]  [Task C] (@2pomo) #[ProjectName]
[Start Time] - [End Time]  Buffer before [Event]

If there is no time constraint:

Present the top 10 tasks as a ranked recommendation list:

## Recommended Next Tasks

1. ⚠️ [Action Title] #[ProjectName] [High] @quick (~15 min) - OVERDUE
2. [Action Title] #[ProjectName] [High] @1pomo (~25 min) - due [date]
3. [Action Title] [Medium] @2pomo (~50 min)
...
10. [Action Title] @1pomo (~25 min)

Total estimated time: ~X hours Y min

Display formatting:

• ⚠️ prefix for overdue items
• Show project name if linked (from notes field)
• Map priority values: 1=[High], 5=[Medium], 9=[Low], 0=omit
• Show context list: @quick, @1pomo, @2pomo, @deep
• Show estimated duration based on context
• Show due date if set, with "OVERDUE" if past

Guidelines

• Prioritize overdue items — they always appear first
• Link actions to projects when #{ProjectName} is found in notes
• Show all matching actions even if multiple belong to the same project
• Handle CLI errors gracefully and report to user
• The agent decides what to work on — present the result, do not ask for selection