Small steps.
Clear outcomes.

Pick the next Story. Agree on the result. Build it yourself or with a coding agent. Check the work before you call it done.

Keep the next task clear. Order your Backlog. Keep later ideas in the Icebox.

Share the brief. Your team and agents use the same scope and acceptance criteria. Connect agents through MCP and link work in GitHub.

Explore TrackerBoard overviewFollow a Story →

Launchpad / BoardCycle: Foundation

Unstarted3

Ready for the team

FeatureLCH-18

Add keyboard shortcuts to the command palette

Structured Stories

MMaya3

SpikeLCH-21

Prototype offline sync for field notes

Workspace foundations

BABuild Agent2

BugLCH-24

Keep draft labels after a Project switch

Project navigation

MMaya1

Started2

Work in progress

FeatureLCH-12

Build the Project switcher

Project navigation

BABuild Agent3

ChoreLCH-27

Align local test commands

Backlog and cycles

MMaya1

Finished1

Implementation ready

ChoreLCH-9

Create the HTTP API scaffold

Application foundation

BABuild Agent2

Delivered1

Ready for review

BugLCH-7

Stop duplicate notifications

Workspace foundations

MMaya1

Accepted1

Checked by the team

FeatureLCH-4

Document the delivery workflow

Structured Stories

MMaya1

LCH-18 · priority 01Unstarted

FICTIONAL STORY

Add keyboard shortcuts to the command palette

Feature · 3 points

Open the palette, move between results and close it with the keyboard.

Scope

⌘K / Ctrl+K, arrow keys and Escape. Custom key bindings are outside this Story.

Maya · Product owner

Fictional Project. This illustrated Story shows the current step in the example.

One Story, from brief to acceptance. Follow the example below.

Try the walkthrough →

Illustrated Board · fictional Project · explore the viewsFollow LCH-18 →

Finished is a state.
Accepted is your call.

Follow LCH-18 from its first brief to the delivered result. Try the example, check the criteria and make the final decision.

Read the five Story states ↓

1Unstarted
2Started
3Finished
4Delivered
5Accepted

LCH-18

Maya

Product ownerFictional example · LCH-18

Unstarted

Start with a shared brief.

Maya defines the keyboard shortcuts and acceptance criteria, then puts LCH-18 first in the Backlog.

Scope defined · three acceptance criteria · first priority

Local example only. No Project data changes.

Unstarted: Maya ranks the scoped Story first.

Started: Build Agent reads the brief through MCP and starts the Story.

Finished: The agent links an illustrative GitHub pull request and verification notes.

Delivered: A reviewer tries the result and checks the acceptance criteria.

Accepted: A team member accepts the Story after checking the work.

The scope, implementation evidence and human review stay connected to the same Story.

Start using Tracker Back to the overview

Small steps.
Clear outcomes.

Add keyboard shortcuts to the command palette

Prototype offline sync for field notes

Keep draft labels after a Project switch

Build the Project switcher

Align local test commands

Create the HTTP API scaffold

Stop duplicate notifications

Document the delivery workflow

Add keyboard shortcuts to the command palette

Choose what your team works on next.

Add keyboard shortcuts to the command palette

Acceptance criteria

Finished is a state.
Accepted is your call.

Start with a shared brief.

Add keyboard shortcuts to the command palette

Prototype offline sync for field notes

Keep draft labels after a Project switch

Build the Project switcher

Align local test commands

Create the HTTP API scaffold

Stop duplicate notifications

Document the delivery workflow

Add keyboard shortcuts to the command palette

Choose what your team works on next.

Add keyboard shortcuts to the command palette

Acceptance criteria

Finished is a state.Accepted is your call.

Start with a shared brief.

Finished is a state.
Accepted is your call.