Faa Std 025

Community

jgsystemsconsulting

faa-std-025

Knowledge base from FAA-STD-025f (Preparation of Interface Documentation). Use for IRD/ICD family definitions, common format and content, IRD shall-requirements, ICD design characteristics, verification/VRTM, and CM/revision/approval of FAA Enterprise Subsystem interfaces. Covers rev F preparation rules only; does not replace FAA-STD-005 drawing/spec prep, Order 1800.66 full CM procedures, or non-FAA interface standards.

Overview

Publisher	jgsystemsconsulting
Repository	`jgs-se-knowledge-packs`
Skill name	`faa-std-025`
Stars	121
Forks	1
Bundled files	10
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
10 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jgsystemsconsulting on GitHub. Read the source before you install it.

Installation

Install the Faa Std 025 AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/faa-std-025
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/faa-std-025

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs.git /tmp/jgs-se-knowledge-packs
mkdir -p .claude/skills
cp -r /tmp/jgs-se-knowledge-packs/packs/faa-std-025 .claude/skills/faa-std-025

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Faa Std 025 in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Faa Std 025 on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Faa Std 025 is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

FAA-STD-025f — Preparation of Interface Documentation

Source: FAA-STD-025f (US Government work, public domain) | Chapters: 6

When to use

Reach for this pack when authoring or reviewing Interface Requirements Documents (IRD) or Interface Control Documents (ICD) for FAA Enterprise Subsystems / NAS interfaces — including choosing IRD vs ICD, filling required outlines, specifying security/physical/power interface shalls, building a VRTM, or routing revisions under configuration management.

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.
With a topic — ask about IRD vs ICD, TBS, facility IRDs, VRTM, security shalls, power factors, or approval roles.
With a chapter — ask for ch01 through ch06.

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

Core Frameworks & Mental Models

IRD / ICD pair

Artifact	Answers	Verb	Baseline role
IRD	What must the interface satisfy?	shall	FAA-controlled requirements baseline
ICD	How is it implemented / as-built?	is/are	Developer deliverable design record

Facility interfaces: IRD only (no ICD). Orphan ICDs (no parent IRD) must carry both shall and is/are — discouraged.

Interface-type outlines

Use the standard decision tree, then the matching TOC:

Facility / analog / discrete family
General service / web service family

Shared rules: front matter, explicit N/A, incorporation by reference, TBS only where allowed.

Common technical spine

Scope template + responsibility lists
Referenced documents (versioned, accessible, tailored)
Functions / demarcation / security / physical / power
Type-specific protocol or facility slots
Verification responsibility + VRTM (1:1 with shalls)

Verification levels

Subsystem/Service (Development) → Integration → Site. SEM T&E guidance tailored into the VRTM; special conformance/interoperability for ATN/IPS.

CM and timing

Start IRD early; before SOW finalization when used in procurement.
Approve IRD before ICD when both required.
Revise by superseding full document under FAA Order 1800.66 (no legacy side "Interface Revision" form).
Facility IRD maturity: Initial → Primary → Intermediate → Final.

Chapter Index

#	Section	Key content
ch01	Scope and Document Family	FESS applicability, IRD vs ICD, TBS, baselining
ch02	General Format and Common Content	Outlines, front matter, scope templates, references
ch03	IRD Content Requirements	Functional/security/physical/power and typed IRDs
ch04	ICD Content Requirements	Design characteristics, as-built, orphan ICD rule
ch05	Verification and Traceability	VRTM, levels, methods, ATN/IPS special tests
ch06	Revisions, CM, and Approval	1800.66 revisions, roles, facility iterations

Topic Index

Analog / discrete interfaces → ch01, ch03, ch04
Application process / protocols → ch03, ch04
As-built / form-fit-function → ch01, ch04
Configuration Management / Order 1800.66 → ch02, ch06
Demarcation point → ch03
Facility IRD (no ICD) → ch01, ch03, ch06
Front matter / TOC outlines → ch02
Interface Control Document (ICD) → ch01, ch04
Interface Management → ch01, ch06
Interface Requirements Document (IRD) → ch01, ch03
Interface Working Group roles → ch06
N/A and TBS language → ch01, ch02
Power / connectors / grounding / EMC → ch03, ch04
Requirements Traceability / VRTM → ch05
Security requirements at interfaces → ch03, ch04
Service / web service interfaces → ch03, ch04
Verification levels (dev/integration/site) → ch05
Verb discipline (shall vs is/are) → ch01, ch04

Supporting Files

glossary.md — IRD/ICD and interface terms
patterns.md — implementation patterns with When/How/Trade-offs
cheatsheet.md — decision rules, maps, tells & smells

Scope & Limits

This pack covers FAA-STD-025f (November 30, 2007) — Preparation of Interface Documentation — as synthesized reference notes from the everyspec mirror of Rev F (64 pages per extraction metadata). It does not cover: full text of FAA-STD-005 / FAA-STD-002 / FAA-G-2100; the complete FAA Order 1800.66 CM procedure set; non-FAA interface control standards (e.g., generic MIL ICD practices beyond this FAA standard); or program-specific IRD/ICD instances. US Government public domain work. No source-material download link is published.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Faa Std 025 AI skill do?

Why use Faa Std 025 on TypingMind?

Because you install it once and use it with any model. Faa Std 025 is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Faa Std 025 in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/faa-std-025. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Faa Std 025?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Faa Std 025?

As many as you like. As long as a model supports skills, you can use Faa Std 025 with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Faa Std 025 AI skill free?

It is published on GitHub by jgsystemsconsulting. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Grill With Docs

mattpocock

CommunityPopular

A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

Grill Me

A relentless interview to sharpen a plan or design.

Brand Discovery

Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand…

Competitive Platform Analysis

affaan-m

CommunityPopular

Use when scoping a competitive landscape — identifying, categorising, and score-filtering a competitor set before any benchmarking begins. Decides who counts as a competitor, which tier they belong…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

FAA-STD-025f — Preparation of Interface Documentation

When to use

How to Use This Skill

Core Frameworks & Mental Models

IRD / ICD pair

Interface-type outlines

Common technical spine

Verification levels

CM and timing

Chapter Index

Topic Index

Supporting Files

Scope & Limits

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now