majordomus capabilities schema

The canonical input or output JSON Schema of one capability

Usage

majordomus capabilities schema [OPTIONS] <ID>

Arguments

argument	value	default	description
<ID>	<ID>	required	The canonical id
--side	input \| output	input	Input or output `input` — The schema of the input `output` — The schema of the output
--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

The canonical output schema of a capability

The JSON Schema the MCP and OpenAPI projections are derived from; `--side input` prints the schema of what the capability accepts.
```
$ majordomus capabilities schema objects.get --side output
```
Verified by the example tests: exits 0; prints one JSON document carrying /title.

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 schema --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.