majordomus product show

One feature in full: what it is made of, resolved, and everything derived from that

Usage

majordomus product show [OPTIONS] <ID>

Arguments

argument	value	default	description
<ID>	<ID>	required	The feature's id, which is also its slug and its route
--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)
--format	text \| json	text	Output shape (accepted by every subcommand) `text` — Lines for a person `json` — One JSON document, deterministic
--featured	flag	—	Only the features the homepage shows (accepted by every subcommand)
--all	flag	—	Include drafts and deprecated features, not only the stable ones (accepted by every subcommand)
--area	<AREA>	—	Only features serving this operational area of the why catalogue (accepted by every subcommand)
--module	<MODULE>	—	Only features made of this capability module (accepted by every subcommand)
--names-command	<NAMES_COMMAND>	—	Only features made of this shell command (accepted by every subcommand)
--surface	<SURFACE>	—	Only features exposed through this surface: cli, api, mcp, cockpit or docs (accepted by every subcommand)
-q, --query	<QUERY>	—	Case-insensitive text over identities, titles, headlines, summaries, tags and bodies (accepted by every subcommand)

Examples

One feature, with everything derived from what it names

The record as its file declares it, then what nobody authored: the capabilities of its modules with their tools and routes, the commands with their summaries, the objects of its kinds counted, the rules with their class, the documents, the decisions, the claims with their status, the moments it answers, and the interfaces all of that adds up to.
```
$ majordomus product show fixture-feature
```
Verified by the example tests: exits 0; prints fixture-feature, surfaces, derived.

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 product show --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.