flight-debrief

To generate a post-flight debrief, trigger the flight-debrief workflow to load context, conduct interviews with developers and architects, perform deep analysis, and output a formal artifact capturing actionable findings for continuous improvement.

A structured post-mortem workflow guides engineers, architects, and operators through context loading, role-specific interviews, and deep analysis to identify deviations and produce a standardized, repeatable debrief artifact after a flight lands.

You conduct developer and architect interviews during a post-flight debrief using standardized prompts managed by the workflow, which include fallback mechanisms to ensure consistent context gathering and deep analysis across roles.

Yes, you can use flight-debrief for post-mission analysis without external dependencies, as it operates independently to guide context loading, interviews, and artifact generation within the mission-control workflow.

You need to trigger formal debrief artifact generation immediately after any completed flight lands within the mission-control workflow to review deviations, capture lessons learned, and ensure traceability for future iterations.

The best way to standardize post-flight analysis is using a phase-driven workflow with standardized prompts for interviews and deep analysis, ensuring repeatable debriefs that capture actionable findings to prevent recurring issues.