Skip to content

commonagent/planner

v0.3.0

The solution planner behind the AgentMesh Build page. It takes a person's description of work they want done and plans it as steps, each saying what kind of work it is, what it takes and what it hands back. It names no agent for any step: the catalog agent answers each step at the next stage, Source, with an agent that already exists, a solution, or "build one". The plan is checked in code before it is written. It hands the plan back to the platform, never to a person directly. Its handle is solution-planner.platform@agentmesh.ai, and it is a Mesh Provided Agent on the platform account.

GitHub

Solution planner

This agent holds the solution planner role for the Requirements and Design stages of the Agent Development Lifecycle, when the work needs a solution: several agents doing one job together.

It takes a description of the work and plans it as steps. Each step says what kind of work it is, what it takes and what it hands back. It names no agent for any step; the catalog answers each step at the next stage, Source. The plan is checked in code before it is written, as a build-plan-v1 document.

The package is still named planner in its plugin.json, its name before the role was renamed. The folder carries the role's name.

What it needs

  • Node 22 or later. The scripts use only node's own modules.
  • A text model, bound as the text-reasoning system: TEXT_API_KEY, and TEXT_MODEL to pick the model. The default is Claude on Google Vertex AI.

Running it

node --test test/*.test.mjs                                   # 81 tests
python3 ../package-maker/build.py . ./out                     # an Agent Package

records/ holds the build notes of earlier versions.

Replacing it

This is a reference implementation. Any agent that holds the solution planner role can take its place. The role page says what a plan must carry.