S
sweetscientist/systems-engineering-skill
Claude Code skill for systems engineering: requirements matrix, FFBD/N², VCRM, traceability, trade studies,…
View on GitHub ↗Link checked 2026-11-12 · HTTP 200 · opens the vendor's own site
- Star count
- 0 ★ · sweetscientist/systems-engineering-skill · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- read directly from its GitHub page · type: open-source project
- Harvest history
- first seen 2026-10-29 · last seen 2026-11-14 · seen 17× · listed by 1 sources
- Score
- score 103 · 1 sources · repo
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: 开源项目. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
sweetscientist/systems-engineering-skill;first catalogued 2026-10-29;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# Systems Engineering Skill for Claude Code
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
Works with: Claude Code (plugin, all 34 slash commands) · OpenAI Codex[^skills] · Gemini CLI[^skills] · OpenCode[^skills] · Windsurf[^skills] · Antigravity[^skills] · Hermes Agent[^skills] · Mistral Vibe[^skills]
[^skills]: Untested. These tools load skills in the Agent Skills SKILL.md format, so skills/systems-engineering/ should load as a skill, but the /systems-engineering: : slash commands are Claude Code only. Ask in plain language instead ("run design:requirements for …"). Where the skill calls for Claude Code's AskUserQuestion tool, other agents ask in chat. Install steps are under Other agents.
A Claude Code plugin that does structured systems-engineering work, organized around the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2). It covers stakeholder expectations through transition, the crosscutting technical management processes, life-cycle reviews, and specialty analyses, all on one shared, traceable set of artifacts.
Every artifact is linked by ID, so a change in one place can be traced through the others. Methods that create artifacts work like plan mode: they read your inputs, ask only the questions that change the result, propose a structure, and write nothing until you approve it.
## Commands
Commands are namespaced /systems-engineering: : . Type /systems-engineering: to see them all.
### design: System design processes (SEH §4)
| Command | What it does |
| design:stakeholders | Stakeholder register, needs / goals / objectives, MOEs, mission success criteria |
| design:conops | Concept of operations per SEH App S: environments, nominal and off-nominal scenarios |
| design:requirements | Build or audit a Standard Requirements Matrix (seven columns, strict traceability, ADIT), MOPs and TPMs, SEH six-step validation, App C checklists |
| design:decomposition | Function tree (FFBD), timing and modes, allocation, derived requirements |
| design:solution | Physical breakdown (PBS), alternatives, enabling products, end-product specs |
### realization: Product realization processes (SEH §5)
| Command | What it does |
| realization:implementation | Buy / make / reuse per element, heritage and requalification |
| realization:integration | Integration sequence and plan per SEH App H |
| realization:verification | Verification matrix (VCRM): qualification, acceptance, protoflight; verification reports |
| realization:validation | Validation matrix traced to ConOps, NGOs, and MOEs per SEH App E |
| realization:transition | Handover readiness: documentation, training, shipping, installation, sustaining |
### management: Crosscutting technical management (SEH §6)
| Command | What it does |
| management:planning | SEMP per SEH App J, WBS, technical schedule keyed to reviews |
| management:requirements | Read-only traceability: impact , coverage, change |
| management:interfaces | N² matrix, interface list, IRD / ICD per SEH App L |
| management:risk | Risk register: risk triplet, RIDM vs. CRM, triggers, mitigation and contingency |
| management:config | Baselines (functional, allocated, product, as-deployed), change requests, waivers, status accounting |
| management:data | Technical data items: owner, format, access, storage |
[^skills]: Untested. These tools load skills in the Agent Skills SKILL.md format, so skills/systems-engineering/ should load as a skill, but the /systems-engineering: : slash commands are Claude Code only. Ask in plain language instead ("run design:requirements for …"). Where the skill calls for Claude Code's AskUserQuestion tool, other agents ask in chat. Install steps are under Other agents.
A Claude Code plugin that does structured systems-engineering work, organized around the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2). It covers stakeholder expectations through transition, the crosscutting technical management processes, life-cycle reviews, and specialty analyses, all on one shared, traceable set of artifacts.
Every artifact is linked by ID, so a change in one place can be traced through the others. Methods that create artifacts work like plan mode: they read your inputs, ask only the questions that change the result, propose a structure, and write nothing until you approve it.
## Commands
Commands are namespaced /systems-engineering: : . Type /systems-engineering: to see them all.
### design: System design processes (SEH §4)
| Command | What it does |
| design:stakeholders | Stakeholder register, needs / goals / objectives, MOEs, mission success criteria |
| design:conops | Concept of operations per SEH App S: environments, nominal and off-nominal scenarios |
| design:requirements | Build or audit a Standard Requirements Matrix (seven columns, strict traceability, ADIT), MOPs and TPMs, SEH six-step validation, App C checklists |
| design:decomposition | Function tree (FFBD), timing and modes, allocation, derived requirements |
| design:solution | Physical breakdown (PBS), alternatives, enabling products, end-product specs |
### realization: Product realization processes (SEH §5)
| Command | What it does |
| realization:implementation | Buy / make / reuse per element, heritage and requalification |
| realization:integration | Integration sequence and plan per SEH App H |
| realization:verification | Verification matrix (VCRM): qualification, acceptance, protoflight; verification reports |
| realization:validation | Validation matrix traced to ConOps, NGOs, and MOEs per SEH App E |
| realization:transition | Handover readiness: documentation, training, shipping, installation, sustaining |
### management: Crosscutting technical management (SEH §6)
| Command | What it does |
| management:planning | SEMP per SEH App J, WBS, technical schedule keyed to reviews |
| management:requirements | Read-only traceability: impact , coverage, change |
| management:interfaces | N² matrix, interface list, IRD / ICD per SEH App L |
| management:risk | Risk register: risk triplet, RIDM vs. CRM, triggers, mitigation and contingency |
| management:config | Baselines (functional, allocated, product, as-deployed), change requests, waivers, status accounting |
| management:data | Technical data items: owner, format, access, storage |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/sweetscientist-systems-engineering-skill/)
- Source
- github · https://github.com/sweetscientist/systems-engineering-skill
- Browse by field
- Open source
- added
- today
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.