gao-tra

Assess technology maturity using GAO TRA best practices, TRL scales, and CTE identification.

5|1|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs --skill gao-tra-jgsystemsconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gao-tra
Source: https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs/tree/main/packs/gao-tra
Command: npx skills add https://github.com/jgsystemsconsulting/jgs-se-knowledge-packs --skill gao-tra-jgsystemsconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Evaluating whether a technology is mature enough to commit to an acquisition program is error-prone: teams over-rate readiness, miss critical technologies, or rely on non-independent assessments. This Skill provides the GAO Technology Readiness Assessment Guide (GAO-20-48G) as an on-demand knowledge base so you can assign defensible TRLs, identify Critical Technology Elements, and judge TRA quality from reconstructed reference notes. ## Core Features & Use Cases - TRL 1-9 Assessment: Apply the environment-keyed Technology Readiness Level scale (laboratory, relevant, operational) plus companion MRL and IRL scales, with guidance on avoiding environment inflation. - CTE Identification & Five-Step Process: Screen technologies with the "new/novel and needed" test derived from the WBS and requirements, then run the five-step TRA process judged against the four reliability characteristics (comprehensive, well-documented, credible, defensible). - Maturation Planning & Milestone Decisions: Build Technology Maturation Plans with off-ramps for immature CTEs and apply TRL 6/7 thresholds to knowledge-based milestone decisions. - Use Case: A program manager asks whether a sensor prototype demonstrated only in a lab is ready for product development; the Skill explains it is at most TRL 4, identifies it as a CTE, and outlines the TMP needed to reach TRL 7 before commitment. ## Quick Start Ask the agent to use the gao-tra skill to explain what TRL applies to a component validated only in a laboratory environment and whether it is ready for product development.

Frequently Asked Questions about gao-tra

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I assign a Technology Readiness Level to a technology?▼

Assign a TRL by first gathering evidence of what was demonstrated and in what environment, then matching it to the scale: laboratory demonstrations support TRL 4 or below, relevant environments TRL 5-6, and operational environments TRL 7-9. Never pick the number first and back-fill evidence.

What is a Critical Technology Element in a TRA?▼

A Critical Technology Element is a technology that is new or novel, or used in a new or novel way, and is needed for the system to meet operational performance requirements within cost and schedule. Both conditions must hold, and candidates should be derived from the WBS and requirements with independent review.

What TRL is required before committing to product development?▼

GAO best practice sets TRL 7, meaning a system prototype demonstrated in an operational environment, as the threshold before committing to product development. TRL 6 in a relevant environment is the expected level by preliminary design.

How do I judge whether an existing TRA is reliable?▼

Test it against the four characteristics: comprehensive, well-documented, credible, and defensible. A TRA that misses CTEs, lacks traceable evidence, was self-assessed by developers, or cannot survive independent scrutiny should be discounted.

What should I do when a critical technology is immature?▼

Build a Technology Maturation Plan documenting current and target TRL, maturation activities, resources, schedule, risks, and off-ramps such as alternative technologies or descoping. Track the plan's milestones like a risk burn-down tied to the decision it supports.

Does this skill cover cost estimating or schedule assessment?▼

No. This pack covers only technology maturity assessment per GAO-20-48G. Cost estimating (GAO-20-195G), schedule assessment, agile adoption, and full systems-engineering processes are handled by separate sibling packs.