A message addressed to the product thinker, a question above all, still carries mechanism details (file names, flags, internal terms, how the code does it) where the product thinker needs only the choice and what each answer leads to, in plain words. Questions put to the product thinker must always be simplified: cut the mechanism and state the decision by its outcomes.

A message addressed to the product thinker, a question above all, still carries mechanism details (file names, flags, internal terms, how the code does it) where the product thinker needs only the choice and what each answer leads to, in plain words. Questions put to the product thinker must always be simplified: cut the mechanism and state the decision by its outcomes.

Checked at the default branch 2026-10-28

Partly met since: abcd's own interview questions now address the product thinker in outcomes, with no record ids, code or internals (internal/core/question/asking.go, agents/question-drafter.md), and the question check enforces part of it. Still open: messages to the product thinker that are not questions, and file and flag names in them.