Operator-ready prompt for reuse, tuning, and workspace runs.
This item is set up for developers who want to inspect the original language, fork it into Workspace, and adapt the evidence model without losing the source prompt structure.
Implementation handoffs, eval setup, and prompt tuning where you need the original structure intact.
Inspect first, copy once, then fork into Workspace when you want variants, notes, and model settings attached to the same run.
Swap domain facts, examples, and any hard-coded entities for your own context.
Tighten the evidence or verification requirement if this is headed toward production.
Decide which failure mode you want to evaluate first before you branch the prompt.
This prompt already carries implementation detail, tool context, and a final-output instruction. Keep that structure intact when you tune it, or your comparison runs get noisy fast.
Open this prompt inside Workspace when you want a live iteration loop.
Copy for quick reuse, or run it in Workspace to keep prompt variants, model settings, and prompt-history changes in one place.
Structured source with 1 active lines to adapt.
Already linked to a challenge workflow.
Sign in to keep private prompt variations.
Prompt content
Original prompt text with formatting preserved for inspection and clean copy.
Define a realistic On-Orbit Servicing mission scenario for GEO satellite refueling. Specify the initial orbital parameters for the servicer and target satellites, the amount of fuel to be transferred, and the primary optimization goals (e.g., minimize fuel, minimize time). Incorporate at least two realistic constraints such as orbital debris avoidance zones or specific time windows for rendezvous. Use this scenario as the basis for your planning system.
Adaptation plan
Keep the source stable, then branch your edits in a predictable order so the next prompt run is easier to evaluate.
Preserve the role framing, objective, and reporting structure so comparison runs stay coherent.
Swap in your own domain constraints, anomaly thresholds, and examples before you branch variants.
Check whether the prompt asks for the right evidence, confidence signal, and escalation path.
Copy once for a pristine source snapshot, then move the prompt into Workspace when you want variants, run history, and side-by-side tuning without losing the original.
Prompt diagnostics
Quick signals for how structured this prompt already is and where adaptation work is likely to happen first.
This prompt is mostly narrative and instruction-driven, so you can adapt examples and output constraints first without disturbing the structure.
LLM-Driven Dynamic Mission Planning for On-Orbit Refueling & Servicing
On-orbit servicing (OOS), particularly refueling in Geostationary Earth Orbit (GEO), is a critical priority for national security and commercial markets. However, planning these missions involves complex multi-objective optimization under dynamic constraints such as fuel efficiency, rendezvous windows, orbital debris avoidance, and unforeseen operational changes. This challenge focuses on building an AI-powered system that can autonomously generate and optimize OOS mission plans. Participants will develop a system that leverages a sophisticated large language model to interpret high-level mission requirements and dynamic constraints, translating them into parameters for trajectory optimization algorithms. The system should be robust enough to adapt plans in real-time, explain its decision-making, and be scalable through MLOps practices. This addresses the need for agile, intelligent planning in complex space logistics scenarios, moving beyond static pre-planned missions.
Use the challenge page to recover the original task boundaries before you tune the prompt. That keeps your variants grounded in the same evaluation target instead of drifting into a different problem.