Skip to content
Back to skills

Mission Planning

ASecurity

Use when designing space missions, computing launch windows, optimizing trajectories, analyzing payload constraints, or planning mission phases and contingencies. Use when "mission design, launch window, trajectory optimization, mission timeline, mass budget, propellant budget, mission phases, porkchop plot, C3, gravity assist, low thrust, mission architecture, LEO, GEO, interplanetary, " mentioned.

  • 137 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 10, 2026
developmentrust

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned February 12, 2026

npx -y skills add omer-metin/skills-for-antigravity --skill mission-planning --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Mission Planning?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Mission Planning
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/omer-metin-mission-planning/badge)](https://www.skillsdirectory.com/skills/omer-metin-mission-planning)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: mission-planning
description: Use when designing space missions, computing launch windows, optimizing trajectories, analyzing payload constraints, or planning mission phases and contingencies. Use when "mission design, launch window, trajectory optimization, mission timeline, mass budget, propellant budget, mission phases, porkchop plot, C3, gravity assist, low thrust, mission architecture, LEO, GEO, interplanetary, " mentioned. 
---

# Mission Planning

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Files in this skill

  • SKILL.md1.3 KB
  • references/patterns.md1.7 KB
  • references/sharp_edges.md6.1 KB
  • references/validations.md2.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…