Jared
A Claude Code plugin that turns a GitHub Projects v2 board into the single source of truth for what's being worked on — with a discipline that survives across sessions, weeks, and shifts in scope.
Project boards drift. Scope leaks into TODO: comments and tmp/next-session-prompt.md files. Plans approved three weeks ago no longer match the code. By month two the board is decorative and real status lives in your head. Jared makes the board the thing you actually look at.
---
What it's for
Long-running work on a complex project — features that take more than one sitting, bugs surfaced mid-refactor, plans that need to outlast the session that wrote them. Anywhere the work is bigger than your working memory, Jared keeps the board in lockstep with reality so you (and any agent picking up the work) can resume from the board instead of from recollection.
It works just as well on non-software projects. A kanban for renovating a house uses the same model — Backlog / Up Next / In Progress / Blocked / Done — with work streams like Demo, Rough-in, Finish. The invariants are identical.
The shape Jared enforces:
- Five Status columns. Backlog / Up Next / In Progress / Blocked /
Done. Blocked is a column, never a label.
- Status + Priority required the moment an issue lands. jared
file is atomic — issue created, on board, fields set, or fail loudly.
- Blocked-by is a native GitHub dependency (addBlockedBy /
removeBlockedBy GraphQL), not a comment convention.
- WIP cap on In Progress (default 4, counted in workstreams when
multiple parallel sessions are running).
---