Skip to content
Vector Stream Systems logo Vector Stream Systems

Free plugin · Claude Code

MBSE Requirements, as a Claude Code skill

One command and your agent stops writing requirements that read well and fail review. The five EARS patterns, permanent ID schemes, a banned-word list, and a repair workflow that shows you the diff rather than rewriting your specification behind your back.

Install it free See the full pack ($29)

Free and stays free · No account · Nothing to run

Install

Two commands, inside Claude Code

These are typed at the Claude Code prompt, not in your shell. A marketplace in Claude Code is simply a Git repository it reads a manifest from, so the first command points it at ours and the second installs from it.

1. Add the marketplace

/plugin marketplace add radsilent/mbe3d-skills

Claude Code fetches the repository and reports the marketplace name it found, vector-stream-systems, along with the plugins in it.

2. Install the skill

/plugin install mbse-requirements@vector-stream-systems

Claude Code shows you what the plugin contains before it enables anything. This one is a single skill: no commands, no hooks, no MCP servers, and no executables. Confirm, and it is available in your next message.

3. Use it

There is nothing to invoke. The skill declares what it is for, and your agent reaches for it when the work matches: writing a shall statement, reviewing a specification, assigning requirement IDs, splitting a compound requirement. Ask for something like:

Review the requirements in docs/srs.md and tell me which ones
would fail a design review, and why.

Browsing rather than installing? /plugin on its own opens the plugin manager, where added marketplaces and their plugins are listed and can be enabled or disabled.

What it knows

The part a general model was never taught

Ask any assistant for requirements and what comes back is compound shall statements, performance claims with no units or measurement conditions, and design decisions dressed up as requirements. It reads well enough to circulate, and you find out in review.

  • The five EARS patterns, and which one a given requirement actually wants. Ubiquitous, event-driven, state-driven, unwanted-behaviour and optional each have a shape, and picking the wrong one is how a requirement becomes untestable.
  • Permanent ID schemes that survive renumbering, so a trace matrix written today still resolves after the document is reorganised.
  • A banned-word list that rejects “robust”, “user-friendly” and the rest on sight, with the reason attached rather than a bare complaint.
  • A repair workflow that shows the diff. An agent that silently rewrites your specification has replaced a review you were going to do with one you now cannot.

What is free, and what is not

This is one skill. There are ten.

Requirements authoring is free: the whole skill, not a trimmed sample, and it stays that way. The other nine are the paid pack, they are not in the public repository, and they are licensed separately. Installing this one does not get you those.

Skill What it does Included
mbse-requirementsEARS authoring, review and repairFree
mbse-safety-analysisMIL-STD-882E severity, probability and RAC; FHA and FMEAPack
mbse-traceabilityAudit queries and change-impact analysisPack
mbse-verificationMethod selection, pass criteria, evidence schemaPack
mbse-model-formatA portable, diffable model file and its validatorPack
mbe3d-connectConnecting to MBE3Dstudio, and its failure modesPack
mbe3d-loadGetting a model in with its attributes intactPack
mbe3d-analyzeSPARQL, competency suites and CI gatesPack
mbe3d-studioThe 3D surface and the provenance model under itPack
mbe3d-harnessThe agent runtime, its plugins and its session logPack

Five work on your own files. Four connect to MBE3Dstudio, which is licensed separately.

Get the pack ($29) The free skill on GitHub

Licence

Free to use. Not free to repackage.

Use it on any number of machines, for your own work and for client work you do yourself, and modify it for your own use. What is not permitted is reselling it, sublicensing it, or republishing it as part of another product, template, course or skill pack. The paid eight are under a separate licence that does not permit publication at all.

Questions, or a site licence for your team: get in touch.