A real backlog, made of markdown.
Boards, task types, subtasks, links, and checklists, with every task a file in your folder that serves a blueprint by its permanent id. The work stays beside what it builds, and closes when it ships while the blueprint stays.
Free for macOS, Windows, and Linux. No account, no subscription.
Tied to the definition
Every blueprint knows its work
A blueprint lists the tasks that serve it under Attached tasks, by status, and a template can carry a Tasks section the plugin keeps current. Start a task from the blueprint, from the board, or with /task in the chat, and it already knows what it is for.
- Attached tasks beside every blueprint
- A Tasks section written into the blueprint for you
- A task can serve several blueprints
Structure
Subtasks, links, and checklists
Subtasks nest under their parent and number from it (T-K48.1, T-K48.2), with progress on the parent’s card. Links follow the kinds Jira made familiar (blocks, relates to, duplicates, clones) or your own, and a blocked task says so on the board.
- Ordered, nested subtasks you drag to reorder
- Link types you can extend
- Checklists ticked from the page or a terminal
Types
Task types that are templates
Each type (a task, a bug, a design, a revision, whatever your work needs) has its own icon, colour, and sections, and an optional prefix in its ids, so a bug reads like a bug and a revision like a revision.
Your board, your statuses
Statuses, the columns they fall into, priorities with icons and colours, and milestones with their own properties are all the root’s settings, edited on the plugin’s page and shared with everyone in it.
Views and exports
Filters live in the address, so a link opens the same view. Save any filter as a view for yourself or the team, find your own work under My work, and export the backlog to CSV or an Excel workbook.
How it connects
Work that points at what it builds.
- Blueprints
A task serves blueprints by their permanent id, so a rename never breaks the link, and each blueprint shows its tasks back.
- AI Agent
/taskfiles one from the chat, and an agent works a task end to end: moves it, ticks its checklist, and writes what it learned. - Decisions
A decision can name the task it was made for, so the why sits beside the work.
- Comments
Threads on any task, with reactions and @mentions.
- Git
Tasks are files, committed with the blueprints and everything else.
From the shell
The board, from a terminal
Every action on the board has a command with --json, which is how an agent works a task while the board updates live.
$ eidos backlog set T-R08 --status "In Progress"
✓ backlog/t-r08-mark-a-film-finished-past-its-credits.md T-R08 Mark a film finished past its credits · In Progress [In Progress] medium tomas → B-V63
$ eidos backlog check T-R08 1
[x] #1 Credits marker read from the media pipeline
$ eidos backlog
In Progress (4)
T-K48.2 Report progress every ten seconds from the TV player · In Progress [In Progress] tomas
T-K48 Store the playback position per profile · In Progress [In Progress] high tomas → B-V63
T-R08 Mark a film finished past its credits · In Progress [In Progress] medium tomas → B-V63
T-X65 Watchlist sync across devices · In Progress [In Progress] medium tomas → B-P48
…Write down what you’re making.
Download Eidos MD, open a folder, and start from the framework closest to your work. Everything it gives you can be reshaped later.
Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.