Daily Operations: Walkthroughs and Meetings
After initiation and planning, the project moves into steady-state operations. The core of this mode is the walk (/manage): a short pass over the live tracker that turns into the question "what do I, as the manager, do next".
The walk: /manage
Type /manage — the agent passes over the live tracker (not a frozen snapshot) and prepares a dated walk document. Modes are chosen from the methodology in the project profile:
| Methodology | Primary mode |
|---|---|
| Scrum, LeSS, SAFe, XP (with sprints) | sprint: committed vs done, blockers, at-risk issues |
| Kanban, Scrumban | board: columns, WIP limits, blocked items, aging |
| Waterfall, PRINCE2, CPM | schedule: overdue, should-have-started, stale in progress |
| Shape Up | lookahead: what to pull into the next cycle |
If the project has a live schedule, an active sprint, or a board — the agent adds the corresponding section without extra questions.
What is always in the walk (PM briefing)
Regardless of modes, every walk has these sections:
- Start here — one sentence: the main operational focus for today.
- In flight — tasks being executed right now: status, due date, assignee. The agent says it explicitly: this work is running — monitor it with the performers and drive it to completion on time. Stale tasks (no updates) are flagged separately.
- Upcoming — what must start this period and next: with dates and assignees.
- Meetings needed — clusters: who to invite, for which tasks, why.
- Risks check — read-only from the register: which risks are still valid, which response measures are in progress, and what to check for progress. The agent does not rewrite the register — that is a separate command (
/risks).
What the walk does not do: it does not create tasks, change statuses, write full agendas (that is /meeting-agenda), or cut risks (that is /risks). It is a read-only pass with conclusions.
The agenda: /meeting-agenda
When a walk produces a "meetings needed" cluster, the agent offers /meeting-agenda: on your confirmation it prepares a dated agenda:
- Goal — 1–3 sentences on why the meeting is needed now;
- Attendees — named individuals only (from tracker assignees, the charter RACI, or your list): "the team" or "everyone" are not attendees;
- Agenda — topics with an owner, a timebox, and references to issues/risks; the timeboxes sum to no more than the meeting length;
- Decisions needed — what the meeting must close;
- Prep — what each attendee should check before the call.
The agenda is written to a dated file — you can send it or run the meeting by it. The agent does not book calendars or create call links: that is your system.
Quality rule: one meeting — one purpose. Unrelated topics are not mixed into one agenda.
A typical weekly rhythm
| When | What |
|---|---|
| Every day (morning) | /manage — "start here", monitoring "in flight" |
| Before the stand-up | /manage → /meeting-agenda for the cluster |
| Start of sprint/cycle | /manage sprint +, if needed, /plan sprint (commit) |
| End of period | /manage — carry-over, lookahead; optionally /status-snapshot (freeze for reporting) |
| On a risk signal | /manage → /risks / /risk-mitigate |
Where to continue
- Status snapshots and change analysis — from "what to do now" to "how the project changed".
- Risk management — what to do when the risks check finds candidates.
- Working with the schedule editor — when the walk shows date problems.