drawbar

drawbar

A lean, Linear-native design → plan → work → learn workflow for Claude Code, with a per-project compounding knowledge base.

Enjoy a mix of AI generated readme, and my interjections in the text below.

Why is it called drawbar

I just got a clonewheel and am digging it, a lot. Other than that, no reason. I'm following the grand tradition of software projects with inscrutable names.

Who it's for

drawbar is for people who love the Beads way of working — atomic, traceable issues and knowledge that compounds across sessions instead of evaporating — but who:

• live in Linear. Your issues stay in Linear, visible to the whole team: a spec is a parent issue's description, stories are ordered sub-issues, status flows Todo → In Progress → Done. Issues aren't stored locally. I know this makes things slower and probably wastes tokens, but this works better for my and my team.
• want a human in the loop, not full autonomy. drawbar is a set of deliberate, reviewable steps — you sharpen scope, pick the approach, approve the plan, and review the work — rather than a fire-and-forget agent. If beads is meth, this is a glass of iced tea.

This is really just an old-school issue tracking workflow with some glue. It is not novel but it has been working well for me.

The knowledge base is the heart of it: every lesson, decision, and "MUST-CHECK" you capture is recalled on the next design/plan/work, so the system gets sharper the more you use it.

If you want maximum agent autonomy, drawbar will feel too hands-on. If you want an agent that drafts and proposes while you stay the decision-maker — and a memory that actually accumulates — that's the point.

Requirements

drawbar needs two things set up before it works:

• Bun — runs the drawbar-kb knowledge CLI (and the tests). Install: curl -fsSL https://bun.sh/install | bash.
• The Linear MCP, connected in Claude Code — drawbar tracks all work in Linear through the MCP (mcp__…Linear… tools must be available in your session). Without it, the design/plan/work commands can still run locally but won't write to Linear.

Plus Claude Code itself (the plugin host).

Install

1. Add the marketplace and install the plugin:

   claude plugin marketplace add mjn298/drawbar
   claude plugin install drawbar@drawbar
   

   Then run /reload-plugins (or restart) so the /drawbar-* commands load.

2. Run /drawbar-setup once in a project. It links the drawbar-kb CLI onto your PATH (via bun link from the installed plugin) and initializes <project>/.drawbar/memory/.

   If drawbar-kb still isn't found afterward, add Bun's global bin to PATH:

   export PATH="$(bun pm bin -g):$PATH"
   

Hacking on drawbar itself? Skip the marketplace and load the repo directly — see Development.

Use

/drawbar-setup [legacy knowledge.jsonl]   # once per machine + per project
/drawbar-design <feature | issue-id>       # spec → Linear parent issue
/drawbar-plan <issue-id>                    # ordered story sub-issues
/drawbar-work <issue-id>                    # implement next story, TDD
/drawbar-learn [issue-id]                   # curate lessons into the KB

issue-id is a Linear issue identifier (e.g. ABC-123) — your team's own prefix.

The [legacy knowledge.jsonl] argument to /drawbar-setup is only for migrating an existing lavra knowledge base into drawbar. If you weren't using lavra before — most people — skip it and start with a fresh, empty knowledge base.

Knowledge lives in <project>/.drawbar/memory/ (the JSONL is committed; the SQLite index is gitignored). Query it directly anytime:

drawbar-kb recall "dynamodb tenancy" --dir "$PWD/.drawbar/memory" --json
drawbar-kb stats --dir "$PWD/.drawbar/memory"

Development

Working on drawbar itself? The kb tool has tests:

bun test

Loading your edits — two modes:

• Iterating fast → run the live source directly. Launch Claude Code with --plugin-dir so it loads your working copy and bypasses the plugin cache entirely:

  claude --plugin-dir /path/to/drawbar
  

  Edits to commands/agents/skills take effect on /reload-plugins — no version bump, no reinstall. It shadows any installed copy for that session only.

• Releasing a change through the marketplace → bump the version. The plugin cache is keyed by plugin.json version, so editing files in place at the same version silently won't propagate — /reload-plugins keeps serving the stale cached copy. To ship a real change: