majordomus capabilities list

Every capability, one line each, with its projections

Usage

majordomus capabilities list [OPTIONS]

Arguments

argument	value	default	description
--kind	<KIND>	—	Only this kind: query or resource
--exposure	<EXPOSURE>	—	Only capabilities exposed through this projection: mcp, http or cli
--format	text \| json	text	Output shape `text` — Lines for a person `json` — One JSON document, deterministic
--repo	<PATH>	—	Start the search for the repository root here (default: the current directory) (accepted by every subcommand)
--discovery	vcs \| filesystem	vcs	How declarative files are enumerated (accepted by every subcommand) `vcs` — Tracked files, through the version-control index (the layer's contract) `filesystem` — A walk of the work tree with the same glob semantics; untracked files included
--strict	flag	—	Refuse to proceed when any file of the layer carries an error diagnostic (accepted by every subcommand)
--share	<DIR>	—	The tool distribution's share directory (kinds.yaml, schemas/); default: $MAJORDOMUS_SHARE, then the repository's own share/, then the one beside the executable (accepted by every subcommand)

Examples

Which capabilities the command line itself dispatches to

One line per capability exposed through the `cli` projection, with the projections of each. The registry answers this; no list of capabilities is written in the command line's own declaration.
```
$ majordomus capabilities list --exposure cli
```
Verified by the example tests: exits 0; prints capabilities.list, capabilities.describe.
Every capability as one JSON document

The whole registry for a script: each capability with its kind, its provenance and every projection it has.
```
$ majordomus capabilities list --format json
```
Verified by the example tests: exits 0; prints one JSON document carrying /capabilities.

Where this comes from

Declared once in apps/majordomus-cli/src/cli.rs: clap for the structure, typed Rust metadata beside it for the examples. This page, majordomus capabilities list --help, docs/generated/cli.md and docs/generated/cli.json are projections of that one declaration.

The whole command line on one page: the registry's command-line page. The task lifecycle (init, start, finish, doctor, ...) belongs to the shell tool, a different program: Commands and its specification.