A real backlog, made of markdown.

Boards, task types, subtasks, links, and checklists, with every task a file in your folder. Each task serves a blueprint by its permanent id. When the work ships, the task closes and the blueprint stays.

Download free Quick start

Free for macOS, Windows, and Linux. No account, no subscription.

The backlog board with To Do, In Progress, In Review, and Done columns. Each card shows its type icon, its id, its priority, who it is assigned to, and the blueprint it serves. — Each card names the blueprint it serves, and the column is the task’s status.

Tied to the definition

Every blueprint knows its work

Each blueprint lists its tasks by status under Attached tasks, and a template can carry a Tasks section the plugin keeps current. Start a task from the blueprint, the board, or /task in the chat, and it already knows what it’s for.

Attached tasks beside every blueprint
A Tasks section written into the blueprint for you
A task can serve several blueprints

A blueprint at its Out of Scope section with a comment thread, and the side panel listing the tasks attached to it, grouped To Do, In Progress, and In Review.

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 use the kinds Jira made familiar (blocks, relates to, duplicates, clones) or your own. 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

A task page showing its implementation plan, three subtasks with their statuses, and links: it blocks one task and relates to another.

Types

Task types that are templates

Make the types your work needs, such as a task, a bug, or a revision. Each has its own icon, colour, sections, and optional id prefix, so a bug reads like a bug.

The Task types settings: Task, Bug, and Design, each with an icon, and the sections the Task type holds: Description, Checklist, Implementation Plan, and Implementation Notes.

Your board, your statuses

Statuses and their columns, priorities with icons and colours, and milestones with their own properties are project settings. You edit them on the plugin’s page, and the whole project shares them.

Views and exports

Filters live in the address, so a link opens the same view. Save a filter as a view for you or the team, find your work under My work, and export to CSV or Excel.

How it connects

Work that points at what it builds.

Blueprints
A task serves blueprints by permanent id, so a rename never breaks the link. Each blueprint lists its tasks back.
AI Agent
/task files one from the chat. An agent can work a task end to end: move it, tick its checklist, and write what it learned.
Comments
Threads on any task, with reactions and @mentions.
Git
Tasks are files, committed with everything else.

From the shell

The board, from a terminal

Every board action has a command with --json. That’s 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
…

Read the Backlog docs

Write down what you’re making.

Download Eidos MD, open a folder, and start from the framework closest to your work. You can reshape it all later.

Download free Quick start

Free for macOS, Windows, and Linux. Your files stay plain text in a folder you own.