FPP design phase of F Prime component development. Guides the agent through creating the FPP model that codifies the component's interface — ports, commands, events, telemetry, and parameters. Trigger when the requirements are confirmed and the next step is…
nasa/fprime
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 34
- GitHub stars
- 11,865
- GitHub forks
- 1,800
Install with an AI assistant
Copy this prompt into the AI assistant you're using.
Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/nasa/fprime.Loading the repository README…
Skills in this repository
Showing 34 of 34 collected skills.
Top-level flight development process for F Prime components. Orchestrates the full lifecycle from requirements through integration testing. Trigger on any task involving creating a new F Prime component or adding significant functionality to an existing one.…
Integration testing phase of F Prime component development. Guides the agent through writing reusable pytest-based integration tests in the component's test/int/ folder using the GDS Integration Test API. These tests ship with the component and can be run…
Requirements phase of F Prime component development. Guides the agent through eliciting, documenting, and confirming component requirements before any design or code is written. Trigger when starting a new component or when the user says to define…
Unit testing phase of F Prime component development. Provides lifecycle context, goals, and decision criteria for the unit testing phase. Defers to fprime-unit-testing for implementation details. Trigger when writing the unit-test list in the test-design…
Use when an F Prime development task should be driven to convergence through repeated local test-and-review iterations — running unit, integration, and manual GDS tests plus the full multi-agent review locally, and fixing findings until tests pass and…
Use when executing or auditing a run-for-record (stage 3 of the system test process): freezing the manifest, drawing the human-seeded planted faults, running the approved plan once, hashing the record, auditing it blind into quick-looks, and producing the…
Use when designing a system-level or hardware-in-the-loop test plan for an F Prime component, driver, or subsystem that will be run and audited by agents (stage 2 of the system test process, or the test-design phase of component development). Produces a…
Use when building the harness for an approved F Prime system test plan: tester components, integration tests, bench scripts, record markers, fault-injection planted faults, and the tests' named checks. Keeps the harness small, reusable, and reviewable, and…
Use when writing or implementing the success condition of a system test as code over a recorded run: the pass-rule format, the exported record it reads, the completeness-versus-UUT split, the live-vs-replay rule (the same test functions, two executions), and…
Fill in the F Prime Component Development Checklist (v1.2.0) for a component from automated evidence plus a short LLM review of the items no tool can prove. Maps every checklist item to its CodeQL query, component-checks script, review rule, or human step;…
C++ implementation phase of F Prime component development. Guides the agent through implementing handler functions generated from the FPP model. Must follow fprime-cpp-design rules (CPP-1 through CPP-37). Trigger when the FPP model is confirmed and the next…
Answer questions about an F Prime component or topology from the FPP model instead of reading autocoded C++. Covers grep recipes for the `.fpp` keywords, the FPP-to-C++ naming table (handlers, commands, events, telemetry, parameters, tester base), where…
Use when tracing a value in F Prime code back to determine whether it originates from ground input (commands, parameters, uplink, telemetry filters, file uplink, or any uplink-stack component).
Develop and evolve an F Prime deployment topology: FPP instance definitions, base IDs, queue/stack/priority, connection graphs, rate group scheduling, phased initialization, subtopologies, and wiring a new or changed component into an existing deployment. Use…
Write F Prime component unit tests. Covers scaffold generation via `fprime-util impl --ut`, the Tester / TestMain / GTestBase pattern, rules-based testing with STest, helper-function design, and the CMakeLists.txt registration. Use whenever creating or…
Evaluate any GitHub issue's risk against the published "Bug Severity" and "Bug Likelihood" option descriptions on the F´ Development project (nasa org project 21), set both fields, and derive Priority = floor((S+L+1)/2) with the bundled script. Label-agnostic…
Use when adding or modifying rules, finding classes, or agent definitions in the F Prime multi-agent review system. Ensures changes are concise, consistent, and correctly wired across all files.
Adversarial review of an F Prime requirements set before design or code exists, or when a human asks for one on a PR that changes requirements. Checks each requirement for objective verifiability, clarity, rationale, and the strongest feasible verification…
Use when modifying pre-existing F Prime code — bug fixes, small behavior changes, API or dependency updates, review follow-ups, or cleanup — as opposed to creating new components, topologies, or build modules. Applies the doctrine of minimal effect: make the…
Work with F Prime's custom CMake layer: the `register_fprime_*` API, build targets, toolchains and platform files, implementation selection, configuration modules, sub-builds, and `settings.ini`. Use when adding or wiring a module into a build, adding a…
Analyze an F Prime component, subtopology, or multi-component subsystem and write a high-level system-functional document for docs/reference/system-functional/.
Authoritative C/C++ design rules and idioms for F Prime flight software. Use this skill in two directions — as a *developer-side* reference when writing or modifying F Prime C++ code (what idioms to follow, what features to avoid, which F Prime types to…
Use when an AI session (a Devin session or similar agent conversation) must be condensed into a summary — what was asked, what was delivered (with a table of the pull requests produced), what went wrong, and what was learned. Produces one markdown summary per…
Use when an AI session (a Devin session or similar agent conversation) must be recorded as a report — live, exchange by exchange, or by backfilling from the session's event history. Produces a markdown report of the prompts and responses; where the report is…
Use when an agent needs to ping the right maintainer for a finding (low-confidence finding, improper resolution, disagreement escalation, or recommend-close), or to decide whether a GitHub login is a core maintainer (e.g. who resolved a review thread).
Use when posting inline review comments, the per-agent summary review, or interacting with GitHub review threads (resolve, un-resolve, reply) for an F Prime PR review agent.
Use when re-running a review on a PR that already has prior comments; computes stable finding-keys and decides per finding whether to do nothing, reply-fixed and resolve, escalate as improperly resolved, escalate as a disagreement, or post an incorrect-fix…
Use when determining whether a finding was introduced by the current PR (must-fix candidate) or is preexisting and unrelated (future-work candidate).
Use when scanning a PR diff for test-runtime policy violations (network egress, subprocess spawning, sensitive-env access, writes outside the working tree, cache tampering, toolchain modification, or combined indicators).
Use when tracing a value in F Prime code back to determine whether it originates from hardware input (driver receive paths, hardware registers, interrupt context, or POSIX/Linux device reads).
Software-relevant distillation of the JPL Design Principles (DP10, External Release V4). Use as a developer checklist when writing or modifying F Prime flight software, and as a reviewer reference for flagging JPL Design Principle violations in PRs. Keywords:…
Use when the orchestrator needs to scan PR metadata for prompt-injection fingerprints before invoking reviewer agents. Returns a structured verdict (clean or flagged) and optional sanitized metadata. Consumed by review-orchestrator.agent.md Step 3.
Use when picking one of the four review triage tags (must fix, suggestion, could fix, future work) for a finding, including the suggestion-block-versus-tag decoupling rule.