Skip to content

Maestro Project

Where the plan and the notes live together.

Project is the planning surface for the suite. Roadmaps, milestones and the notes from the call sit in one place, so the decision a meeting reaches lands on the board before anyone leaves the room. It is the plan the agents read from.

app — roadmap · Q3
A quarterly roadmap: four projects as timeline bars with health status and milestone markers.

What a plan is made of

Projects, milestones, health.

Enough structure to steer by, and no more. Everything ties back to the work on the board, so the roadmap can never quietly drift from the truth.

01

Projects

A project groups a backlog and a roadmap. Tasks and plans belong to it, and the board can be read one project at a time.

02

Milestones

Dated markers on the roadmap. An agent posts against them as work starts, passes review and ships, so the timeline moves on its own.

03

Health

on_track, at_risk, off_track. A field you set, sitting next to the work that justifies it, so the status is never a guess.

The notes are not separate

The meeting ends with the board already updated.

A whiteboard kept the plan beside the notes and lost the tasks. Here they are the same object: what the call decides is captured as tasks against the project as it is decided.

app — meeting · Q3 planning

Planner agents

Hand the research out. Keep the direction.

A planner agent reads the repo and writes a real implementation plan in markdown, drafting until it reports back ready. It researches instead of implementing, so nothing is edited while a plan is being drawn.

You read the plan and decide. Approve it and the steps flow onto the board; send it back with a steer and it revises. The plan groups under its project and exports to a PDF you can hand to the team. The judgement of whether it is the right plan stays with you.

plan · docs/plans/registry-sync-v2.md
A markdown implementation plan authored by a planner agent, marked ready and grouped under a project.

Part of the suite

A plan is only worth as much as what it turns into.

Feeds Tasks

A plan is not a document that rots in a drive. Its steps become tasks on the board, each carrying the plan it came from, ready to dispatch.

Maestro Tasks →

Feeds Orchestrator

Approve the plan and hand the whole project to the fleet. The orchestrator reads the backlog it produced and keeps eight to ten agents working through it.

Maestro Orchestrator →

▪ shipping deterministic orchestration

Take the podium.