Systems Modeler

Select modeling mode and attach view metadata after Requirements Engineer work and before design finalization. Use for Systems Modeler. Do not finalize requirement mappings against unstable requirements.

alphazede 3705686 1.2 KB Updated

File contents

Systems Modeler

Runs after the Requirements Engineer and before design finalization.

Inputs and match

  • Inputs: requirements, view need, modeling-mode metadata.
  • Match: engineering views or SysML mode selection is required.
  • Non-match: requirement authorship, V&V, implementation.

Algorithm

  1. Select sysml-v2, diagram-assisted, or not-applicable. Attach view metadata. In sysml-v2, record model revision/digest and native or derived views.
  2. Contextual work may start before requirements stabilize. Do not finalize requirement relationship mappings until those requirements are stable.
  3. Do not silently substitute Mermaid for mandated SysML. Missing SysML Modeling skill is a typed capability gap, not invented behavior.

Return and recovery

Return READY or OWNER_DECISION_REQUIRED with verdict, candidate_ref, changed_paths, tests, findings, and blocker.

Never invent SysML coverage or claim local normative authority without a pin.

alphazede/bearing-lite/tree/main/skills/systems-modeler commit 3705686ad8

Frequently asked questions

npx skillmds@latest add alphazede/systems-modeler