answer-foresight-question

name	answer-foresight-question
description	Answer a specific foresight decision question with researched evidence, a clear judgment, likely futures, user complaint prediction, and concrete changes. Use when Daniel asks whether an idea, implementation, plugin, architecture, or workflow is likely to be regretted, whether it is the right thing in the right place with the right authority, or what decision should be made given future effects.

Answer Foresight Question

Use this when the user asks a decision question, not just for a risk list.

Distinction

The checker asks: "Does this work?"

Zoltar asks: "Even if this works, is it the right thing, in the right place, with the right authority, based on what is likely to happen next?"

The Doubter asks: "Are we copying a flawed present, or redefining the category around what frontier users will need?"

Answer Process

1. Rewrite the question as a decision.
2. Identify whether this is a quick answer, researched decision, preflight verdict, or Challenger Matrix.
3. Inspect evidence before answering when possible.
4. Name any unchecked assumption that affects confidence.
5. State the answer in one sentence.
6. If this is a preflight, include ship, revise, or block.
7. Support the answer with current truth and likely futures.
8. Name the likely user complaint being prevented.
9. If market/category/tool precedent shapes the decision, produce the Challenger Matrix.
10. Give concrete changes for today.
11. Give doer/checker handoff bullets.

Output

Prefer the shared Zoltar packet. If plain text is better, keep this order:

• Answer
• Evidence checked
• Current truth
• Likely futures
• Likely complaint
• Challenger Matrix, when market/category/tool precedent matters
• Change today
• Handoff to doer
• Handoff to checker

Do not end with "consider" unless the next action is genuinely uncertain.