goalslot-goal-checkup

Goal checkup in GoalSlot

One goal, one honest answer, with the arithmetic shown.

Sequence

1. goalslot_get_context for today and timezone.
2. goalslot_list_goals to find the goal and its id.
3. goalslot_get_goal with includeReflections: true. The user's own past reflections on a goal usually explain the stall better than any report does.
4. goalslot_get_report with view: "detailed", goalIds: [id], preset: "last_30_days". The trailing actual rate.
5. goalslot_get_report with view: "schedule", preset: "last_30_days". Planned against logged for the blocks tied to this goal.

The arithmetic, shown

Write it out. Do not present a conclusion without the numbers under it.

target                40 h
logged                12 h
remaining             28 h
days to deadline      35  (2026-08-25 to 2026-09-29)
weeks remaining       5
required rate         5.6 h/week
actual rate (30d)     2.1 h/week
verdict               behind by roughly 2.7x

If the goal has no deadline, say so and use the trailing rate to project a finish date instead.

The diagnosis that matters

Two goals both at 10 percent of target look identical in a list and need opposite fixes. The schedule report is what tells them apart:

• No blocks tied to the goal at all. The user never allocated time. The fix is to allocate it. Hand off to planning the week.
• Blocks exist, adherence near zero. The time was allocated and did not happen. More blocks will not help and proposing them is the wrong answer. Ask what got in the way, and check the journal for those days.
• Blocks exist, adherence high, still behind. The allocation is honest but too small. The fix is more hours per week, a later deadline, or a smaller target. Say which.

End with a decision, not a summary

Offer the three real options and a recommendation:

1. Cut the target: goalslot_update_goal with a lower targetHours.
2. Move the deadline: goalslot_update_goal with a later deadline.
3. Add time: goalslot_manage_schedule_block to widen or add a block.