Match a job Paths Subjects Questions Quizzes Pricing
Overview Read Practice

Practice — Case Study: Migrate a Production Prompt Suite Across a Model Deprecation (5 questions)

Pro content

Sign up free, then start a 14-day Pro trial — no card needed.

Intermediate Open Free

Triaging 40 Prompts Before Touching Any of Them Permalink →

Your provider announces the model behind your production application will stop working in 60 days. The application has 40 distinct prompts built up over two years by several teams, with wildly different traffic and criticality, and almost none of them have a golden set. A colleague wants to start by opening the highest-traffic prompt file and rewriting it for the new model today.

  1. Explain what's wrong with starting there, and what "safe migration" should mean before any prompt is edited.
  2. Design the inventory/triage step: what axes you'd score all 40 prompts on, and how that scoring determines migration order.
  3. Give a plausible breakdown of the 40 prompts into a few triage buckets and say which bucket you'd migrate first, with reasoning.

Share this question

Advanced Open Pro

Building Golden Sets Retroactively Under a Deadline

Unlock this question →
Advanced Open Pro

Reading a First-Run Regression Report

Unlock this question →
Advanced Open Pro

Choosing a Rollout Strategy and Rollback Triggers

Unlock this question →
Advanced Open Pro

The Migration Looks Done. What Could Still Go Wrong?

Unlock this question →

We use cookies for product analytics to improve OmniAtlas. See our Privacy Policy.