Skip to content
cccskills
FreePublished on GitHub

mil-std-881f

Knowledge 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.

The English summary is being prepared. Showing the original description.

See how to install

Files included (13)

  • SKILL.md5.8 KB
  • chapters/ch01-wbs-principles-and-definitions.md3.4 KB
  • chapters/ch02-program-wbs-roles-and-preaward.md3.1 KB
  • chapters/ch03-contract-wbs-and-programmatic-issues.md3.0 KB
  • chapters/ch04-commodity-wbs-air-missile-sea-space.md3.1 KB
  • chapters/ch05-commodity-wbs-ground-umms-launch-is.md2.8 KB
  • chapters/ch06-common-elements-appendix-k.md3.2 KB
  • chapters/ch07-numbering-reporting-sustainment.md3.0 KB
  • cheatsheet.md1.9 KB
  • glossary.md1.8 KB
  • LICENSE1.3 KB
  • PACK.yaml2.0 KB
  • patterns.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

<!-- argument-hint: [WBS, Program WBS, Contract WBS, 100% rule, dictionary, appendix A-J, common elements, sustainment, CSDR, IMP/IMS, software placement, or chapter number] -->

MIL-STD-881F — Work Breakdown Structures for Defense Materiel Items

Source: MIL-STD-881F, 13 May 2022 (US DoD; public domain; Distribution Statement A per ASSIST QuickSearch Dist Stmt for Rev F) | Chapters: 7

When to use

Use this pack when building or reviewing a defense Program or Contract WBS: choosing commodity appendices, applying the 100% rule, writing WBS dictionaries, placing software/cyber/SoS work, hanging Appendix K common elements, aligning IMP/IMS and cost reporting identifiers, implementing post-award WBS control, or applying Appendix L sustainment CES / Appendix M Government ST&E structures under 881F.

Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime. Pair with program cost/CSDR guidance and service tailoring memos for reporting specifics.

How to Use This Skill

  • Without arguments — load the core frameworks below.
  • With a topic — ask about Program vs Contract WBS, 100% rule, dictionaries, a commodity appendix, common elements, sustainment L, or software placement.
  • With a chapter — ask for ch01 through ch07.

Supporting files: glossary.md, patterns.md, cheatsheet.md.

Core Frameworks & Mental Models

Three-layer WBS spine

  1. Program WBS (Government) — whole materiel item / PE
  2. Contract WBS — performer extension of program parents
  3. Subcontract WBS — lower-tier extension with same product parents

100% rule

Decomposition children must represent 100% of parent work/resources. Never promote a child to sibling of its former parent for 'visibility'.

Commodity + commons pattern

LayerSource
Product taxonomyAppendices A–J
Enabling commonsAppendix K (A–J only)
Sustainment CES reportingAppendix L
Government ST&EAppendix M

Dictionary discipline

Every managed element needs definition, inclusions, exclusions—this is interface control for cost, schedule, and engineering.

Software dual path

  • Embedded on weapon equipment → prefer equipment parent (elevate only if unpartitionable)
  • IS/Defense Business Systems → Appendix J

Pre-award → post-award flow

Program WBS + dictionary → RFP extension requirements → Contract WBS CM → reporting levels ≤ definition depth → L/M where applicable.

Chapter Index

#SectionKey content
ch01WBS Principles and DefinitionsPurpose, PE/materiel item, 100% rule, dictionary, layers
ch02Program WBS, Roles, Pre-AwardGovernment construction, RFP, pitfalls
ch03Contract WBS and Programmatic IssuesExtension, SoS, cyber, software, IMP/IMS
ch04Commodity Templates A–FAircraft, electronics, missile, strategic, sea, space
ch05Commodity Templates G–JGround, unmanned maritime, launch, IS/DBS
ch06Common Elements (K)SE/PM, ST&E, training, data, SE, facilities, spares
ch07Implementation, Reporting, SustainmentNumbering, CSDR, Appendix L CES, Appendix M

Topic Index

  • 100% rule / parent-child integrity → ch01, ch03
  • Aircraft WBS (Appendix A) → ch04
  • CAPE Sustainment CES / Appendix L → ch07
  • Common Elements / Appendix K → ch06
  • Contract WBS extension → ch03, ch07
  • CSDR / reporting levels → ch07
  • Cybersecurity placement → ch03
  • Dictionary → ch01, ch02
  • Electronics / avionics / generic (B) → ch04
  • Government ST&E / Appendix M → ch07
  • Ground vehicle (G) → ch05
  • IMP / IMS linkage → ch03
  • Information Systems / DBS (J) → ch05, ch03
  • Launch vehicle (I) → ch05
  • Missile / ordnance (C) / strategic (D) → ch04
  • PM / measurement / EVMS mapping → ch07
  • Program Element / defense materiel item → ch01
  • Program WBS / pre-award / RFP → ch02
  • Sea systems (E) → ch04
  • SE/PM / SEIT/PM → ch06
  • Software placement (embedded vs IS) → ch03, ch05
  • Space systems (F) → ch04
  • Subcontract WBS → ch03
  • System of Systems / Family of Systems → ch03
  • Technical planning & WBS → ch01, ch02, ch07
  • Training / data / support equipment elements → ch06
  • Unmanned maritime (H) → ch05

Supporting Files


Scope & Limits

  • Covers MIL-STD-881F WBS standard practice only (13 May 2022 text used at build).
  • Does not replace CAPE CSDR manuals, service-unique WBS memos, or contract clauses.
  • Synthesized reference notes; not a substitute for the official ASSIST publication for contractual citation.
  • No source PDF or full-text redistribution in this pack.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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.

The English summary is being prepared. Showing the original description.

jgsystemsconsulting/jgs-se-knowledge-packs8Updated Oct 15, 2026

Signpost (not a knowledge pack) for the avionics development assurance standards landscape: RTCA DO-178C / EUROCAE ED-12C and its supplements (DO-330/ED-215, DO-331/ED-218, DO-332/ED-217, DO-333/ED-216); RTCA DO-254 / EUROCAE ED-80; SAE ARP4754B and ARP4761A; and the free regulator documents that recognise them (FAA AC 20-115D, AC 20-152A, Order 8110.49A; EASA AMC 20-115D and AMC 20-152A). Contains no source content: each row carries only the designation, title, edition, owner, redistributability status, and the owner's URL. Use when you need to identify, cite, or locate an avionics standard; paywalled rows point to the owner, free rows point to the regulator text, and the FAA rows also name the in-repo faa-8110-49 pack.

The English summary is being prepared. Showing the original description.

jgsystemsconsulting/jgs-se-knowledge-packs8Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

jgsystemsconsulting/jgs-se-knowledge-packs8Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

jgsystemsconsulting/jgs-se-knowledge-packs8Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

jgsystemsconsulting/jgs-se-knowledge-packs8Updated Oct 15, 2026

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.

The English summary is being prepared. Showing the original description.

jgsystemsconsulting/jgs-se-knowledge-packs8Updated Oct 15, 2026

See all skills by jgsystemsconsulting

Report a problem with this skill