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…
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…