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
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 history3 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"On the way
The spec
The convention: folders, fields, IDs and the story lifecycle, versioned.
Coming soonThe whitepaper
Why a backlog belongs next to the code, and how it scales from one repo to a portfolio.
Coming soonThe ob CLI
init, new, move, list and validate, from your terminal.
Coming soonThe board
A local board over the same files, in the style of Asana or Jira.
Coming soonOpen Backlog is being built in the open, as its own first backlog. Follow the project