Make a Hard Decision
Interaction
When missing information materially changes the outcome and the host exposes a dedicated user-input or question tool, use that tool. Ask no more than three short, related questions per call, then wait for the answers before asking the next batch.
Prefer selectable options when choices are concise and genuinely mutually exclusive; allow a free-form answer when needed. Do not present a long questionnaire in normal chat. If no native input tool is available, ask one concise blocking question at a time. For non-blocking gaps, state the assumption and continue.
Create a decision record that protects the user's present reasoning from hindsight.
Frame one decision
Ask for the choice, owner, deadline, objectives, constraints, affected people, and available options—including wait, test, or do nothing where real.
Separate this decision from later decisions it may create. A frame is complete when it can be answered with one choice.
Record the current model
Capture evidence, assumptions, important unknowns, expected outcomes, confidence, and what would change the choice. Use probabilities only when they help; preserve the user's uncertainty rather than manufacturing precision.
Match process to reversibility
For reversible choices, prefer a bounded test and a review trigger. For irreversible or high-downside choices, require stronger evidence, stakeholder consent where relevant, and explicit safeguards.
Run PREMORTEM.md, then write DECISION-RECORD-FORMAT.md.
Review later
At the review date, judge two things separately:
- Process quality: did the decision use the information and safeguards reasonably available?
- Outcome: what actually happened?
A good outcome does not prove a sound process, and a bad outcome does not prove a poor one.
Do not make medical, legal, financial, or safety-critical decisions for the user. Surface where qualified advice or another person's consent is required.