> ## Documentation Index
> Fetch the complete documentation index at: https://docs.specpilot.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks and lanes

> Your tasks are rows in planning/tasks.md, and the board shows them in four lanes.

Each lane is a heading in `planning/tasks.md` with a table under it, one row per task. The board reads those tables and nothing else, so what you see is always what the file says.

| Lane | What goes there | IDs |
| - | - | - |
| Backlog | Work you have not planned yet | BL-### |
| Current Sprint | What you and your agent work on now, top first | CS-### |
| Review | Finished work waiting for you | as it was |
| Completed | Approved work, with its commit | CD-\<you>-### |

A task in Backlog, Current Sprint or Review has a type (feat, bug or chore), a priority (P1, P2 or P3) and a description. Type and priority are optional. An optional "Won't do" section keeps tasks you decided against.

## How tasks move

Backlog and Current Sprint swap freely. Current Sprint moves on to Review when the work is done, and Review goes back to Current Sprint when you send it back. Nothing is dragged into Completed: once you approve a task, your agent records it there with its commit.

## Both of you work the board

You drag tasks and add new ones in the App. Your agent lists and moves them through the local MCP connection. Every change is one line in `tasks.md`, so git shows exactly what happened, and SpecPilot sets up `.gitattributes` so parallel edits to `tasks.md` merge cleanly.

## Keeping it short

When Completed grows long, Archive moves the oldest rows to `planning/tasks-archive.md`. Use it in the App or run `specpilot archive`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.