#+title: vissue
#+description: A plan is a directed acyclic graph of Org headings.
#+options: toc:nil num:nil
#+begin_export rst
.. raw:: html
vissue
What does this node stand on, and who agrees?
A plan is a directed acyclic graph of Org headings.
Org mode
Plain text
CLI + MCP
#+end_export
* Install
#+begin_src console
$ cargo install vissue-cli
$ cargo install vissue-mcp
$ cargo install vissue-hud # summonable overlay, optional
#+end_src
Seven crates ship at one version. Tagged releases also carry prebuilt
archives and a shell installer. Completions and the manual page come
out of the binary:
#+begin_src console
$ vissue completions zsh > ~/.zfunc/_vissue
$ vissue man > ~/.local/share/man/man1/vissue.1
#+end_src
* First minute
#+begin_src console
$ mkdir -p /tmp/demo && cd /tmp/demo
$ vissue create --project parser "Reject a manifest with no header"
parser-k29f TODO [#C] Reject a manifest with no header
file: /tmp/demo/Software/parser/issues.org
#+end_src
That file is the database: one Org heading, ordinary text, nothing beside it.
The [[file:getting-started.org][tutorial]] continues from this issue.
Wire a coding seat through =ljos-mcp= on the [[file:harness.org][Harness]] how-to.
#+begin_export rst
.. toctree::
:maxdepth: 1
:caption: Guides
:hidden:
getting-started
howto
harness
reference
control
explanation
emacs
org-syntax
ecosystem
seat
#+end_export