Build a requirement traceability matrix
delivery_traceability_matrixBuild a requirements traceability matrix by mapping Jira issue requirements and acceptance criteria to changed files, then flag gaps for review.
Instructions
Build a requirements traceability matrix: map each requirement and acceptance criterion of a Jira issue to the changed files that implement it, and flag gaps. Fetches the issue itself. For a ready-for-PR verdict use delivery_check_changes.
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": {
"issueKey": "<issueKey>"
},
"name": "delivery_traceability_matrix"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| issueKey | Yes | Jira issue key (e.g. PROJ-123) | |
| repoPath | No | Path to the git repository | . |
| baseBranch | No | Base branch to diff against | origin/main |
| compareRef | No | Branch or commit to compare | HEAD |
| includePrDiff | No | Match requirements against the local diff | |
| includeConfluence | No | Include requirements found in Confluence |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tool | Yes | ||
| issueKey | No | ||
| markdown | Yes | ||
| warnings | Yes | ||
| schemaVersion | Yes |