Supersede element
Supersede an element: set an invalid status of its type and optionally name a successor (relation with meaning succession, written into the successor’s file). There is no delete (D-045).
Command element.supersede. Writes files in the working tree, never to Git. It is refused while the workspace is read-only. Sets an invalid status of the metamodel, and no change can be checked against a missing or faulty metamodel.
| Field | Type | Required | Description |
|---|---|---|---|
ref |
elementRef |
yes | UUID, short ID or identifier (e.g. SR-036), any case; several matches give ref.ambiguous. |
status |
keyOrName |
yes | Key or display name of a status of the metamodel, in any case; the key is written. It must be a status of the element’s type that the metamodel marks invalid (#306). |
successor |
elementRef |
no | UUID, short ID or identifier (e.g. SR-036), any case; several matches give ref.ambiguous. |
relation |
key |
no | Relation kind with meaning succession to write from the successor; needed only when more than one fits the types and the successor does not already have the relation under exactly one of them. |
Output
Section titled “Output”| Field | Type | Required | Description |
|---|---|---|---|
files |
array of string |
yes | |
problems |
array of problem |
no |
In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command Supersede element.
reqseq element supersede, with --json for the output as JSON. Its help:
Usage: reqseq element supersede <ref> <status> [options]
Supersede an element: set an invalid status of its type and optionally name asuccessor (relation with meaning succession, written into the successor's file).There is no delete (D-045).
Arguments: ref status Key or display name of a status of the metamodel, in any case; the key is written. It must be a status of the element's type that the metamodel marks invalid (#306).
Options: --ref <value> instead of the argument <ref> --status <value> instead of the argument <status> --successor <value> --relation <value> Relation kind with meaning succession to write from the successor; needed only when more than one fits the types and the successor does not already have the relation under exactly one of them. --input <json|@file|-> command input as JSON: inline, from a file, or from standard input --workspace <path> workspace root (default: nearest folder upwards with reqseq-workspace.yaml) --json print exactly the command output as JSON --yaml print the whole command output as YAML, problems one per line -h, --help show helpPOST /v1/commands/element.supersede on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.
Tool element_supersede of the MCP server (reqseq mcp), with the input as its arguments.