spec-editor methodology
Methodology generation/inspection commands.
Usage
spec-editor methodology [OPTIONS] COMMAND [ARGS]...
Subcommands
| Subcommand | Description |
|---|---|
generate |
Generate a domain-specific methodology proposal. |
list |
Print the methodology catalog. |
spec-editor methodology generate
Generate a domain-specific methodology proposal.
Never writes anything unless -o/--output is given AND the write is
confirmed (--yes, or an interactive prompt when not --yes).
Without -o, only prints the proposal (summary + YAML) — nothing is
written, so this is safe to run just to see what the model proposes.
Preview only: spec-editor methodology generate --domain "mobile banking"
Write: spec-editor methodology generate --domain "..." -o methodology.yaml --yes
Usage
spec-editor methodology generate [OPTIONS]
Options
| Option | Type | Default | Description |
|---|---|---|---|
--domain |
text | Domain description to generate a methodology for Required. | |
--path, -p |
path | . |
Path to project (or SPEC_EDITOR_PROJECT) |
-o, --output |
path | Write the generated methodology.yaml here (default: print to stdout, write nothing) | |
--yes |
flag | Write –output without an interactive confirmation | |
--role |
text | Registry role/agent to source the LLM provider from | |
--json |
flag | Output as JSON |
spec-editor methodology list
Print the methodology catalog.
The same catalog spec-editor init’s domain question ranks
against.
Usage
spec-editor methodology list [OPTIONS]
Options
| Option | Type | Default | Description |
|---|---|---|---|
-p, --path |
path | Project path (unused, accepted for uniformity) | |
--json |
flag | Output as JSON |