flight

To turn high-level project missions into actionable flight specs, you run a specification workflow that breaks missions into flights and legs, applying artifact-aware planning and phase-based workflows to guide implementation and testing.

Artifact-aware planning aligns engineering work with project artifacts and artifact locations to ensure traceability. In flight specifications, it reads artifact configurations to tailor the flight plan to the target project's codebase reality.

To generate end-to-end flight plans that align with your codebase architecture, the specification workflow verifies prerequisites, reads artifact configurations, and consults the codebase to tailor the flight plan to the target project.

Yes, you can use design reviews and crew interviews to validate your approach against codebase reality and architecture best practices, ensuring the generated flight plans accurately reflect your project's artifact configurations.

Yes, you need project artifacts like .flightops configurations and defined artifact locations. The specification workflow must verify these prerequisites and read artifact configurations before tailoring the flight plan to your target project.

The best way to track changes during flight specification generation is to use the workflow's built-in change tracking and artifact management, which ensures traceability between your engineering work and project artifacts throughout the mission breakdown.