Skip to Content
Kanban Board

Kanban Board

AgentLoop includes an interactive terminal-based kanban board for visual task management. Tasks flow through columns as they progress through the development workflow.

Opening the Kanban Board

Open the kanban board with:

> /orchestrator kanban

Board Columns

The kanban board has five columns representing task states:

┌─────────────────────────────────────────────────────────────────────────────┐
│                           Kanban Board                                      │
│  ┌─────────┐  ┌─────────────┐  ┌────────┐  ┌──────┐  ┌─────────┐            │
│  │  Todo   │  │ In Progress │  │ Review │  │ Done │  │ Blocked │            │
│  │         │  │             │  │        │  │      │  │         │            │
│  │ Task 1  │  │   Task 3    │  │ Task 5 │  │Task 7│  │ Task 9  │            │
│  │ Task 2  │  │   Task 4    │  │ Task 6 │  │Task 8│  │         │            │
│  └─────────┘  └─────────────┘  └────────┘  └──────┘  └─────────┘            │
└─────────────────────────────────────────────────────────────────────────────┘
ColumnDescription
TodoTasks waiting to be started
In ProgressTasks currently being worked on by agents
ReviewTasks awaiting review or validation
DoneSuccessfully completed tasks
BlockedTasks that cannot proceed due to dependencies or issues

Managing Tasks

Adding Tasks

Add tasks naturally:

> Add a new task for implementing the login page
> Create a task to fix the payment bug

The PM agent will create well-structured tasks with descriptions.

Moving Tasks

Update task status using natural language:

> Mark task 5 as in-progress
> Move the login task to review
> Move all completed tasks to done

Viewing Tasks

List all tasks:

> /tasks

Checking Status

Ask about task status naturally:

> What's the status of task 5?
> What tasks are currently in review?
> Which tasks are blocked and why?

Task Dependencies

Tasks can have dependencies that affect when they can be worked on. The DAG scheduler manages these relationships.

Adding Dependencies

> Add a dependency so task 3 must complete before task 7
> Make the login task depend on the database setup

Viewing Dependencies

> /orchestrator dag ascii

This shows an ASCII visualization of task dependencies:

Task 1 (Database Setup)
    └── Task 3 (User Model)
        ├── Task 5 (Login API)
        └── Task 6 (Register API)
            └── Task 7 (Auth Middleware)

Removing Dependencies

> Remove the dependency between tasks 2 and 5

Task Properties

Each task can have:

PropertyDescriptionValues
StatusCurrent statetodo, in-progress, review, done, blocked
PriorityImportance levellow, medium, high, critical
DependenciesTasks that must complete firstList of task IDs
AssigneeAgent working on the taskengineer, qa, etc.

Workflow Example

# Generate tasks from a description
> Break down "user authentication" into tasks

# View the board
> /orchestrator kanban

# Check which tasks are ready
> Which tasks can be started now?

# Start working on a task
> Mark task 1 as in-progress

# Add a dependency discovered during planning
> Task 4 should wait for task 2 to be done

# Move completed work
> Mark task 1 as done and move task 2 to in-progress

# Check blocked tasks
> What tasks are blocked?

Integrating with Jira

The kanban board can sync bidirectionally with Jira:

> /jira sync

This synchronizes:

  • Task status updates
  • New tasks from Jira
  • Completed work back to Jira

See Integrations for Jira configuration.

Clearing Tasks

Clear all tasks for the current project:

> /orchestrator clear

This permanently removes all tasks. Use with caution.

Learn how tasks are scheduled and executed.

Orchestrator

See how agents work on tasks.

Agents
Last updated on
AgentsGit Worktrees