How do I install the Systems Engineering skill?

Run npx skillmds@latest add ashfordeou/systems-engineering-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Systems Engineering safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Systems Engineering?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Systems Engineering free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Systems Engineering?

ashfordeOU (@ashfordeou) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Systems Engineering by ashfordeou — Agent Skill

Name: Systems Engineering
Author: ashfordeOU

Systems Engineering

Use when running model-based systems engineering for an aerospace program: sequence the modeling workflow (requirements modeling, functional and logical architecture, allocation, analysis, traceability), check that every function is allocated to a design element, verify traceability closure (full for safety-critical items), and map modeling tasks to open-source toolchains such as Capella, OSATE, and Papyrus. Models are the primary artifacts; the systems engineering process follows the mapped guidance. Trigger: MBSE, model-based systems engineering, SysML, architecture modeling, functional architecture, allocation, digital thread, Capella, OSATE.

ashfordeOU e7a30ac 3 files · 7.1 KB Updated Sep 17, 2026

File contents

MBSE Systems Engineering (systems-engineering-safety/mbse/systems-engineering)

Use when the task is model-based systems engineering: building and checking the model workflow, allocation, and traceability for an aerospace program.

Domain quick reference

MBSE executes systems engineering with models as the primary artifacts: requirements against functional and logical architecture, functions allocated to design elements, analysis run on the architecture.
The mapped systems-engineering guidance (ARP4754A) governs the development process; MBSE is a means of executing it.
Traceability links each requirement through design to its verification; safety-critical items need full closure.
Open-source toolchains: Capella (functional architecture), OSATE (AADL architecture analysis), Papyrus (SysML modeling).

Workflow

Model the requirements against the functional architecture.
Build the logical architecture and allocate functions to design elements.
Run analysis (safety, performance) on the architecture.
Verify traceability closure; full closure for safety-critical items.
Keep the model under configuration management and link it to the verification artifacts (digital thread).

Pitfalls

Functions left unallocated while the model is declared closed.
Safety-critical items with traceability gaps.
Analysis skipped because the architecture is only diagrammed.
Tool choice driven by habit instead of the modeling task.

Behavior contract (gate 3)

The workflow, allocation, traceability, and toolchain logic is exercised by the gate 3 contract test: scripts/test_mbse.py against scripts/mbse_logic.py (stdlib unittest, offline). Run: python3 scripts/test_mbse.py

Compliance

Standards referenced, not reproduced: ARP4754A / ARP4761A text is proprietary (SAE); summary-only per standards-map.yaml and brief 06.
compliance: STANDARDS-REF, gated: false.

---name: systems-engineering-2description: Use when running model-based systems engineering for an aerospace program: sequence the modeling workflow (requirements modeling, functional and logical architecture, allocation, analysis, traceability), check that every function is allocated to a design element, verify traceability closure (full for safety-critical items), and map modeling tasks to open-source toolchains such as Capella, OSATE, and Papyrus. Models are the primary artifacts; the systems engineering process follows the mapped guidance. Trigger: MBSE, model-based systems engineering, SysML, architecture modeling, functional architecture, allocation, digital thread, Capella, OSATE.license: Apache-2.0---# MBSE Systems Engineering (systems-engineering-safety/mbse/systems-engineering)Use when the task is model-based systems engineering: building andchecking the model workflow, allocation, and traceability for anaerospace program.## Domain quick reference- MBSE executes systems engineering with models as the primary artifacts: requirements against functional and logical architecture, functions allocated to design elements, analysis run on the architecture.- The mapped systems-engineering guidance (ARP4754A) governs the development process; MBSE is a means of executing it.- Traceability links each requirement through design to its verification; safety-critical items need full closure.- Open-source toolchains: Capella (functional architecture), OSATE (AADL architecture analysis), Papyrus (SysML modeling).## Workflow1. Model the requirements against the functional architecture.2. Build the logical architecture and allocate functions to design elements.3. Run analysis (safety, performance) on the architecture.4. Verify traceability closure; full closure for safety-critical items.5. Keep the model under configuration management and link it to the verification artifacts (digital thread).## Pitfalls- Functions left unallocated while the model is declared closed.- Safety-critical items with traceability gaps.- Analysis skipped because the architecture is only diagrammed.- Tool choice driven by habit instead of the modeling task.## Behavior contract (gate 3)The workflow, allocation, traceability, and toolchain logic isexercised by the gate 3 contract test: scripts/test_mbse.py againstscripts/mbse_logic.py (stdlib unittest, offline). Run:python3 scripts/test_mbse.py## Compliance- Standards referenced, not reproduced: ARP4754A / ARP4761A text is proprietary (SAE); summary-only per standards-map.yaml and brief 06.- compliance: STANDARDS-REF, gated: false.

Frequently asked questions