boardlisted

# Multica: the parts around the command reference ## 0. The command reference is not this skill Multica publishes the canonical CLI skill at [`multica-ai/multica-cli`](https://github.com/multica-ai/multica-cli). It is well maintained — a linter runs its documented commands against the real binary daily, on both the minimum and latest CLI — and it is the authority on the command surface: ```text /plugin marketplace add multica-ai/multica-cli /plugin install multica-cli@multica-cli ``` Go there for: `issue search` semantics, the comment read modes (`--roots-only --summary`, `--thread --tail`, `--recent` capping *threads* not comments, `--compact`, `--full`), the working-directory restriction on `--content-file` / `--description-file` / `--attachment`, when `--parent` is mandatory, the `mention://` side effects, metadata versus custom properties, subscribers, run inspection and cancellation, sub-issue stages, and PR linking. **Do not restate any of that here.** Two skills that describe the same commands will disagree eventually, and the session obeys whichever it read first. This skill covers what that reference does not, and the moment it starts to overlap, the overlap is the bug. If the reference is not installed, say so before operating a board — the safe defaults for mentions, status side effects and comment writes live there. ## 1. Finding the binary in a desktop-app install The reference assumes `multica` is on `PATH` (a package-manager install). With the desktop a