# Agentic Kanban: a worked example

A made-up team, so you can see every part working together. The records are in [example-board.json](https://hamedtaheri.com/playbook/v0.2.0/framework/example-board.json); [the flow tools](https://hamedtaheri.com/playbook/v0.2.0/tools/README.md) compute the brief and the report from them.

## The work

The team needs an import workflow. It is an `epic` with two parts: a storage contract and the import job. An `investigate` task asks whether imported files can be kept for 30 days. An export task and an import guide wait on the import.

## Monday

The storage contract runs once and is accepted: checks pass on the exact revision, a reviewer approves, and it merges. The import job is now unblocked.

## Tuesday

The import job's first attempt stops: it finds a column the contract did not describe. That is not a failure of the developer; the worker protected the team from a guess. The task goes back to preparation, the developer answers one question in a decision round, and a second attempt implements the revised brief.

## Tuesday evening

The developer stops. The agent saves a resume point on the task: branch, revision, checks already run, the real-database check still left, and the next command. Nobody creates a "finish import" task.

## Wednesday morning

The morning brief for the developer reads:

1. **Decide:** the retention question has an answer ready and waits on you.
2. **Resume:** the import job, from last night's resume point.
3. **Review:** a teammate's rate limiter change is assigned to you.

The export task is ready (its blocker is done), so it is listed after those. The import guide is not ready: it waits on the whole import epic.

## Friday

The weekly review shows one accepted outcome this week: a `fix` from a teammate, $0.49 including its review, accepted on the first attempt after six hours waiting on a person. The storage contract is a `part`, so it rolls into the import epic and is not counted on its own. The epic counts once, when all its parts are done and its own acceptance holds.

The retro asks why the import brief missed a column. The team changes one rule: briefs that touch storage include the current schema lines. They check next Friday whether it helped.