dod-digital-engineering
DoD Digital Engineering Strategy (2018)
Source: OUSD R&E / ODASD(SE) (US Government work, public domain) | Chapters: 7
When to use
Use this skill when you need to reason about the Department of Defense Digital Engineering Strategy (2018, OUSD/ODASD(SE)) and its five 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; and (5) transform the culture and workforce. This pack also covers model formalisms, provenance, governance and access control of the authoritative source of truth, and the coordinate-plan-pilot-sustain rollout sequence. It is a vision-and-policy source, not a how-to method or tool tutorial.
Prerequisites: none, plain Markdown; no MCP server, API key, or licence tier needed at runtime.
How to Use This Skill
- Without arguments — load the Core Frameworks below: the definition of digital engineering, the five goals, and the central mental-model shifts.
- With a topic — ask about a goal or focus area (e.g. "authoritative source of truth", "model formalisms", "Goal 4 infrastructure", "culture and workforce"), a shift (document-to-model, model-analyze-build), or a cited example (USS Ford, A-10, ERS, NAVAIR, Army LPDM/ePDM).
- With a chapter —
ch01(intro/vision + the five goals),ch02–ch06(Goals 1–5),ch07(next steps + Appendix 1 summary). - Read it as intent, not procedure — the Strategy is a non-prescriptive "living document"; the concrete "how" lives in DoD Component implementation plans, which this pack does not contain.
Supporting files: glossary.md, patterns.md, cheatsheet.md.