Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →matlab/generate-requirement-drafts
Generates draft requirements from Simulink models.
Passed 5 of 11 test cases with the skill, and 6 of 11 without it.
and 1 more in the full report
4 fixed5 passed either way6 still failing7 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
Provide the MATLAB code snippet to finalize and save a newly generated requirement set and its associated link set for InverterControl.slx.
| Checked | Without skill | With skill |
|---|---|---|
| The code invokes save on the requirement set object. | Passed | Passed |
| The code queries slreq.find with Type equal to LinkSet and saves each link set. | Missed | Passed |
The instructions your model reads when the skill loads.
Generate draft requirements from Simulink models using the richest artifact the environment supports. All outputs are drafts requiring human review and approval before baselining.
.slreqx or .yaml requirements artifactstesting-simulink-models skill<Model>_Requirements.slreqx or <model>_requirements.yamlREQ_<SYSTEM>_001, REQ_<SYSTEM>_002, … — use one consistent project-wide prefix with sequential integers across all requirements, even when they derive from different subsystems. Do not switch to per-subsystem prefixes or hierarchical decimal numbering (e.g. CB-1.1, TP-1.1)..slreqx or .yaml files already exist"draft" in Keywords (slreq) or status: Draft + keywords: [draft] (YAML)Requirements must express behavioral intent (WHAT the system shall do), not restate model topology (HOW it is implemented). Put the WHY in Rationale. Use EARS (Easy Approach to Requirements Syntax) patterns:
Choose the pattern that best fits the model behavior:
| Pattern | Template | When to Use |
|---|---|---|
| Ubiquitous | The <system> shall <response>. | Always-on behavior, invariants |
| Event-driven | When <trigger>, the <system> shall <response>. | A momentary trigger causes a one-time response: input events, entering a Stateflow state (the transition itself) |
| State-driven | While <state>, the <system> shall <response>. | Behavior that holds continuously while in a Stateflow state or mode — the ongoing response, not the entry transition |
| Unwanted behavior | If <condition>, then the <system> shall <response>. | Error handling, safety limits, saturation |
| Optional feature | Where <feature>, the <system> shall <response>. | Variant subsystems, configurable features |
| Combined | While <state>, when <trigger>, the <system> shall <response>. | State + event combinations |
test cases passed, vs 6 / 11 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.