按任务选择模型档位与推理设置
结合任务难度、错误代价与响应要求,给出模型档位选择、升降级条件及验证方案。
完整提示词
<context>
Most people use one model for everything: the largest, paying in waiting time, cost and usage caps for work a smaller model does as well, or the default, and then trust it on work it gets wrong. Model names and prices change every few months, so the durable decision is the tier:
- small: fast and cheap; classification into fixed labels, extraction against a clear schema, routing, short rewrites and formatting;
- mid: most writing and editing, summarising, answering from documents you provide, everyday code and spreadsheet formulas;
- frontier: multi-step reasoning, ambiguous or novel problems, long agentic work, subtle judgement and output where a mistake is expensive.
A reasoning or thinking setting is a second dial. It helps when the answer needs planning, maths, weighing evidence or checking its own work, and only adds delay to lookups, rewrites and formatting.
This gives a reasoned first choice and a check sized to the stakes. A production feature that needs measured success criteria, latency percentiles and a test harness needs a full evaluation, not this shortcut.
Setting: {{setting}}
Volume: {{volume}}
<task_description>
{{task}}
</task_description>
{{#constraints}}
<constraints_given>
{{constraints}}
</constraints_given>
{{/constraints}}
</context>
<task>
1. If you cannot tell what goes in and what must come out, ask up to two questions and stop.
2. Profile the task on: reasoning depth, ambiguity, knowledge needed beyond the input, input length, output length and how strict its format is, number of steps or tool calls, cost of an error, latency need and volume. Rate each low, medium or high.
3. Recommend one tier and one reasoning setting (off, on for hard cases only, or on), with your confidence (low, medium or high) and the two or three factors that decided it. Lean towards the smaller tier when volume or latency matters and errors are cheap or caught downstream; lean larger when one error costs more than many runs.
4. Say how to apply it in the setting: in a chat app, which kind of option to pick (the fast everyday model or the most capable one, thinking on or off), described generically; in an API or automation, the tier and the reasoning parameter; for an agent, whether a larger tier should plan while a smaller one carries out routine steps. If the setting is unsure, cover the chat-app and API cases in one line each.
5. Recommend a split only when it clearly pays: a cascade (small first, escalate when a check fails or the model is unsure), a pipeline (small for extraction or routing, larger for synthesis), or batching for work that is not urgent.
6. List the signs during use that mean step up (repeated misreadings, invented details, broken format, skipped steps) or step down (the larger option gives the same answers, waiting time or usage limits hurt).
7. Size a quick check to the volume and risk:
- occasional use by hand: run three to five real, recent examples through both options side by side, including one hard one, and compare against what you would have accepted;
- recurring or automated work: 20 to 50 representative inputs including edge cases, scored by a stated check, through the recommended option and the adjacent one, recording pass rate and rough time and cost per run; move to a full evaluation if it becomes a product feature.
8. Write the decision rule before the check is run.
</task>
<constraints>
- Name tiers only, never specific models, vendors, prices or limits; tell the user to check what their tool or account currently offers.
- Tier boundaries move as models improve. State your confidence honestly; the quick check, not this recommendation, makes the decision.
- When errors could harm people (health, legal, financial or safety decisions, or decisions about individuals), recommend human review of the output whatever the tier.
- If a constraint rules out a tier, such as self-hosting limiting model size or a usage cap, say so and adjust.
- Keep the answer short enough to act on in a few minutes.
</constraints>
<output_format>
## Task profile
Table: Factor | Rating | Note.
## Recommendation
Tier, reasoning setting, confidence and deciding factors in three or four lines, then how to apply it in the setting and any split.
## Step up or down when
Two short bullet lists: step up, step down.
## Cost and latency
Two to four bullets in relative terms: what scales the cost and where the waiting comes from.
## Quick check
Numbered steps sized to the volume.
## Decision rule
One or two sentences, written before running.
</output_format>可替换内容
- {{setting}}
- {{volume}}
- {{task}}
- {{#constraints}}
- {{constraints}}
- {{/constraints}}
分类与标签
思维提升、模型选型、推理设置、成本权衡、效果验证