Tasks

The Task Board is a kanban board for work you want to come back to. Cards move through status columns and each one can carry a git branch.

The board is still Beta, and says so on its own header. Read the sections below with that in mind: what is described here is what the board stores, and some of it has more behind the schema than in front of it.

Task Board Overview

Open the Task Board from the Command Palette ("Task Board") or the sidebar. Tasks are organized into columns by status.

Task Statuses

A task holds one of six statuses, five of which have a column on the board:

Status	Description
Backlog	Not yet planned
Ready	Planned and ready to start
In Progress	Actively being worked on
In Review	Work complete, awaiting review
Done	Completed
Cancelled	Abandoned, and kept off the board rather than shown in a column

Drag tasks between columns to update their status.

Creating a Task

Create tasks from the Task Board or Command Palette. Each task has:

Title: short description of the work
Description: detailed context (optional)
Priority: critical, high, medium (default), or low
Assignees: assign to humans or agents
Tags: arbitrary labels for filtering
Git Branch: link to a feature branch
Working Directory: project path for the task

Task Links

Tasks support typed relationships to other entities:

Link Type	Target
`file`	Source file
`session`	Agent session
`commit`	Git commit
`pr`	Pull request
`parent` / `child`	Task hierarchy
`blocks` / `blocked_by`	Dependency graph

Assigning to Agents

Tasks can be assigned to AI agents. When an agent is assigned:

The agent type (human or agent) and ID are recorded.
Workflows can trigger agent sessions automatically when a task status changes.

Workflow Automation

Workflows run steps off task events: moving a card to Done can create a branch or commit without anyone touching git by hand.

This part is the least finished thing in Vect, and the honest summary is short. There is no workflow editor yet, and the only workflow that runs today is the one fired when a task moves to Done. Of the events below, only task.status_changed is matched; of the steps, the git branch, checkout, commit, push and approval steps are the ones with working handlers. The rest are declared in the schema and will fail if a workflow reaches them.

Triggers

Event	Runs today
`task.status_changed`	Yes
`task.created`	Declared only
`task.assigned`	Declared only
`session.completed`	Declared only
`file.saved`	Declared only
`manual`	Declared only

Step Types

Step	Description	Runs today
`git_create_branch`	Create a new git branch	Yes
`git_checkout`	Switch branches	Yes
`git_commit`	Auto-commit changes	Yes
`git_push`	Push to remote	Yes
`human_approval`	Pause and wait for human confirmation	Yes
`git_create_pr`	Open a pull request	Not wired yet
`run_command`	Execute a shell command	Reports what it would run
`notify`	Send a notification	Not wired yet
`git_create_tag`	Tag a release	Declared only
`update_changelog`	Update CHANGELOG	Declared only
`agent_spawn`	Start an agent session	Declared only
`agent_send`	Send a prompt to a running agent	Declared only

Workflow Runs

Each workflow execution is tracked as a run with status: pending, running, waiting_approval, completed, failed, or cancelled. Step results include output and timing.