Skip to main content

Planning

Codebolt includes a set of built-in planning tools that live alongside your code and your agents. They cover the full arc from strategic intent to individual work items — and agents can read and update them, so your plans stay connected to what's actually happening in the codebase.

The tools​

ToolWhat it's forLevel
RoadmapFeatures, phases, and ideas — the product visionStrategic
SpecsTechnical specification documents with rich formattingDocumentation
UI FlowWireframes and UI mockups on a freehand canvasDesign
Requirement PlanAggregated documents linking specs, flows, and action plansAggregation
Action PlanStructured execution plans with tasks, dependencies, and parallel groupsExecution
TasksIndividual work items with status, priority, and sub-task hierarchyOperational

How they fit together​

Planning overview: roadmap feeds tasks, requirement plans aggregate specs, UI flows, and action plans, and action plans drive execution tasksHow The Planning Tools ComposeRoadmapProduct intent: phases, features, and ideation.phasesfeaturesSpecsTechnical behavior, constraints, and design detail.written in rich Markdown / MDXUI FlowScreens, wireframes, and interaction sketches.freehand canvas stored in projectRequirement PlanOne aggregation document that embeds linked planning artifacts.spec linksflow linksplan linkslinks artifacts into one planning documentAction PlanExecution graph with dependencies, loops, and parallel groups.often created and updated by agents during multi-step workhow it gets builtTasksIndividual work items, status, priority, subtasks, and messages.backlog and live work trackingconvert roadmap features into tasksexecution breaks down into tasksUse one artifact on its own, or combine them into a planning stack that stays readable by both people and agents.

The tools are independent — you can use any one without the others. But they're designed to compose: a Roadmap feature can become a Task; a Requirement Plan can pull together a Spec, a UI Flow, and an Action Plan into one document.

Where planning tools live​

Every planning tool persists inside the project:

ToolLocation
Roadmap.codebolt/roadmap/roadmap.json + ideation.json
Specsspecs/*.specs
UI Flows.codebolt/uiflows/
Requirement Plansplans/*.plan
Action Plans.codebolt/.action-plans/
TasksIndexed in the Codebolt database

All files (except Tasks) are plain JSON or Markdown on disk. You can check them into version control, diff them, and share them with your team.

Agents and planning​

Agents can read and write every planning tool via the codeboltjs SDK:

// Read the roadmap
const roadmap = await codebolt.roadmap.getRoadmap();

// Create a task
await codebolt.taskplaner.createTask({ name: 'Fix auth bug', priority: 'high' });

// Update an action plan task status
await codebolt.actionplan.updateTaskStatus(taskId, 'completed');

// Read a spec
const spec = await codebolt.specs.get('auth-flow.specs');

This means agents can plan their own work, report progress back into the planning tools, and surface what they've done where you can see it.