fhwa-its-se
From the author
Knowledge pack synthesized from Systems Engineering for ITS, fourth generation (December 2022, Federal Highway Administration, US Government work, 17 U.S.C. § 105): ITS project systems engineering for transportation agencies. SCOPE LIMITS: single-source (December 2022 FHWA PDF); not construction specifications, not FEMA, not device model-document libraries, not a general SE textbook; INCOSE, ISO/IEC/IEEE 15288, NTCIP, IEEE, and SAE named, not quoted; reconstructed reference notes, not FHWA guidance, and no FHWA endorsement.
Install
npx skills add jgsystemsconsulting/jgs-se-knowledge-packs --skill fhwa-its-se -a claude-code
Installs to .claude/skills/fhwa-its-se/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- nhtsa-vehiclejgsystemsconsulting/jgs-se-knowledge-packsSynthesized reference notes from three US Government vehicle-safety sources: NHTSA Cybersecurity Best Practices for the Safety of Modern Vehicles (updated 2022, final), NHTSA Automated Driving Systems 2.0: A Vision for Safety (2017), and a 16-section selection of 49 CFR Part 571 (FMVSS) pinned at eCFR versioner date 2025-01-01. Use for voluntary vehicle cybersecurity practices, the ADS 2.0 twelve priority safety design elements, and FMVSS occupant protection, brakes/stability/lighting, and fuel/EV integrity requirements. Not ISO 26262, not ASPICE, not ISO/SAE 21434, not UNECE R155/R156, not SAE J3016, and not the full Part 571; the FMVSS material is a selection of vehicle-level minimum performance standards, not a process standard.Design★ 85
- faa-ams-vvjgsystemsconsulting/jgs-se-knowledge-packsKnowledge pack synthesized from FAA AMS Lifecycle Verification and Validation Guidelines, Version 4.0 (January 2023): verify-vs-validate, the three tiers, decision-point-gated V&V across the AMS lifecycle, and shift-left. SCOPE LIMITS: single-source (the January 2023 guidelines); FAA acquisition V&V doctrine, not a general SE process model, not a requirements manual, and not a test-design textbook; CMMI for Development v1.2 named and paraphrased, never copied; surrounding AMS lifecycle is faa-sem; phase tables are January 2023 snapshots, not live authority; reconstructed reference notes, not FAA guidance, and no FAA endorsement.Testing★ 85
- workOutlineDriven/outline-driven-developmentUse when implementing from a plan, spec, clear build request, or settled ticket, orchestrated or standalone. Don't use for open-ended debugging (figure-it-out), exploration, or read-only research.Science★ 55
- nasa-se-handbookjgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2). Use for NASA's systems-engineering process model — the SE Engine and 17 common technical processes, the program/project life cycle (Pre-Phase A through F), Key Decision Points and technical reviews (MCR/SRR/PDR/CDR/…), stakeholder expectations, technical requirements, design solution, product verification and validation, and crosscutting technical management (planning, risk, configuration, interfaces, data, assessment, decision analysis). Strong for aerospace/spaceflight project SE and lifecycle gating; NASA-specific terminology (KDPs, NPR 7123.1).Design★ 85
- nasa-hsijgsystemsconsulting/jgs-se-knowledge-packsKnowledge base from NASA Human Systems Integration (HSI) Practitioner's Guide (NASA/SP-2015-3709). Use for HSI process implementation, lifecycle phase activities, function allocation, ConOps development, HSI Plan writing, HSI metrics (MOE/MOP/TPM/KPP), HITL testing strategy, HSI team organisation, scaling/tailoring for program size, and V&V planning. Does not cover the specific human engineering design standards (NASA-STD-3001 content) or detailed HFE methods beyond what the guide itself provides.Testing★ 85
- digital-systems-engineeringjgsystemsconsulting/jgs-se-knowledge-packsKnowledge 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.Science★ 85
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in