simulink-requirementslisted
Install: claude install-skill matlab/agent-skills-playground
# MATLAB Requirements Toolbox — Requirements & Traceability
This skill covers everything in the `slreq` API: creating and reading requirements,
managing traceability links, checking verification coverage, allocating requirements
to architecture components, and auditing link health.
For architecture phases (System Composer models, functional decomposition,
functional→physical allocation) see the `mbse-architecture` skill.
See `references/api-quickref.md` in this skill folder for a compact one-page API reference.
---
## The Two File Types
| Extension | Class | Role |
|---|---|---|
| `.slreqx` | `slreq.ReqSet` | Stores requirements (text, hierarchy) |
| `.slmx` | `slreq.LinkSet` | Stores traceability links **outgoing from a source artifact** |
### When a `.slmx` file is created
slreq writes a `.slmx` file **only when its companion artifact is the source of at least one link.** The LinkSet is keyed on the source artifact, not the destination.
- `MyReqs~slreqx.slmx` appears only if some link's source is a requirement in `MyReqs.slreqx` (e.g., `slreq.createLink(srcReq, destReq)` where `srcReq` lives in `MyReqs`)
- `MyModel~mdl.slmx` appears only if some link's source is a model element in `MyModel.slx` (typical: `slreq.createLink(component, req)` with Type `Implement` — the component is the source)
An artifact that is only ever a link *destination* never gets a paired `.slmx`. In a typical MBSE project:
| Artifact | Gets a `.slmx`? | Why |
|---|---|---|
| `StakeholderNee