spec-editor breakpoint (Pro)

Pro command. Available with the spec-editor Pro plugin; the open core does not include it.

Work with breakpoints: sources created by clicking an element of the running product, bound to the requirement of that element.

Usage

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

Subcommands

Subcommand	Description
`bind`	Show binding candidates for a breakpoint, or confirm/reject targets.
`chat`	Converse with the Formulator (requirement mode) about one breakpoint.
`formulate`	Finalise the latest chat draft into the breakpoint itself.
`migrate-lifecycle`	Normalize stored breakpoints to exactly one lifecycle_state.
`replay`	Generate a Playwright replay bundle (check spec + demo spec + fixture) for one breakpoint: navigate to its captured screen, target its captured element – for the Verifier’s post-fix re-check and…
`show`	Show one breakpoint’s full detail (attributes, captures, snapshot, content).

spec-editor breakpoint bind

Show binding candidates for a breakpoint, or confirm/reject targets.

With neither flag, shows ranked fallback candidates (route/title/text/ entity signals) and any declared-but-missing spec-ids. --confirm/ --reject write the breakpoint’s about relationship — human-only (rejected with an error if run as an agent identity).

spec-editor breakpoint bind <id> -p .
spec-editor breakpoint bind <id> -p . --confirm <id>,<id>
spec-editor breakpoint bind <id> -p . --reject <id>

Usage

spec-editor breakpoint bind [OPTIONS] BREAKPOINT_ID

Arguments

Argument	Required
`BREAKPOINT_ID`	yes

Options

Option	Type	Default	Description
`--path`, `-p`	path	`.`	Path to project (or SPEC_EDITOR_PROJECT)
`--confirm`	text		Comma-separated element ids to confirm as `about` targets
`--reject`	text		Comma-separated element ids to remove from `about`
`--json`	flag		Output as JSON

spec-editor breakpoint chat

Converse with the Formulator (requirement mode) about one breakpoint.

spec-editor breakpoint chat <id> "I need an export-to-CSV button" -p .

Usage

spec-editor breakpoint chat [OPTIONS] BREAKPOINT_ID MESSAGE

Arguments

Argument	Required
`BREAKPOINT_ID`	yes
`MESSAGE`	yes

Options

Option	Type	Default	Description
`--path`, `-p`	path	`.`	Path to project (or SPEC_EDITOR_PROJECT)
`--by`	text	`human:cli`	Speaker identity (default ‘human:cli’)
`--json`	flag		Output as JSON

spec-editor breakpoint formulate

Finalise the latest chat draft into the breakpoint itself.

Human-only: the command is rejected if --by does not start with human:. No requirements are created and no gate is requested. The breakpoint stays in draft with its dialogue marked as formulated, for the analysis team to pick up.

Usage

spec-editor breakpoint formulate [OPTIONS] BREAKPOINT_ID

Arguments

Argument	Required
`BREAKPOINT_ID`	yes

Options

Option	Type	Default	Description
`--path`, `-p`	path	`.`	Path to project (or SPEC_EDITOR_PROJECT)
`--by`	text	`human:cli`	Approver identity, MUST start with ‘human:’ (default ‘human:cli’)
`--json`	flag		Output as JSON

spec-editor breakpoint migrate-lifecycle

Normalize stored breakpoints to exactly one lifecycle_state.

The data half of the field’s migration — it moves a record still carrying the legacy lifecycle attribute (or none at all) under the current name, keeping the state it already reads as. Idempotent: a second run rewrites nothing. The schema half — declaring the attribute in the project’s methodology.yaml — is spec-editor migrate.

spec-editor breakpoint migrate-lifecycle -p .

Usage

spec-editor breakpoint migrate-lifecycle [OPTIONS]

Options

Option	Type	Default	Description
`--path`, `-p`	path	`.`	Path to project (or SPEC_EDITOR_PROJECT)
`--json`	flag		Output as JSON

spec-editor breakpoint replay

Generate a Playwright replay bundle (check spec + demo spec + fixture) for one breakpoint: navigate to its captured screen, target its captured element – for the Verifier’s post-fix re-check and for a “before/after” film. Web-only: errors if the breakpoint has no screen.route.

spec-editor breakpoint replay <id> -p . --base-url http://localhost:3000

Usage

spec-editor breakpoint replay [OPTIONS] BREAKPOINT_ID

Arguments

Argument	Required
`BREAKPOINT_ID`	yes

Options

Option	Type	Default	Description
`--path`, `-p`	path	`.`	Path to project (or SPEC_EDITOR_PROJECT)
`--base-url`	text		Base URL of the running product (overrides local.yaml: breakpoints.replay_base_url).
`--out-dir`, `-o`	directory		Output directory (default packages/e2e/replays/<id>/).
`--json`	flag		Output as JSON

spec-editor breakpoint show

Show one breakpoint’s full detail (attributes, captures, snapshot, content).

spec-editor breakpoint show <id> -p .

Usage

spec-editor breakpoint show [OPTIONS] BREAKPOINT_ID

Arguments

Argument	Required
`BREAKPOINT_ID`	yes

Options

Option	Type	Default	Description
`--path`, `-p`	path	`.`	Path to project (or SPEC_EDITOR_PROJECT)
`--json`	flag		Output as JSON