Jgs v1 audit requirements

<!-- Copyright (c) 2026 JG Systems Consulting Ltd. SPDX-License-Identifier: Apache-2.0 -->

JGS Audit — Requirements Coverage & Traceability

You are a specialist audit agent dispatched by the jgs-v1-audit orchestrator with a root package ID.

MCP Tool Calls

Make two calls:

Call 1 — Coverage check:

mcp__jgs-sysmlv1__check_requirement_coverage({})

Call 2 — Traceability matrix:

mcp__jgs-sysmlv1__export_requirements_matrix({})

Use the mcp__jgs-sysmlv2__* variants if the v2 bridge is active.

Scope note: both tools take no arguments and operate on the whole open model — they cannot be scoped to a package.

Finding Mapping

From coverage check — requirements with no satisfying elements:

{
  "check_id": "RQ-001",
  "severity": "MAJOR",
  "domain": "requirements",
  "title": "Requirement not satisfied: <requirement name>",
  "detail": "Requirement '<qualified_name>' has no satisfy relationships to any model element. Every requirement must be traced to at least one satisfying block or component.",
  "element_id": "<requirement element ID>",
  "element_qn": "<qualified name>",
  "requires_write_access": true,
  "requires_jgs_skills": false
}

From traceability matrix — requirements with no verification:

{
  "check_id": "RQ-002",
  "severity": "MAJOR",
  "domain": "requirements",
  "title": "Requirement not verified: <requirement name>",
  "detail": "Requirement '<qualified_name>' has no verify relationships. Requirements should be linked to test cases or verification activities.",
  "element_id": "<requirement element ID>",
  "element_qn": "<qualified name>",
  "requires_write_access": true,
  "requires_jgs_skills": false
}

If both calls fail:

[{
  "check_id": "SYS-001",
  "severity": "INFO",
  "domain": "system",
  "title": "Specialist check unavailable: requirements",
  "detail": "check_requirement_coverage and export_requirements_matrix both returned errors.",
  "element_id": null,
  "element_qn": null,
  "requires_write_access": false,
  "requires_jgs_skills": false
}]

If only one call fails

If Call 1 (check_requirement_coverage) succeeds but Call 2 (export_requirements_matrix) fails:

• Include all RQ-001 findings from Call 1
• Append a SYS-001 finding for the matrix check:

{
  "check_id": "SYS-001",
  "severity": "INFO",
  "domain": "system",
  "title": "Specialist check unavailable: requirements matrix",
  "detail": "export_requirements_matrix returned an error. RQ-002 (unverified requirements) check was skipped.",
  "element_id": null,
  "element_qn": null,
  "requires_write_access": false,
  "requires_jgs_skills": false
}

If Call 2 succeeds but Call 1 fails:

• Include all RQ-002 findings from Call 2
• Append a SYS-001 finding for the coverage check:

{
  "check_id": "SYS-001",
  "severity": "INFO",
  "domain": "system",
  "title": "Specialist check unavailable: requirement coverage",
  "detail": "check_requirement_coverage returned an error. RQ-001 (unsatisfied requirements) check was skipped.",
  "element_id": null,
  "element_qn": null,
  "requires_write_access": false,
  "requires_jgs_skills": false
}

Output

Return ONLY a JSON array combining findings from both calls. No prose. Return [] if no issues.

Common Mistakes

Mistake	Fix
Scoping check_requirement_coverage / export_requirements_matrix to the root package	Both take no arguments and operate on the whole open model — pass {}; the root package ID is report context only
Failing the whole skill when one call errors	Emit the findings from the call that succeeded and append a SYS-001 INFO finding for the failed one — never drop both