init-project

Bootstraps Flight Control projects by creating .flightops directory and configuring crews, migrations, and CLAUDE.md sync.

2|1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/msieurthenardier/mission-control --skill init-project-msieurthenardier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init-project
Source: https://github.com/msieurthenardier/mission-control/tree/main/.claude/skills/init-project
Command: npx skills add https://github.com/msieurthenardier/mission-control --skill init-project-msieurthenardier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates the .flightops directory and wires up the methodology reference and artifact configuration for a new Flight Control project, ensuring a consistent bootstrap every time.

Core Features & Use Cases

  • Creates the .flightops directory at project root with the Flight Control methodology reference and artifact configuration.
  • Applies migrations to reconcile legacy layouts and updates CLAUDE.md with Flight Operations guidance.
  • Configures default agent crews and references to streamline project setup and onboarding.

Quick Start

Run /init-project on a new project to bootstrap the Flight Control workspace.

Frequently Asked Questions about init-project

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap a Flight Control project workspace?

To bootstrap a Flight Control project, run /init-project to automatically create a .flightops directory with methodology references, artifact configuration, and default agent crews for consistent onboarding.

What does flight control project initialization do to existing files?

Flight Control project initialization applies migrations to reconcile legacy layouts and updates CLAUDE.md with flight operations guidance to standardize documentation.

Can I use project setup tools to migrate a legacy directory layout to Flight Control?

Yes, the setup process detects legacy directory layouts and applies migrations to reconcile them into the standardized Flight Control artifact structure.

What is the best way to standardize project documentation and crew definitions during onboarding?

The best way to standardize onboarding is to use a bootstrap workflow that enforces consistent project documentation, crew definitions, and artifact structure in one step.

Do I need a specific environment to configure default agent crews for Flight Control?

No specific environment is required beyond a target project directory where the setup can create the .flightops directory and sync the necessary configuration files.