simulink-requirements

Creates and audits Requirements Toolbox traceability links and coverage reports in MATLAB MBSE projects.

162|31|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/matlab/agent-skills-playground --skill simulink-requirements-matlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: simulink-requirements
Source: https://github.com/matlab/agent-skills-playground/tree/main/demos/mbse-with-agentic-ai/skills/simulink-requirements
Command: npx skills add https://github.com/matlab/agent-skills-playground --skill simulink-requirements-matlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the manual effort and error-prone effort of building and auditing end-to-end traceability between requirements, architecture elements, Simulink/System Composer models, and test cases in MATLAB MBSE.

Core Features & Use Cases

  • Requirements authoring with slreq: create and populate requirement sets (.slreqx), including IDs, hierarchical structure, summaries, descriptions, and rationale.
  • Traceability link management: create and manage Derive, Implement, Verify, Refine, and Relate links across requirement artifacts and model/test artifacts, then save all cross-artifact changes.
  • Traceability auditing & reporting: check link health (broken/orphan links), verify coverage (SR coverage by Verify links), and export traceability reports (including guidance for Excel workflows).
  • Use Case: when you decompose stakeholder needs into system requirements, implement those system requirements from architecture components/blocks, and verify them with test cases, use this Skill to generate consistent link structures and coverage/health reports.

Quick Start

Use this skill when your MBSE task is to set up or troubleshoot slreq requirements and traceability links (for example, when you need Verify coverage or broken-link diagnostics) in your MATLAB MBSE project.

Frequently Asked Questions about simulink-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate requirements traceability link creation in MATLAB MBSE projects?

Automate requirements traceability by using slreq workflows to create Derive, Implement, Verify, Refine, and Relate links across .slreqx artifacts, model elements, and test cases. This eliminates manual effort and ensures consistent cross-artifact link structures.

How do I check link health and find broken traceability links in Simulink?

Check link health in Simulink by using slreq.load and link-set utilities to audit traceability for broken or orphan links. The skill analyzes link robustness and provides diagnostics for conditional .slmx generation issues.

Can I generate verification coverage reports for requirements linked to test cases?

Generate verification coverage reports by analyzing Verify links between requirement artifacts and test cases. The skill queries outLinks and inLinks to calculate SR coverage and exports traceability reporting, including guidance for Excel workflows.

Does this support creating hierarchical requirement sets with IDs and descriptions?

Creating hierarchical requirement sets with slreq supports defining IDs, summaries, descriptions, and rationale within .slreqx files. This enables structured requirements authoring for decomposing stakeholder needs into system requirements.

What is the best way to query traceability links across .slreqx and .slmx artifacts?

Query traceability links across artifacts using scripted analysis patterns with slreq.load and link-set utilities. The skill handles outLinks and inLinks traversal to audit cross-artifact link semantics and verify coverage across MBSE projects.

Why does conditional .slmx generation fail when saving traceability links?

Conditional .slmx generation fails when saving cross-artifact traceability links due to robustness issues in link-set utilities. The skill provides guidance around these limitations to ensure all cross-artifact changes are saved correctly.