Aimgod

Add one focus point to the Focus section when the user asks, optionally to a Focus sphere and starred. It joins the end of the list, or the top when the user chose New first. Keep it short, in the user's words.

Add one goal to the month, quarter or year that contains date (today when omitted), optionally with subgoals, a star and the goals it comes after. Horizon defaults to month. For a whole path to a bigger goal, build_goal_flow fits instead.

Create a sphere (life area) when the user asks for a new area, in one or more sections: planning for tasks, goals for the Goals canvas, focus for Focus points, visualisations. Planning by default. If a sphere with this name is already in those sections, it is returned instead of a twin. The free plan keeps 3 Planning spheres; Goals and Focus spheres are free.

Add a subtask (checklist item) under a task when the user asks to break a task into steps or list items under it (a link in the title opens as a link in the app). Works on the user's own tasks and on tasks of a shared sphere where the user is responsible; not on tasks the user only ticks (shared.my_role member or viewer). Add one subtask per call.

Add one task to a day when the user asks to add or plan something. Without date it goes to today; without time it joins the untimed list. remind_minutes_before sets a reminder (the task needs a time). repeat makes it a repeating task (a habit): one call, Aimgod puts it on the following days itself, so do not add copies to several dates. sphere may be a shared sphere where the user is responsible (shared.my_role in list_spheres): the task goes to the whole sphere as its owner's, without starred, reminder or repeat; members and viewers cannot add there. If two spheres share a name, pass the id: a name picks the user's own.

Archive a sphere: it leaves every section, past tasks and goals keep it. Only when the user clearly asks to remove it.

Create a bigger goal and the path to it in one step, on the Goals canvas of a month, quarter or year (month and today when omitted). A good flow: exactly one final goal (final: true, the result, no subgoals) that nothing comes after; 3 to 6 measurable milestones before it ("Send 20 proposals", not "Work harder"), each with 2 to 4 concrete subgoals; parallel branches add up to the final goal. after lists what comes first. Cards are placed left to right. Max 14 goals. A year chain (horizon year): a month goal per month (own horizon and date, up to 3 subgoals), linked earlier month first, the year goal last; a month may rest.

Move the open goals of the previous month, quarter or year into the current one, with their open subgoals, when the user asks. The old ones stay in the archive, marked as moved.

Delete a focus point for good. Only when the user clearly asks to delete it.

Delete a goal for good, with its subgoals and arrows. Only when the user clearly asks to delete it.

Delete a goal's subgoal for good. Only when the user clearly asks to delete it.

Delete a task for good. Only when the user clearly asks to delete it.

Mark the work on a task handed to an agent as finished and ready for the user's review, with a link to the result (https) and a short note of what was done; the note shows in the task's AI chat. A note alone also fits for asking the user a question or proposing a plan. Tick the subtasks you did with update_subtask first. Never mark the task itself done: the user does that after reviewing.

The tasks the user handed to an AI agent in Aimgod (Claude switched on in the task window) that are not done: each with its description, subtasks, the user's new notes for the agent and thread (the last notes between you and the user, yours too). Fits when the user asks to take their Aimgod work, or a scheduled Aimgod worker run starts. Do the work with your own tools; Aimgod only shows its state.

One read for planning or reviewing a day: the day's tasks in display order (timed first), tasks left open the day before, repeating tasks due that day with their streak (streak_today on other days), and planned vs done for that week (Monday to Sunday). Fits for reading a day without showing it: reviewing how a day went, or answering a question about it. When the user wants to see or plan their day, show_day fits. Omit date for the user's today. Tasks of spheres the user hides from their day (Hide from my day) are left out of the tasks and of the week's planned vs done (Dashboard in the app still counts their done ones), only their number shows as hidden_from_day; get_tasks lists them.

Habit statistics; a habit is a repeating task. With task_id (any day of the series): planned vs done over the last 4 weeks, the streak toward 67 days, 8 weeks of history, the app's verdict with its suggestion, and the latest two month report if there is one. Without task_id: every live habit, weakest first. Fits when the user asks how a habit or their habits are going.

Tasks for one day, or for a range of up to 62 days (date to to_date); omit date for today. Fits when the user asks what is planned on a day, week or period. Includes tasks of spheres other people share with the user: those carry "shared" (sphere, owner, my_role, locked, can_tick; for the owner and responsible people also ticked of the whole group). A locked task belongs to someone else: it can only be marked done or not done with update_task; when my_role is responsible, add_subtask works on it too. A task with hidden_from_day is in a sphere the user keeps out of their daily list (for example scheduled blog posts): mention it only when asked about that sphere or the whole period.

The user's today: date in their time zone, main goal, day streak, and today's tasks with subtasks (shared ones too, see get_tasks). Tasks of spheres the user hides from their day (Hide from my day) are left out, and out of today_total and today_done, only their number shows as hidden_from_day; one with a time and a reminder still shows, marked hidden_from_day. get_tasks lists them. Open tasks whose time has passed: ask what got done. Fits when the user asks about today or a relative date needs resolving.

Draw an arrow from one goal to another: reach the first, then the second opens. The two may be in different periods, earlier period first (January's goal to February's, a month goal to the year goal). Loops are refused.

The user's Focus section: its spheres with point counts, and the focus points (short statements the user keeps in front of them), starred (important) first, then in the user's order. Each point has its place in its sphere's list. Pass sphere to see one sphere only. Up to 200 points per call; when more is true, call again with offset set to next_offset. Fits when the user asks about their focus points.

The user's goals for the current month, quarter and year (or one horizon), with subgoals (ids, done), arrows (after, leads_to) and locked. Pass date for the periods that contain another day. Fits when the user asks about their goals or progress toward them.

The user's spheres (life areas) with colors and sections; hidden_from_day marks a sphere kept out of the daily list. Planning spheres (used by tasks) by default; pass section for Goals, Focus, Visualisations or all. Fits when a task, goal or point needs a sphere, or the user asks about their areas.

Shows one day to the user: the same compact day as get_day_brief (tasks in display order, yesterday's open tasks, habits due, the week's planned vs done). In clients that display apps the user also sees their Aimgod day there and can tick, reorder, time and add tasks in it. Fits when the user asks to see or plan their day or what is on it. Omit date for the user's today.

Mark a task handed to an agent as being worked on now: its line runs in the user's day. Returns the task and notes_taken, the user's waiting notes (newer than get_agent_work may have shown; they count as handled once you finish the task); follow them. Call it before working on the task.

Remove the arrow from one goal to another. The goals stay.

Rename a focus point, star or unstar it (important), move it to another Focus sphere, or give it a new place in its sphere's list (1 is the top). Send only what changes. Point ids come from list_focus.

Rename a goal, mark it reached or not, star it (important), set its sphere, or add a subgoal. Send only what changes. A goal linked after other goals can be marked reached only once the goals before it are reached, whatever period they are in.

Rename a sphere, change its color, set the sections it shows in, or hide it from the day, when the user asks. Send only what changes.

Tick a goal's subgoal done or not done, or rename it. Subgoal ids come with each goal. Ticking is refused while the goal is locked.

Tick a subtask done or not done, or rename it. Subtask ids come with each task in get_today and get_tasks. Send only what changes.

Change one task when the user asks: rename, move to another date, set or clear the time, mark done or not done, star, set the sphere or description, set or remove the reminder (null removes it), set, change or stop the repeat. Send only what changes. On a repeating task the name, description, time and reminder change for the whole series from this day on; subtasks are each day's own. Repeating tasks are habits with statistics: when moving several tasks ("move everything to tomorrow") move only one-off tasks; move a repeating task only when the user names it, and only to a day its habit does not have yet (a daily habit already has tomorrow, so leave it and tell the user).