Glossary

Definitions of terms used in Toban.

Core Concepts

Project

The top-level unit of management in Toban. A Project contains a connected GitHub repository, agents, sprints, and ADRs. Switch between Projects from the sidebar header.

API name: workspace. The API endpoints use /api/v1/workspace, but the user-facing term is "Project."

Sprint

A time-boxed work cycle. Phases progress in order: Active -> Review -> Retrospective -> Completed. A Project can have multiple Sprints. Sprint #0 is the initial sprint auto-created on Project setup.

Task

A unit of work within a Sprint. Status transitions: todo -> in_progress -> review -> done. When the owner is set to an agent role (e.g. builder), the CLI picks it up automatically. Tasks owned by user require manual handling.

Backlog

Tasks not assigned to any Sprint (sprint number = -1). Use the Backlog to queue work for future Sprints.

Story

A higher-level work item that groups related Tasks. Creating a Story auto-creates a Builder task for it. Stories provide structure for larger features.

Handoff Notes

Context notes attached to a task (context_notes field). Used to pass information between agents or from a user to an agent when a task is created or reassigned.

Agents

Manager

LLM-powered coordination agent. Interacts with users via chat, proposes tasks (propose_tasks), requests agent spawning (spawn_agent), and manages Sprint flow. Included as a platform service.

Builder

Worker agent that implements code. Works in an isolated git worktree, commits changes, and the CLI merges to main and pushes on completion.

Reviewer

A template (not a standalone agent role) used to perform structured code review on completed tasks. Produces a review report with quality scoring.

Configuration

Template

A prompt template that controls agent behavior. Available templates: implementation (for Builder task execution) and reviewer (for code review).

Knowledge

Shared memory entries that persist across agent sessions. Used for cross-agent context (design decisions, known issues, architecture notes). Managed at Settings > Knowledge or via the API.

ADR (Architecture Decision Record)

A document recording an architectural decision for the Project. ADRs are injected into agent prompts so agents respect past decisions. Each ADR has context, decision, rationale, and consequences.

Project Spec

Defines the Project's vision, target users, tech stack, roadmap, and constraints. Used as context in agent prompts.

Prompts

A read-only debug preview of the full prompt that agents receive. Available at Agents > Prompts or via GET /api/v1/agents/:name/prompt-preview.

Infrastructure

CLI (toban-cli)

The local agent runner. Communicates with the dashboard via WebSocket and REST API. Spawns and manages agent processes. Run with npx toban-cli@latest start.

Engine

The execution backend for agents. Currently only claude-code (Claude Code CLI) is supported. Future engines: claude-api, codex, gemini.

Worktree

An isolated working directory created via git worktree for each task. Each agent gets its own branch and directory, merged to main on completion.

Audit Log

A record of security-relevant events in the workspace (auth events, agent spawns, prompt injection attempts).

Workflow

Story Points

Estimation of task size using the Fibonacci sequence: 1, 2, 3, 5, 8.

Velocity

Total story points completed per Sprint. Viewable on the Analytics page.

Quality Score

A numeric score (0-100) calculated from review results. Based on requirement match, code quality, test coverage, and risk assessment. Tracked per task and aggregated per sprint.

Enrich

An optional step that adds structured details (acceptance criteria, technical notes) to a task before agent execution. Not required.

Sprint Goal

A free-text memo field on a Sprint describing what the sprint aims to accomplish.