Why project management needs to change for AI agents

You can assign a coding task to an agent, let it change the code, and ask a reviewer to check the result. That workflow includes a new kind of contributor, while many project-management habits still assume that one person reads the backlog, chooses the work, and reports the result.

A project-management system for this workflow needs an agent identity, a current briefing, and a way to connect work to the outcome it should move. Atoll uses agent members, assigned work, strategy records, and heartbeat to provide those pieces. Humans keep the permissions and review decisions that the workspace requires.

Agent identity belongs in the member model

An agent needs a durable identity for assignment, permissions, activity, and audit. A shared human API key hides which process acted and makes a later review harder. A generic integration identity hides the agent's assigned work and owner.

Atoll represents an agent as an organization member with its own credentials and access. Teams can assign an issue to that member and see the agent as the actor in the activity trail. The access scope still applies to every read and write.

Each run needs current orientation

A human brings context from prior conversations and work. An agent receives the context its harness supplies for the current run. The product can fill the gap with a structured read of the current state.

Atoll heartbeat returns current strategy and execution context within the caller's permissions. Compact output groups actionable signals, direct attention, counts, page data, and a strategy-backed recommended action when Atoll has enough evidence. A full read can include goals, KPI pace, initiatives, assigned work, and relevant project context.

A team can configure an agent's heartbeat sections and signal focus. That policy narrows the briefing. It does not grant project or KPI access.

Work selection needs relationships

A backlog gives an agent a list. Strategy links add reasons for choosing one item over another. Atoll connects goals, KPIs, initiatives, milestones, targets, and issues so an agent can inspect the outcome, the expected impact, and the execution condition before it starts.

The agent can read whether a KPI is off pace or stale, whether an initiative has stalled work, whether a target is approaching its due date, and whether a dependency blocks an issue. Those signals give the agent evidence for the next action. The agent still checks the current board and any required human approval.

Three levels of autonomy

A useful vocabulary separates three operating levels:

1. An assistant summarizes or drafts while a human chooses each action.
2. An executor receives a scoped task and completes it with limited intervention.
3. A member reads authorized organization context, selects work based on its leverage, and returns progress for review.

The third level requires structured strategy data and a durable agent identity. A better drafting feature does not provide those records by itself.

An illustrative morning

Consider a fictional workspace with a KPI for paying customers, an initiative expected to move it, and an open issue linked to that initiative. The sequence below illustrates a supported workflow; it is not a report from a real Atoll organization.

1. The agent runs atoll heartbeat --json and handles direct attention before broad signals.
2. A KPI signal and initiative context point to an open issue with a clear next step.
3. The agent reads the issue and dependencies, then starts work with an approved atoll issue update command.
4. A human reviews the change. The agent reports progress and records a KPI snapshot only when it has an authorized, valid measurement.

The records keep the reason for the task beside the work. The review loop keeps a human responsible for the decisions the team has reserved for people.

A practical design test

Choose one workflow and ask five questions. Can the agent identify itself? Can it read the current state allowed by its access? Can it select a concrete task from the strategy context? Can it take the intended action and report it? Can a human inspect the result and the actor?

Record each handoff that requires a person to recall hidden context or translate a screen. Then decide whether the product needs a field, a command, a permission rule, or a review step. This test turns an agent discussion into a product backlog with specific work.

A category taking shape

Project management for agent contributors sits between task tracking and agent runtime. It needs the accountability of a team workspace and the machine-readable context of an agent tool.

In Atoll, create an agent member, assign work to it, and read the heartbeat before the next action. The strategy chain gives the agent the reason for the work, while activity and review records show what happened afterward.

If your team is adding agents to production workflows, read the Atoll guide to AI project management for the concrete model and the access boundaries behind it.