nasa-fault-management

Installation
SKILL.md

NASA Fault Management Handbook (NASA-HDBK-1002 Draft 2, April 2012)

Source: NASA — US Government work, public domain | Chapters: 8 | DRAFT SOURCE

READ FIRST — DRAFT. This pack synthesizes NASA-HDBK-1002 Draft 2 (April 2, 2012), an unapproved working draft of the NASA Fault Management Handbook. Terminology, scope, review names, and the FM process here reflect that draft and may differ from any later released or approved edition. Several source sections are explicit placeholders (detailed FM architecture building blocks in §6.3; the Assessment & Analysis guidance; the Operations & Maintenance section §9) and are correspondingly thin in this pack. Treat all of it as informational guidance, not a controlling standard, and verify against the current NASA standard before citing in formal work. NASA does not endorse this pack.

When to use

Use this skill when you need to design, assess, or explain how a system detects and accommodates failures: the fault/failure/anomaly vocabulary; deciding whether a fault is handled by flight software, firmware, hardware, crew, or ground (the response-latency-vs-TTC trade); choosing among the five FM strategies and the four redundancy approaches; writing top-down FM requirements; planning FM verification and validation; running the dedicated FM milestone reviews; organizing a project so FM has a system-level home; or checking a design against recurring NASA Lessons Learned. It is the off-nominal companion to the NASA Systems Engineering Handbook.

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 for an overview of the FM discipline, its vocabulary, the latency-vs-TTC trade, the five strategies, and the FM process/review structure.
  • With a topic — ask about a concept (e.g., "time to criticality", "failure containment region", "safe mode"), a strategy (e.g., "failure masking vs. goal change"), a process activity (e.g., "FM requirements development"), a review (e.g., "FMCDR success criteria"), or organization/lessons learned.
  • With a chapter — ask for ch01 (definitions), ch02 (FM process), ch03 (requirements), ch04 (design & architecture / latency-vs-TTC), ch05 (V&V), ch06 (reviews & operations), ch07 (fundamental concepts), ch08 (organization & lessons learned).

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

Installs
1
GitHub Stars
56
First Seen
Nov 5, 2026