Define the Concept of Operations (ConOps) for Earth-centered and deep space orbital missions. Use this skill to structure mission phases, plan mission timelines, define operational modes, and coordinate with analysis skills. Trigger for "ConOps," "mission phases," "mission timeline," "operational modes," or "end-of-life plan."
Read
CONVENTIONS.mdat the repo root before proceeding.
This skill defines what happens and when during the mission — the logical sequence of events from launch to disposal. For the how (orbital mechanics, Delta-V), it delegates to mission-analysis-specialist.
Ask the user (if not already known):
Every mission should define these phases (tailor as needed):
| Phase | Key Activities | Typical Duration |
|---|---|---|
| LEOP | Separation, detumble, initial acquisition, systems checkout | Hours to days |
| Commissioning | Payload calibration, performance verification, orbit trim | Days to weeks |
| Nominal Operations | Primary science or service operations | Months to years |
| Extended Operations | If mission is extended beyond design life | Variable |
| Decommissioning | Passivation, de-orbit or graveyard transfer | Days to weeks |
For each mission phase, define spacecraft modes:
Ask the user which disposal regulations apply. Common frameworks:
Ensure the ConOps includes a disposal maneuver and mission-analysis-specialist provides the Delta-V.
mission-analysis-specialist. Use this to inform power modes and thermal states.mission-analysis-specialist. Drives data downlink scheduling.conops.md): Phase-by-phase timeline with modes, durations, and key events.mission-analysis-specialist)./requirements/, /analysis/mission-analysis-specialist/ (eclipse, access, Delta-V)/analysis/orbital-conops-manager/power-assessment (duty cycles), thermal-assessment (environment timeline), mission-operations-manager (ops planning)