Question 3
Domain 1An engineering team has a recurring multi-step request: 'Generate weekly release notes from the last 7 days of merged PRs.' Users want one-click access. Which primitive is the right shape?
Correct answer: A
Explanation
A prompt is the right primitive because this is a recurring, multi-step request that users want as “one-click access,” which fits a reusable template rather than a one-off command. The `weekly_release_notes` prompt can encapsulate the workflow and expose optional slots like `start_date` and `repo` for user input.
Why each option is right or wrong
A. Prompt — a `weekly_release_notes` template the user picks from the menu, with optional `start_date` and `repo` slots.
The correct primitive is a prompt template because the request is a reusable, multi-step workflow that should be surfaced as a menu choice rather than executed as a single ad hoc action. In the OpenAI Apps/Responses tool model, prompts are the reusable, user-invoked templates intended for repeated tasks with parameter slots; here, `start_date` and `repo` are the appropriate optional inputs to parameterize the weekly report generation without forcing a new command definition each time.
B. Resource — exposed as a URI of the last 7 days of PRs.
A resource represents data to read, not a reusable instruction workflow for generating an output.
C. Tool — `generate_release_notes` the model calls when it senses the user wants notes.
A tool is for executable actions the model invokes, not a user-facing one-click template.
D. Three separate resources, one per day, that the user attaches manually.
Three daily resources expose fragments of input and force manual assembly instead of simplifying the task.