sd-22-dmsms
From the author
Knowledge base from the SD-22 DMSMS Guidebook (DSPO, SD-22, 06-JAN-2026 (cover dated December 2025)). Use for managing Diminishing Manufacturing Sources and Material Shortages (DMSMS) and obsolescence across a long-lived system's life cycle: the five-step process (Prepare, Identify, Assess, Analyze, Implement); standing up a DMSMS Management Team (DMT) and Management Plan (DMP); FMS communication and FMS considerations on partner configurations; risk-based monitoring and surveillance (predictive tools, vendor surveys, GIDEP/DLA PDNs, critical-materials analysis); health assessments and resolution timing; costing and selecting resolutions (life-of-need buys, substitutes, redesign, technology refreshment) by AoA/BCA, including system security engineering as an Analyze consideration; and budgeting/executing resolutions through modification funding and related accounts. Defense-sustainment / DoD-acquisition framing throughout. Does NOT teach general systems engineering, parts-management standards, or contracting
Install
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill sd-22-dmsms -a claude-code
Installs to .claude/skills/sd-22-dmsms/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Contains hidden text (invisible characters, long comments or encoded blobs)Medium
Why 70
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- dau-se-guidebookjgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from the DoD Systems Engineering Guidebook (September 2026, DOPSR Case # 26-T-2032). Use for the DoD SE process model (16 processes: 8 technical management + 8 technical, mapped by method to ISO/IEC/IEEE 15288), SE Modernization (digital engineering, MBSE, MOSA, Agile), engineering resources and enablers, event-driven technical reviews and audits (ASR/SRR/SFR/PDR/CDR/SVR/FCA/PRR/PCA), the Systems Engineering Plan (SEP), TPMs and leading indicators, and the 24 design considerations. Acquisition-program oriented. Guidance not policy. Not the SoS guide.Design★ 98
- dod-mq-bokjgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from the DoD M&Q BoK (the Manufacturing and Quality Engineering Body of Knowledge), v3.0 of July 2025, published by OUSD(R&E). Use for the manufacturing-and-quality view of the defense acquisition life cycle: what M&Q engineers do across the Adaptive Acquisition Framework phases (Pre-MDD, Materiel Solution Analysis, Technology Maturation and Risk Reduction, Engineering and Manufacturing Development, Production and Deployment, Operations and Support); the twelve M&Q threads (A–L) built on the '5 Ms'; manufacturing feasibility and producibility; Manufacturing Readiness Levels and assessments; Key/Critical Characteristics and process capability (Cp/Cpk, SPC); the standards stack (AS6500, AS9100/ISO 9001, AS9103, AS9145); technical reviews (ASR/PDR/CDR/PRR) and milestone gates; DCMA surveillance; industrial base and supply chain; and sustainment (LCSP, IPS, ILA, ISR). Scope is DoD acquisition M&Q practice on the Major Capability Acquisition path — it is a best-practice compilation, not policy, and DevOps★ 98
- dod-mosajgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from the OUSD(R&E) guidebook Implementing a MOSA in DoD Programs (Feb 2025). Use for the Modular Open Systems Approach as a DoD acquisition + design discipline: the statutory/regulatory basis (10 U.S.C. 4401–4403, FY2017/FY2021 NDAA, DFARS), the five OUSD(R&E) pillars, the plan→modularize→identify→define→standardize interface lifecycle, technical levers (WBS/MIL-STD-881F taxonomy, standards profiling, API-first software, COTS/cybersecurity), MOSA assessment metrics and tools (PART/OAAT/KOSS/SEAM/MAUT), technology-change and DMSMS management, roadmaps, MOSA across the six AAF pathways, and contracting/IP/data-rights mechanics. SCOPE LIMITS: this is U.S. DoD weapon-system acquisition policy, not a general open-architecture or interface-standards reference — it names standards (FACE, OMS, DISR) without reproducing them, is light on detailed engineering of any specific standard, and does not cover the underlying SE processes (use dau-se-guidebook / nasa-npr-7123) or general systems-engineering theoDesign★ 98
- mil-hdbk-61jgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from MIL-HDBK-61B, the DoD Configuration Management (CM) guidance handbook (7 April 2020, cataloged with Change 1, 2025). Use for defense CM across the acquisition and sustainment life cycle: the five CM functions (planning, identification, control/change management, status accounting, verification & audit), the three configuration baselines (FBL/ABL/PBL) and FCD→ACD→PCD documentation, configuration items (CIs/HWCI/CSCI), change instruments (ECP/NOR/RFV), the CCB and Class I/II classification, CDCA/AA authority, FCA/PCA audits, data management and data rights (CDRL/DID, DFARS rights ladder, master/authoritative source), and tailoring CM by phase (EIA-649-1 R/T/NR matrix, Appendix C templates), plus digital-era CM (digital twin, viewpoints, MOSA). NOTE: 61B is advisory guidance that adopts and points to the SAE EIA-649 / EIA-649-1 / GEIA-HB-649 suite for the authoritative CM requirements — this pack names and describes that suite but does not reproduce its copyrighted requirement text. Thin on: Finance★ 98
- mil-std-881fjgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from MIL-STD-881F (13 May 2022), DoD Standard Practice for Work Breakdown Structures for Defense Materiel Items. Use for Program/Contract/Subcontract WBS construction, 100% rule and dictionary discipline, commodity appendices A–J, Common Elements (K), sustainment CES reporting (L), Government ST&E (M), and RFP/post-award implementation. Technical planning & WBS and PM/measurement focus—not a cost manual substitute for CAPE policy.Legal★ 98
- nasa-fault-managementjgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from the NASA Fault Management Handbook (NASA-HDBK-1002, Draft 2, April 2012). Use for the systems-engineering discipline of designing what a system does when it fails — the fault/failure/anomaly vocabulary, the five FM strategies (two prevention strategies — design-time fault avoidance and operational failure avoidance — plus three tolerance strategies — failure masking, failure recovery, and goal change), the six FM process activities across NASA mission phases Pre-A to E, response-latency-versus-time-to-criticality (TTC) design trades, fault/failure containment regions and FEPPs, the four redundancy approaches, top-down FM requirements development, FM verification vs. validation, the seven dedicated FM milestone reviews (FMCR/FMARR/FMPDR/FMCDR/FMTRR/FMLRR/FMCERR), FM organizational structure, and mined NASA Lessons Learned. Space-mission oriented (flight/ground/operations); spacecraft examples throughout. IMPORTANT: built from an UNAPPROVED DRAFT — several sections (detailed architecture buiDesign★ 98
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in