Skip to main content

​
Overview

Analyze blast radius of changing an artifact. Uses BFS by depth to classify impact: depth 1 = WILL_BREAK, depth 2 = LIKELY_AFFECTED, depth 3 = MAY_NEED_REVIEW. When code intelligence is available, uses call graph for deeper analysis. This tool helps you understand the consequences of modifying a requirement, use case, or any other artifact by traversing the traceability graph and identifying all dependent or dependency artifacts.

​
Parameters

​
artifact_id
string
required
The artifact ID to analyze (e.g. REQ-AUTH-001, UC-003)
​
direction
enum
required
Direction to traverse:
  • upstream - What does this depend on?
  • downstream - What depends on this?
​
maxDepth
number
default:"3"
Maximum traversal depth

​
Response

​
artifact
object
The root artifact being analyzed
​
id
string
Artifact ID
​
type
string
Artifact type
​
title
string
Artifact title
​
direction
string
Traversal direction (upstream or downstream)
​
maxDepth
number
Maximum depth traversed
​
risk
enum
Overall risk level:
  • HIGH - More than 5 direct dependents or 20 total affected
  • MEDIUM - More than 2 direct dependents or 10 total affected
  • LOW - Fewer dependents
​
totalAffected
number
Total number of artifacts affected across all depths
​
byDepth
object
Artifacts grouped by depth level
​
[depth]
object
​
label
string
Impact label: WILL_BREAK, LIKELY_AFFECTED, or MAY_NEED_REVIEW
​
count
number
Number of artifacts at this depth
​
artifacts
array
​
id
string
Artifact ID
​
type
string
Artifact type
​
title
string
Artifact title
​
file
string
Source file path
​
viaRelationship
string
Relationship type connecting to this artifact
​
affectedStages
string[]
List of pipeline stages affected by this change
​
codeImpact
object
Code intelligence enrichment (when available)
​
directSymbols
array
Code symbols directly related to the artifact
​
name
string
Symbol name
​
file
string
File path
​
type
string
Symbol type (function, class, etc.)
​
transitiveCallers
string[]
Functions that call the related symbols
​
totalCallChainDepth
number
Total depth of the call chain

​
Impact depth labels

  • Depth 1 (WILL_BREAK): Direct dependencies that will definitely be affected
  • Depth 2 (LIKELY_AFFECTED): Second-degree connections that will likely need updates
  • Depth 3 (MAY_NEED_REVIEW): Third-degree connections that may need review

​
Examples

​
Analyze downstream impact of a requirement

{
  "artifact_id": "REQ-AUTH-001",
  "direction": "downstream"
}

​
Check upstream dependencies with limited depth

{
  "artifact_id": "UC-LOGIN-003",
  "direction": "upstream",
  "maxDepth": 2
}

​
Assess blast radius before major changes

{
  "artifact_id": "API-USER-MGMT",
  "direction": "downstream",
  "maxDepth": 4
}

​
TypeScript types

interface ImpactArgs {
  artifact_id: string;
  direction: "upstream" | "downstream";
  maxDepth?: number;
}

interface AffectedArtifact {
  id: string;
  type: string;
  title: string;
  file: string;
  viaRelationship: string;
}

const DEPTH_LABELS: Record<number, string> = {
  1: "WILL_BREAK",
  2: "LIKELY_AFFECTED",
  3: "MAY_NEED_REVIEW",
};

​
See also

  • sdd_context - Get full context including relationships
  • sdd_trace - Trace complete traceability chain

Build docs developers (and LLMs) love

Get started for freeTalk to us