easa-rules

Installation
SKILL.md

EASA AMC 20-115D and AMC 20-152A

Source: European Union Aviation Safety Agency (EASA): AMC 20-115D (ED Decision 2017/020/R, AMC-20 Amendment 14) and AMC 20-152A (ED Decision 2020/010/R, AMC-20 Amendment 19), both consolidated in AMC-20 Amendment 23 (June 2023 Easy Access Rules compilation); pinned 2026-09-26. Adapted from the sibling prototype and re-checked against the 2026-10-13 EASA source pin | Licence: per-document, see LICENSE | Chapters: 7

When to use

Prerequisites: airborne software or airborne electronic hardware vocabulary (DAL, life cycle processes, assurance); the question names EASA, not the FAA.

Use this skill for questions about the EASA means of compliance for airborne software and airborne electronic hardware: which AMC answers which question and how the decision instruments anchor them, where AMC 20-115D applies and what its replacement of AMC 20-115C changed, how the AMC frames software life cycle assurance without dumping the standard's objectives, where AMC 20-152A applies and what it adds beyond recognising ED-80/DO-254, and how the software and hardware sides meet in one certification workflow. The pack answers with the AMCs' own frameworks, cited by chapter and source row.

How to Use This Skill

  • Without arguments: read the Core Frameworks below for the means-of-compliance landscape, the two applicability models, and the added hardware objectives.
  • With a topic: use the Topic Index to find the chapter, then ask directly (e.g. "does AMC 20-152A apply at DAL D", "what AltMoC requires").
  • With a chapter: ch01 orientation (which AMC and which decision answer which question); ch02-ch04 AMC 20-115D scope, software assurance, and transition/GM material; ch05-ch06 AMC 20-152A scope and the added AEH objectives; ch07 the joint software and hardware workflow.

Supporting files: glossary.md, cheatsheet.md.

Installs
1
GitHub Stars
56
First Seen
Nov 5, 2026