From need to generative specification

Review questions

From need to generative specification

Professional practice starts with a task card: who uses the output, which decision it supports, what input is permitted and what output is acceptable. Success remains bounded by what was tested; a good draft register does not prove better follow-up. The specialist then distinguishes deterministic rules, retrieval and generative wording, combining them only when the task requires it. Context is a limited resource, and text being present does not guarantee correct use. Before prompt refinement, the specialist marks what may be invented, what must remain grounded and what must be reported as unknown. The result is a checkable specification rather than an open rhetorical request.

Review questions

Test your understanding with these questions. Marking and saved results are available with a free account.

  1. Question 1Synthetic minutes state: “The team proposed moving training to Wednesday; the decision was deferred to a later meeting.” What belongs in an approved-decision register?
  2. Question 2A task card asks for the role responsible for a decision. The decision is approved but no role is assigned. Which output follows the evidence?
  3. Question 3The original file contains six rows, the saved request only four, and the answer covers those four. Where should diagnosis begin?
  4. Question 4A model gives the same product name three times although it is absent from the supplied source. What does repetition establish?
  5. Question 5A fictional organization only needs the sum of structured numeric values. What is a suitable simple baseline?
  6. Question 6A well-written answer uses an archived version when the task asks for the effective procedure. What is the primary defect?