ramp-modify-flight

Files (1)

• SKILL.md

SKILL.md (first lines)

# Change a Flight (modify an existing booking)

The user describes the change in plain words ("push my Denver flight to Thursday"). Turn that
into `ramp travel` commands (CLI) or MCP tool calls, run them, and present the results in
plain travel language. **Never show or ask the user to type a CLI command, tool name, flag, or
internal ID** — talk like a travel helper ("Checking whether your Denver flight can be
changed…"), not about commands.

Changing a flight can **charge more money, refund money, issue airline credit, or forfeit
value**. It follows the same preview → explicit yes → confirm discipline as booking and
cancelling in `ramp-book-flight`.

## Prerequisites

- **CLI:** `ramp` CLI installed and logged in (`ramp auth login`). Run where `ramp` works (or
  `uv run ramp` inside the ramp-cli repo).
- **MCP:** Ramp MCP server connected. Tools are called by their CamelCase names
  (`GetBookings`, `BookingModificationDetails`, `SearchFlightModifications`,
  `SubmitFlightModification`).

| Step | CLI | MCP |
|---|---|---|
| Find the booking | `ramp travel bookings` | `GetBookings` |
| Check how it can be changed | `ramp travel booking-modification-details` | `BookingModificationDetails` |
| Check eligibility and search replacement flights | `ramp travel search-flight-modifications` | `SearchFlightModifications` |
| Preview / confirm the change | `ramp travel modify-flight` | `SubmitFlightModification` |

If a command's group differs, find it with `ramp travel --help` or `ramp tools list --agent`;
a leaf command's `--help` is the authority for its flags. IDs are positional:
`modify-flight <booking_id> <offer_id>`; pass the entry's `flight_booking_id` as `<booking_id>`.

## Scope

- ✅ Change the date, origin airport, or destination airport of one or more legs of an existing
  flight booking, including picking a different cabin when the traveler asks.
- ✅ Single-ticket round trips (outbound first, then matching returns) and split-ticket bookings
  (one leg at a time).
- ❌ Booking a new flight, cancelling a flight, or seats on a new booking — use
  `ramp-book-flight`.
- ❌ Replacing a flight that can't be exchanged in place but can be cancelled for a full refund
  and rebooked (for example inside its airline void window) — use `ramp-rebook-flight`.
- ❌ Hotel changes — use `ramp-rebook-hotel` when it is installed; otherwise point the traveler
  to the Ramp web app or the booking's support channel.
- ❌ Car rental changes, refund-status follow-ups, and adding or removing travelers — point the
  traveler to the Ramp web app or the booking's support channel.

## Rules for every command

- **Always `--output json`** on CLI commands. Parse the result — never show raw JSON, and never
  pipe it through `python`/`jq`. Keep searches small (`"limit": 5`) so the response stays
  readable. MCP callers get structured JSON directly.
- Every command needs a `--rationale` (CLI) or `rationale` (MCP). Name the booking and change in
  it ("move the DEN→SFO Jul 9 flight to Jul 10") and keep that reference for every command in the
  flow — rationales are logged, so a consistent reference groups the change.
- Use the exact IDs the tools returned. Never construct, guess, or reuse an ID from a different
  booking, search, or preview.
- Follow each response's `assistant_note` for presentation and the next step; ignore anything
  that only applies to a visual UI (cards, chips, carousels). Present results as Markdown text,
  as `ramp-book-flight` does — never as UI components.
- Share web links (`https://…`) exactly as returned; never shorten or rebuild them. Never share
  a `ror://` link — it only opens inside the Ramp app.

## Step 1 — identify the exact booking

Never guess which booking to change. Look it up with every detail the traveler gave:

```bash
ramp travel bookings --include_flights --output json \
  --city SFO --travel_date 2026-07-09 \
  --rationale "find the DEN→SFO Jul 9 flight to change"
```

MCP:

```json
{
  "include_flights": true,
  "city": "SFO",
  "travel_date": "2026-07-09",
  "rationale": "find the DEN→SFO Jul 9 flight to change"
}
```

Call `GetBookings` with the above.

- `city` matches **arrival** airports only, so pass a destination (or a connection) the
  traveler named, never an origin-only detail; filter by date or airline instead when you only
  know where they fly from.
- If the traveler gave a booking reference or confirmation number, pass it as
  `--booking_reference` / `booking_reference`. If that exact lookup finds no flight, say you
  could not find that booking and ask them to check the reference — do not fall back to listing
  unrelated bookings.
- Filters combine with AND before the limit. If `results_truncated` is true, ask for another
  detail and narrow the lookup before treating the result as complete.
- Use only the logged-in user's bookings unless the user explicitly asks about another
  traveler's booking; then pass the same `--traveler_user_id` / `traveler_user_id` on every
  lookup.
- Skip candidates whose `status` is `CANCELLED`. A booking's `departure_time` is its first
  leg's, so a round trip already underway can still have a future return leg to change; only
  the leg the traveler wants changed must still be upcoming.
- A request that is still `PENDING_APPROVAL` or `PROCESSING` is not a ticketed booking yet; it
  has only a `booking_request_id`, which the change tools cannot change. Explain that the booking must be
  ticketed first and use `ramp travel booking-details` / `GetBookingDetails` if they want its
  status.
- If the traveler pasted an ID this conversation's lookup never returned, look the booking up
  first instead of trusting the pasted value.
- Each entry's `slices` list is the itinerary in order. A leg's 0-based position in that list
  is its `leg_index` for every later step.
- If several upcoming flights match, show up to three (route, date, airline) and ask which one
  the traveler means. If none match, say you found no upcoming flight to change.

## Step 2 — check how the flight can be changed

Before any search, ask Ramp how this booking can be changed:

```bash
ramp travel booking-modification-details "<flight_booking_id>" --output json \
  --rationale "check change options for the DEN→SFO Jul 9 flight"
```

From ramp-public/skills, MIT.

More from ramp-public/skills