majordomus why diagnose

What the symptoms you recognise imply: the areas they weigh towards and the mechanisms that answer them

Usage

majordomus why diagnose [OPTIONS]

Arguments

argument	value	default	description
--signal	<SIGNALS>	—	A signal id or a moment id; repeat for each one you recognise. Without any, the questionnaire is printed
--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
--audience	<AUDIENCE>	—	Only moments this audience recognises (accepted by every subcommand)
--area	<AREA>	—	Only moments in this operational area (accepted by every subcommand)
--tag	<TAG>	—	Only moments carrying this tag (accepted by every subcommand)
--severity	<SEVERITY>	—	Only moments of this severity (accepted by every subcommand)
--frequency	<FREQUENCY>	—	Only moments of this frequency (accepted by every subcommand)
--lifecycle	<LIFECYCLE>	—	Only moments at this stage of work (accepted by every subcommand)
--capability	<CAPABILITY>	—	Only moments naming this capability of the executable (accepted by every subcommand)
--names-command	<NAMES_COMMAND>	—	Only moments naming this command (accepted by every subcommand)
--featured	flag	—	Only the moments the homepage features (accepted by every subcommand)
--all	flag	—	Include drafts and deprecated moments, not only the public ones (accepted by every subcommand)
-q, --query	<QUERY>	—	Case-insensitive text over identities, titles, hooks, summaries, tags, aliases, signals, examples and bodies (accepted by every subcommand)

Examples

The questionnaire, assembled from the catalogue's own signals

With no selection there is nothing to diagnose, so the questions are printed instead of an empty answer. Every line is a signal a moment declares; nothing here is a list of questions.
```
$ majordomus why diagnose
```
Verified by the example tests: exits 0; prints Which of these happened to you this week?.
What the symptoms you recognise imply

A name is a signal id or a moment id. The answer is counting, not inference: each recommendation carries the moments that produced it, and there is no percentage because there is no model behind one.
```
$ majordomus why diagnose --signal fixture-signal
```
Verified by the example tests: exits 0; prints moment(s) matched, fixture-moment.

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 why diagnose --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.