spec-editor source

Requirement sources: add, import, sync, listen, list.

Usage

spec-editor source [OPTIONS] COMMAND [ARGS]...

Subcommands

Subcommand	Description
add	Analyze requirements from a file, inline text, or a channel, and create SRC elements.
cleanup	Delete closed sources whose knowledge lives in confirmed elements.
import	Import an OpenSLO description as metrics aspect elements.
list	List sources: id, title, status, tags.
listen	Start a Telegram hook for receiving requirements.
sync	Bidirectional sync with all configured tracker channels.

spec-editor source add

Analyze requirements from a file, inline text, or a channel, and create SRC elements.

By file:        spec-editor source add -p . -f new_features.txt
Inline text:    spec-editor source add -p . -t "Users must login via SSO"
By channel:     spec-editor source add -p . --channel jira:SPEC
Dry-run only:   spec-editor source add -p . -f new_features.txt --dry-run

Usage

spec-editor source add [OPTIONS]

Options

Option	Type	Default	Description
--path, -p	path	.	Project path (default: current directory)
--file, -f	path		Requirements file to analyze
--text, -t	text		Inline requirement text to analyze
--channel	text		Pull one configured channel’s items and analyze them — ‘type’ or ‘type:name’ (e.g. ‘telegram’ or ‘jira:SPEC’)
--dry-run	flag		Analyze only — do not write any SRC elements
--json	flag		Output as JSON

spec-editor source cleanup

Delete closed sources whose knowledge lives in confirmed elements.

Usage

spec-editor source cleanup [OPTIONS]

Options

Option	Type	Default	Description
--path, -p	path	.	Project path (default: current directory)
--approve	flag		Owner approval: delete the batch (default: dry-run)
--json	flag		Emit JSON

spec-editor source import

Import an OpenSLO description as metrics aspect elements.

Re-running with the same file updates the elements it previously created instead of duplicating them; manually-created metrics elements are left untouched.

spec-editor source import -p . --format openslo slo.yaml

Usage

spec-editor source import [OPTIONS] OPENSLO_FILE

Arguments

Argument	Required
OPENSLO_FILE	yes

Options

Option	Type	Default	Description
--format	one of openslo		Source file format Required.
--path, -p	path	.	Project path (default: current directory)
--dry-run	flag		Show what would be imported without writing
--json	flag		Output as JSON

spec-editor source list

List sources: id, title, status, tags.

Usage

spec-editor source list [OPTIONS]

Options

Option	Type	Default	Description
--path, -p	path	.	Project path (default: current directory)
--json	flag		Emit JSON

spec-editor source listen

Start a Telegram hook for receiving requirements.

Live mode:        spec-editor source listen
Fetch history:    spec-editor source listen --fetch-since 2026-01-01

History + limit: spec-editor source listen –fetch-since 2026-01-01 –fetch-limit 500

Usage

spec-editor source listen [OPTIONS]

Options

Option	Type	Default	Description
--path, -p	path	.	Project path (default: current directory)
--config, -c	path		Path to hooks.yaml (default: <path>/hooks.yaml)
--fetch-since	text		Load history from date (YYYY-MM-DD). No flag — live mode
--fetch-limit	integer	200	Max messages when loading history (default: 200)
--json	flag		Output as JSON

spec-editor source sync

Bidirectional sync with all configured tracker channels.

Pulls new cards → creates spec elements. Pushes element changes → updates Planka/Trello/Jira cards. Safe for polling — idempotent, respects timestamps.

Usage

spec-editor source sync [OPTIONS]

Options

Option	Type	Default	Description
--path, -p	path	.	Project path
--dry-run	flag		Show what would be synced without syncing
--json	flag		Output as JSON