本文へ移動
cccskills
無料GitHub で公開

nasa-se-handbook

Knowledge base from the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2). Use for NASA's systems-engineering process model — the SE Engine and 17 common technical processes, the program/project life cycle (Pre-Phase A through F), Key Decision Points and technical reviews (MCR/SRR/PDR/CDR/…), stakeholder expectations, technical requirements, design solution, product verification and validation, and crosscutting technical management (planning, risk, configuration, interfaces, data, assessment, decision analysis). Strong for aerospace/spaceflight project SE and lifecycle gating; NASA-specific terminology (KDPs, NPR 7123.1).

jgsystemsconsulting/jgs-se-knowledge-packs
インストール方法を見る

含まれるファイル（40）

  • SKILL.md10.4 KB
  • chapters/ch01-2-0-fundamentals-of-systems-engineering.md8.3 KB
  • chapters/ch02-2-1-the-common-technical-processes-and-the-se.md11.6 KB
  • chapters/ch03-2-3-example-of-using-the-se-engine.md13.4 KB
  • chapters/ch04-2-5-cost-effectiveness-considerations.md9.1 KB
  • chapters/ch05-2-6-human-systems-integration-hsi-in-the-se-process.md8.4 KB
  • chapters/ch06-2-7-competency-model-for-systems-engineers.md6.9 KB
  • chapters/ch07-3-0-nasa-program-project-life-cycle.md8.6 KB
  • chapters/ch08-3-1-program-formulation.md12.9 KB
  • chapters/ch09-3-2-program-implementation.md11.1 KB
  • chapters/ch10-3-3-project-pre-phase-a-concept-studies.md9.4 KB
  • chapters/ch11-3-4-project-phase-a-concept-and-technology-development.md7.2 KB
  • chapters/ch12-3-5-project-phase-b-preliminary-design-and-technology-completion.md6.4 KB
  • chapters/ch13-3-6-project-phase-c-final-design-and-fabrication.md6.9 KB
  • chapters/ch14-3-7-project-phase-d-system-assembly-integration-and-test-launch.md6.9 KB
  • chapters/ch15-3-8-project-phase-e-operations-and-sustainment.md11.4 KB
  • chapters/ch16-3-9-project-phase-f-closeout.md9.5 KB
  • chapters/ch17-4-1-stakeholder-expectations-definition.md10.1 KB
  • chapters/ch18-4-2-technical-requirements-definition.md11.1 KB
  • chapters/ch19-4-3-logical-decomposition.md7.2 KB
  • chapters/ch20-4-4-design-solution-definition.md11.3 KB
  • chapters/ch21-5-1-product-implementation.md7.1 KB
  • chapters/ch22-5-2-product-integration.md10.2 KB
  • chapters/ch23-5-3-product-verification.md11.5 KB
  • chapters/ch24-5-4-product-validation.md10.2 KB
  • chapters/ch25-5-5-product-transition.md8.0 KB
  • chapters/ch26-6-0-crosscutting-technical-management.md7.6 KB
  • chapters/ch27-6-1-technical-planning.md16.0 KB
  • chapters/ch28-6-2-requirements-management.md9.0 KB
  • chapters/ch29-6-3-interface-management.md5.7 KB
  • chapters/ch30-6-4-technical-risk-management.md7.9 KB
  • chapters/ch31-6-5-configuration-management.md10.0 KB
  • chapters/ch32-6-6-technical-data-management.md8.2 KB
  • chapters/ch33-6-7-technical-assessment.md12.7 KB
  • chapters/ch34-6-8-decision-analysis.md13.9 KB
  • cheatsheet.md5.3 KB
  • glossary.md16.8 KB
  • LICENSE970 B
  • PACK.yaml889 B
  • patterns.md13.1 KB

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

<!-- argument-hint: [topic, process name, or chapter number] -->

NASA Systems Engineering Handbook

Source: NASA (US Government work, public domain) | Document: NASA/SP-2016-6105 Rev 2 | Pages: ~383 | Chapters: 34

When to use

Use this pack when you need NASA's systems-engineering process model: the SE Engine and the 17 common technical processes, the program/project life cycle (Pre-Phase A → F), Key Decision Points and technical reviews (MCR, SRR, SDR, PDR, CDR, SAR, ORR, FRR), stakeholder expectations → technical requirements → logical decomposition → design solution, product verification vs validation, and crosscutting technical management (planning, risk, configuration, interfaces, data, assessment, decision analysis). Strong for aerospace/spaceflight project SE and lifecycle gating. Less suited to general MBSE notation or AI integration.

Prerequisites: none — this pack is plain Markdown; no MCP server, API key, or licence tier is needed at runtime.

How to Use This Skill

  • Without arguments — load the core process model below for reference.
  • With a topic — ask about verification vs validation, PDR, trade studies, configuration management, or another indexed topic; I read the relevant chapter.
  • With a chapter — ask for ch20 to load Design Solution Definition.
  • Browse — ask "what chapters do you have?" for the full index.

Supporting files: glossary.md (108 terms), patterns.md (21 techniques), cheatsheet.md (decision rules, phase/KDP/review gates, cost thresholds).

Core Frameworks & Mental Models

The SE Engine (Ch 1–3). NASA's central model: the 17 common technical processes arranged as three families — system design (4 processes: stakeholder expectations, technical requirements, logical decomposition, design solution), product realization (5: implementation, integration, verification, validation, transition), and technical management (8: planning, requirements management, interface management, risk, configuration, data, assessment, decision analysis). The engine is applied recursively down the product hierarchy and iteratively within each life-cycle phase.

Program/project life cycle (Ch 7–16). Phases Pre-Phase A (concept studies) → A (concept & technology development) → B (preliminary design) → C (final design & fabrication) → D (assembly, integration, test, launch) → E (operations) → F (closeout). Phase transitions are gated at Key Decision Points (KDPs) and supported by technical reviews (MCR, SRR, SDR/MDR, PDR, CDR, SIR, TRR, SAR, ORR, FRR).

System design flow (Ch 17–20). Stakeholder Expectations (captured as Needs-Goals-Objectives, ConOps, and Measures of Effectiveness) → Technical Requirements (validated, verifiable, with MOPs/TPMs) → Logical Decomposition (functional architecture, Product Breakdown Structure) → Design Solution (trade studies + decision analysis selecting the baseline).

Product realization (Ch 21–25). Implementation (make/buy/reuse) → Integration → Verification ("built it right" — test, analysis, inspection, demonstration) → Validation ("built the right thing" — against stakeholder expectations) → Transition. Verification and validation are distinct and both required.

Crosscutting technical management (Ch 26–34). Technical Planning (WBS, SEMP), Requirements Management (traceability, change control), Interface Management, Technical Risk Management (continuous, risk-informed decision making), Configuration Management, Technical Data Management, Technical Assessment (TPMs, EVM, reviews), and Decision Analysis (structured trade studies).

Chapter Index

#SectionKey content
ch012.0 Fundamentals of SEThe SE Engine; design processes
ch022.1 Common Technical Processes & SE EngineThe 17 processes; process families
ch032.3 Example of Using the SE EngineSE Engine; Product Breakdown Structure
ch042.5 Cost-Effectiveness ConsiderationsDesign trade studies; cost-effectiveness
ch052.6 Human Systems Integration (HSI)HSI Plan
ch062.7 SE Competency ModelNASA SE Competency Model
ch073.0 Program/Project Life CycleLife-cycle model; Key Decision Points
ch083.1 Program FormulationProgram coupling taxonomy
ch093.2 Program ImplementationProgram technical activities; reviews
ch103.3 Pre-Phase A: Concept StudiesConOps; Analysis of Alternatives
ch113.4 Phase A: Concept & Tech DevelopmentSEMP; mission architecture
ch123.5 Phase B: Preliminary DesignPhase B baseline; the PDR
ch133.6 Phase C: Final Design & FabricationDetailed design package; CDR
ch143.7 Phase D: AI&T, LaunchAssembly/integration/V&V; FRR/MRR
ch153.8 Phase E: Operations & SustainmentMission operations; sustainment
ch163.9 Phase F: CloseoutCompliance matrix; NPR 7123.1 tailoring
ch174.1 Stakeholder ExpectationsNGOs; ConOps; MOEs
ch184.2 Technical RequirementsRequirements definition & validation
ch194.3 Logical DecompositionFunctional architecture; PBS
ch204.4 Design SolutionTrade study; decision analysis
ch215.1 Product ImplementationMake/buy/reuse; Material Review Board
ch225.2 Product IntegrationIntegration strategy
ch235.3 Product VerificationVerification process & methods
ch245.4 Product ValidationValidation process
ch255.5 Product TransitionTransition process
ch266.0 Crosscutting Technical ManagementThe 8 management processes
ch276.1 Technical PlanningWBS; SEMP
ch286.2 Requirements ManagementTraceability; change control
ch296.3 Interface ManagementInterface specs; change control
ch306.4 Technical Risk ManagementRIDM; Continuous Risk Management
ch316.5 Configuration ManagementCM process
ch326.6 Technical Data ManagementData management process
ch336.7 Technical AssessmentTechnical reviews; Earned Value Management
ch346.8 Decision AnalysisDecision analysis / trade studies

Topic Index

  • SE Engine / 17 processes → ch01, ch02, ch03
  • Life cycle phases (Pre-A–F) → ch07, ch10–ch16
  • Key Decision Points / technical reviews (PDR, CDR, …) → ch07, ch33, ch12, ch13
  • Stakeholder expectations / ConOps / NGOs / MOEs → ch17, ch10
  • Technical requirements / MOPs / TPMs → ch18, ch33
  • Logical decomposition / functional architecture / PBS → ch19, ch03
  • Design solution / trade studies / decision analysis → ch20, ch34, ch04
  • Verification vs validation → ch23, ch24
  • Integration / transition → ch22, ch25
  • Risk management (RIDM, CRM) → ch30
  • Configuration management → ch31
  • Interface management → ch29
  • Requirements management / traceability → ch28
  • Technical planning / WBS / SEMP → ch27, ch11
  • Earned Value Management / technical assessment → ch33
  • Human Systems Integration → ch05
  • Competency model → ch06

Supporting Files

  • glossary.md — 108 NASA SE terms with chapter refs
  • patterns.md — 21 techniques (SE Engine application, trade studies, V&V methods, risk, CM, reviews)
  • cheatsheet.md — decision rules, phase/KDP/review-gate table, cost-of-late-fix thresholds, tells & smells

Scope & Limits

This pack covers NASA/SP-2016-6105 Rev 2 only. It is NASA-specific: the process model, Key Decision Points, technical reviews, and tailoring are framed for NASA programs/projects (and reference NPR 7123.1), with an aerospace/spaceflight emphasis. It is strong for lifecycle process, gating, V&V, and technical management; it is not a modelling-notation reference (use the SysML pack) and does not address AI/ML integration. The source is a US Government work in the public domain.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

ログインしてレビューを書く

同じリポジトリのスキル

概要と使いどころ

automotive-signpost

無料

Signpost (not a knowledge pack) for the automotive standards landscape: ISO 26262, ASPICE, SAE J3016, UNECE R155, UNECE R156, and the NHTSA vehicle set. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate an automotive standard. Most are paywalled or carry no redistribution grant and cannot be packaged; the one open path is the nhtsa-vehicle pack.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

cisa-cpg

無料

Knowledge base from CISA Cross-Sector Cybersecurity Performance Goals 2.0. Use for prioritized IT/OT baseline cyber goals aligned to NIST CSF 2.0 (including GOVERN), critical-infrastructure hygiene, MSP/supply-chain expectations, and board-friendly outcome language. Covers CPG 2.0 goals only; does not replace full CSF programs, sector-specific goals (SSGs), or CSET tooling detail.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

dafman-63-119

無料

Knowledge base from DAFMAN 63-119 (15 April 2021), Mission-Oriented Test Readiness Certification. Use for continuous MOTRC replacing single-point OTRR thinking: framework/applicability, Certification Official vs PM roles, review cycle and exit criteria, certification memo/decertify gates, DT&E/contractor evidence, ITT integration and cyber resiliency, and the 31-template matrix. DAF T&E readiness process only—does not replace DoDI 5000.89, AFI 99-103, or multi-service lead policies.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

dau-se-guidebook

無料

Knowledge base from the DoD Systems Engineering Guidebook (OUSD R&E, February 2022). Use for the DoD SE process model — the 16 SE processes (8 technical management + 8 technical) mapped to ISO/IEC/IEEE 15288, the event-driven technical reviews and audits across the Major Capability Acquisition life cycle (ASR, SRR, SFR, PDR, CDR, SVR/FCA, PRR, PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs and leading indicators, system-of-systems and digital engineering, and the 24 design considerations (RAM, system safety, HSI, system security engineering, MOSA, supportability, etc.). Acquisition-program oriented: thin on detailed cost estimating, contracting law, and non-DoD or commercial life cycles.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

digital-systems-engineering

無料

Knowledge pack from 'Towards Digital Engineering: The Advent of Digital Systems Engineering' (Huang et al., Old Dominion University, arXiv:2002.11672, 2020). Use when reasoning about digital engineering, the DoD Digital Engineering Strategy and its five goals, the Authoritative Source of Truth, digitalization vs. digitization, digital augmentation, digitalized models, provenance, unique identification, and the four-level (vision/strategy/action/foundation) DSE research framework. Covers the conceptual/vision layer of the field. SCOPE LIMITS: this is a single ~28-page vision paper, not a methods handbook — it is thin on step-by-step procedures, tooling, case studies, and quantitative evaluation, and it predates 2020 so it does not cover later digital-engineering standards or recent AI/LLM advances. Use the sebok pack for established SE canon and MBSE depth.

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

dod-digital-engineering

無料

Knowledge base from the DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)). Use for the Department of Defense's five digital engineering goals — (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; (5) transform the culture and workforce — plus their focus areas, the document-to-model and design-build-test→model-analyze-build shifts, model formalisms/provenance, governance and access control of the authoritative source of truth, and the coordinate→plan→pilot→sustain rollout. A vision-and-policy strategy, deliberately non-prescriptive. Does NOT provide a how-to method, tool tutorials, MBSE/SysML mechanics, or implementation-plan content; thin on metrics, acquisition-policy detail, and step-by-step procedure. Excludes the CAC-gated Digital Engineering Body of Knowledge (DEBoK).

日本語の概要は準備中です。原文の説明を表示しています。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月9日 更新

jgsystemsconsulting のスキルをすべて見る

このスキルの問題を報告する