Show related elements

All children of a set of parents, or all parents of a set of requirements, each once, optionally up to a depth; one page at a time, total counts all.

Command trace.related. Reads the workspace and changes no file.

Input

Field	Type	Required	Description
`refs`	array of `elementRef`	yes
`direction`	one of `"children"`, `"parents"`	yes
`maxDepth`	`integer`	no
`view`	`view`	no	`core`, a variant ID, or absent for all. A variant’s view: the core requirements it neither excludes nor replaces, plus those valid for it; elements without validity property are in every view (SR-043).
`limit`	`integer`	no	Elements of the page; total counts all. Default: `200`.
`offset`	`integer`	no	Elements skipped before the page, in the order of the list (by distance from the selection). Default: `0`.

Output

Field	Type	Required	Description
`elements`	array of `element`	yes
`total`	`integer`	yes
`incomplete`	`incomplete`	no	True when a result is incomplete because targets are in repositories that are not available locally (SR-006 AK2, SR-036 AK3).

App

In the command prompt (Ctrl+Shift+P, macOS ⌘⇧P): the command Show related elements.

CLI

reqseq trace related, with --json for the output as JSON. Its help:

Usage: reqseq trace related <direction> [options]

All children of a set of parents, or all parents of a set of requirements, each
once, optionally up to a depth; one page at a time, total counts all.

Arguments:
  direction               one of: children, parents

Options:
  --direction <value>     instead of the argument <direction>
  --refs <value>          repeatable
  --max-depth <number>
  --view <value>
  --limit <number>        Elements of the page; total counts all. default: 200
  --offset <number>       Elements skipped before the page, in the order of the
                          list (by distance from the selection). default: 0
  --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 help

API

POST /v1/commands/trace.related on the local API (reqseq serve api), with the input as the JSON body; the answer is the output.

MCP

Tool trace_related of the MCP server (reqseq mcp), with the input as its arguments.