AgentLayerā–ødocs
Use it

Daily rhythm

What to run and when. Briefings and the pulse, goals from the day to the year, attention for the day, standup, session checkpoints, and sync.

A day with your agent has a few fixed points. Ask in plain words ("brief me", "plan my day", "set today's goals") or name the skill and playbook. Each one reads the board, the memory, and the recent sessions to tell you what matters, and nothing changes your tasks or goals until you confirm.

A day

WhenRunWhat you get
Sitting downbriefing morningPriorities, drafted artifacts, goals delta, per-project pulse, news, and a ranked list of first moves. Includes the Hijri date when your profile asks for it, and a red CI run on your code repo's default branch when the GitHub pack is set up
Setting the daygoals dayOne to three outcomes for today. See Goals
Planning the dayattention planToday cut to three, ranked toward today's goals. See Plan the day
Overwhelmedattention organizeYour head emptied into tasks and notes first, then today cut to three. See When there's too much in your head
Any timebriefing pulseA one-minute scan: anything stalled, recent errors, tasks past their cadence
Before standupattention standupDid, next, and blocked as a card to glance at while you talk. See Standup
Lostattention checkpoint allEvery recent session as a checklist, the decisions waiting on you first. See Checkpoints
Looking for somethingfind-sessionA past session found by what it worked on (a branch, a PR, a bug), with its resume command
Wrapping upbriefing eveningWhat shipped, drafted, and stalled, how today's goals landed, and tomorrow's first moves
Been awaysyncEverything current in one pass, optionally chaining a briefing. See Sync

How a briefing ends

Both briefings close with a short ranked list of what to do first, drawn from everything at once: a task due today or tomorrow, a session sitting idle until you answer it, a pull request or reply you owe, and only then goals you haven't set. The top item is the first move.

šŸ‘‰ First moves
  1. Send the vendor the signed renewal (ac-104, due tomorrow)   ← start here
  2. ā˜… Merge the billing fix? → yes, CI is green Ā· billing-retry session
     ↳ claude --resume 7c1e…
  3. Review the onboarding redesign (#212), owed 2 days
  4. /goals day: today's goals aren't set

The ā˜… items come from the newest checkpoint all report, so a briefing on its own reads what that report saw, and one chained from sync sees the sessions as of that run.

Goals

Goals are outcomes; attention plans the tasks that reach them. The goals skill writes the goals blocks at the top of projects/TASKS.md, one playbook per horizon:

PlaybookSets
goals dayOne to three outcomes for today, the finished state rather than the activity. The evening wrap scores them
goals weekMonday: two or three week goals, proposed from the roadmap's slipped and in-flight milestones first. Friday: the week scored. goals week interview grills you before it proposes anything
goals monthThis month's themes and big rocks, with a report card on last month
goals yearThe year, quarter by quarter, under the north star your roadmap names

The week is set and scored in one place, so the plan and the goals never disagree:

  • Monday. The goals you pick are applied in one step: each goal's task is planned for the week, and the Weekly Goals block is rewritten to match. The dashboard's Goals tab and the week lane show the same list.
  • Friday. Every task planned for the week is scored done, partial, or missed, with a reason for each miss, and you're asked where the open ones go.
  • Without asking. The standup playbook runs the Monday set and the Friday score on those days. goals week does the same any day.

Month and year interview you before drafting. Sync flags a week, month, or quarter that has come due and offers to run it (the week as goals week interview), and keeps nudging until you set it or consciously skip it. A bare goals runs whichever is due, or the day when nothing is.

Working sessions

  • flywheel runs a cross-project work session framed by the roadmap, for when several projects need a push in one sitting. It catches up on the sessions since its last run, advances, updates and closes tasks, keeps milestone statuses honest, and turns a task that keeps slipping into one decision. Sync runs it for you: see What flywheel does.
  • self-review is the monthly upkeep sync offers: a brain pass that clears stale tasks, memory and articles, and a rules pass that prunes the prompts and turns accumulated feedback into edits. See Self-evolution.
  • plan-spec interviews you into a standalone spec you can hand to your host's planning mode. A spec for code carries a design section and a check on every task.
  • roadmap builds or updates a north-star roadmap as a self-contained HTML page, its content kept as JSON inside the page so attention can read what's in flight.

The home's own roadmap, roadmap.html at the root, carries the north star: the one line every lane ladders up to.

  • The build takes the north star from the Yearly Goals header, or asks for one, and writes it back there. That header loads every session, so goals year then states it instead of asking each quarter.
  • When this year's goals aren't set, the build runs goals year first.
  • Sync offers the build at every run until the home has a roadmap.

All outputs land in reports/ and show up under today's reports in the next session's context.

On this page