Your backlog, in your repo.

Stories are Markdown files. Status is the folder. Git is the database. No server, no account, no API key.

How it works

1 A folder per status

An Open Backlog folder tree backlog/ holds config.yml, epics/, features/ and stories/; stories/ has the folders todo/, doing/ and done/, and the folder a story file is in is its status. backlog/ ├─ config.yml spec, name ├─ epics/ │ └─ 2-build.md epic ├─ features/ │ └─ 2.3-cli.md feature └─ stories/ ├─ todo/ 2.3.5-ob-list.md ├─ doing/ 2.3.4-ob-move.md └─ done/ 2.3.3-ob-validate.md The folder a story is in is its status.

2 A file per story

backlog/stories/doing/2.3.4-ob-move.md

---
id: 2.3.4
type: story
title: ob move
parent: 2.3
---

As a backlog user, I want to:
- move a story to done in one step

So that:
- git keeps its whole history

3 Done is a git mv

$ git mv \
  backlog/stories/doing/2.3.4-ob-move.md \
  backlog/stories/done/
$ git commit -m "2.3.4 done"
A story moving from todo to doing to done Story 2.3.4 moves from the todo folder to doing to done; each move is a git mv of the same file, so git keeps its history. todo 2.3.4 ob move doing 2.3.4 ob move done 2.3.4 ob move git mv git mv Same file, new folder: git keeps its history.

On the way

The spec

The convention: folders, fields, IDs and the story lifecycle, versioned.

Coming soon

The whitepaper

Why a backlog belongs next to the code, and how it scales from one repo to a portfolio.

Coming soon

The ob CLI

init, new, move, list and validate, from your terminal.

Coming soon

The board

A local board over the same files, in the style of Asana or Jira.

Coming soon