Project Planner agent

The Project Planner agent breaks work into a delivery plan. It produces phases, the dependencies between them, milestones and effort estimates.

Where it runs

In both workflows it runs right after the Product Analyst, so it plans against agreed requirements and acceptance criteria. In Discovery & Spec it is the last step, which makes its plan the session's summary. In Feature SDLC the Architect designs the technical solution next.

Inputs

• The session task.
• A read-only snapshot of relevant files from the project's repository, so phases reflect the code that exists.
• The requirements from the Product Analyst and, in Discovery & Spec, the Researcher's survey of prior art.

Outputs

A phased plan in text. Beyond the session, the platform reads the plan and syncs its items to the workspace plan board, tagged with the session they came from and the project when there is one. A few rules keep the board usable:

• Items already on the board, matched by title, are not added again. Archived items count, so closed work is not brought back.
• At most 50 new items are added from one plan, so a list-heavy answer cannot flood the board.

On the Auto tier, its step goes to the Premium tier first.

Example run

Illustrative example, not a recorded session. After the Product Analyst writes requirements for workspace data export, the Project Planner proposes three phases. Phase one: the background export job and storage of the archive, about two days. Phase two: the owner-only button, the email with an expiring link and the audit entry, about a day, depending on phase one. Phase three: limits on export size and frequency, half a day. It marks one milestone, "an owner can download a full export", and one risk: large workspaces may need the export split into parts. Six items appear on the plan board.

Limits

• It has no view of your team's capacity, calendar or past velocity.
• Estimates are guesses from the model. Adjust them before you commit to dates.
• It plans the work. It does not assign it or track its progress.
• See projects for how plans relate to projects and changes.