triple-c

Active orchestrator for multi-agent flight execution. Drives leg design per leg, then batches implementation across all autonomous legs, with a single code review and commit at the end of the flight.

Post-flight analysis for continuous improvement. Use after a flight is completed to capture lessons learned and improve the methodology.

Create technical flight specifications from missions. Use when breaking down a mission into implementable work or planning technical approach.

Initialize a project for Flight Control. Creates .flightops directory with methodology reference and artifact configuration. Run before using other Flight Control skills on a new project.

Generate detailed implementation guidance for LLM execution. Use when creating atomic implementation steps from a flight.

Post-mission codebase health assessment. Run after `/mission-debrief` to verify the codebase is flight-ready or scaffold a maintenance mission. Per-flight findings instead roll into the next flight or accumulate into an end-of-mission maintenance flight — not into this skill.

Post-mission retrospective for outcomes assessment and methodology improvement. Use after a mission completes or aborts to capture overall lessons learned.

Create outcome-driven missions through research and user interview. Use when starting a new project, feature, or initiative that needs planning.