vissue
A plan is a directed acyclic graph of Org headings. One file per project holds the nodes. No daemon, no database, no server.
What it is#
An issue is a top-level Org heading. The file is the database: every command parses the files it needs, every mutation rewrites one file under a lock. The tracker diffs, merges, and greps like the repository it lives in, and a command-line tool, a Model Context Protocol server, and Emacs all read the same bytes.
<root>/Software/<project>/issues.org
Four properties carry the plan. :PARENT: groups work under it. :BLOCKED_BY:
is the partial order. ready is the frontier anything can pick up. claim is
the lock that stops two workers taking the same node.
Where to go#
Getting started takes an empty directory to a tracked backlog two workers share. Start here.
How-to answers a task at a time: filter, share a backlog, watch for changes, fold in work found elsewhere.
Reference is the command surface, the properties, the configuration, and the export schema.
Explanation is why the file is the database, why the order is a partial order, and what the citations do and do not justify.
Emacs is the other reader of the same file: the agenda, tag search, and
id:links, with nothing installed.
Install#
$ cargo install vissue-cli
$ cargo install vissue-mcp # the MCP server, same version
Tagged releases carry prebuilt archives and a shell installer. Shell completions and a manual page come out of the binary itself:
$ vissue completions zsh > ~/.zfunc/_vissue
$ vissue man > ~/.local/share/man/man1/vissue.1