PortfolioCase study
CF-01Built · local tool
Campfire Board
One dashboard, every project.
A local-first, multi-project management dashboard for the AI build workflow — a personal fork of Backlog.md, reshaped into a cross-project command centre.
10
build-workflow stages, Discovery to Deployment
Structural
1
local binary — nothing to deploy
Structural
Evidence keyStructuralPrototype
The problem
Many builds, many folders — no single view.
Each project keeps its tasks as Markdown files in its own backlog folder — agent-first and self-contained, but nothing showed every project at once.
The product
Switch projects; see the board, the Gantt and the workflow.
A project switcher, a Kanban board with an Execution / Workflow toggle, an hours-axis Gantt with dependency arrows, the ten-stage workflow view, statistics and an in-app artifact viewer.
Decisions
Fork, don’t rebuild — and keep it local.
- Could have
- Write a tracker from scratch
- Chose
- Fork Backlog.md, with credit
- Because
- It inherits a Markdown-native, agent-first design (Alex Gavrilescu and contributors, MIT licence).
- Could have
- A hosted, multi-user service
- Chose
- One local binary with the UI inside
- Because
- Nothing to deploy: launch it locally in Chrome over your own folders.
How it works
Markdown on disk, one binary on top.
- projects.jsonthe manifest of projects
- backlog/ folderstasks as Markdown files
- Bun-compiled CLIa single local binary
- Embedded React UIserved on a loopback address
- Board, Gantt, Workflow, Stats
Evidence
Piloted on scratch projects; not yet on real ones.
3 / 3
pilot checks passed: switching, ticket moves, isolation
Prototypeas of 6 Sep 2026
scripted, at the API level, against two throwaway projects
What isn’t measured
- No users or usage data are recorded.
- No hosted product link, by design: it runs on your machine.
Sources
Everything here is backed by a real artifact.
- Readme
- Evaluation
- Design