Where Used
where_usedTraverse the lockfile dependency graph to report every parent that consumes an item, revealing the full blast radius for impact analysis. Optionally surface immediate direct parents separately.
Instructions
Where-used / impact analysis (issue #142, C3; MULTI_AGENT.md §9): traverse the
lockfile depends_on graph and report every parent that CONSUMES an item — the
blast radius, so exactly those parents re-dispatch when the item changes. The
lockfile records edges consumer -> consumed (lid depends_on housing); where-used
is the reverse reachability of the item (everything that reaches it).
lockfile: path to the lockfile (the JSON assembly_lock wrote). item: the item / component id to query. direct: if true, also surface only the immediate mates separately.
Returns {item, where_used (the full transitive blast radius), direct (the §9 immediate-neighbour layer)} — an unknown item fails loudly, never a silent empty set.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"lockfile": "<lockfile>",
"item": "<item>"
},
"name": "where_used"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| item | Yes | ||
| direct | No | ||
| lockfile | Yes | ||
| workspace | No | Run this call in this named workspace |