Pressure test
Use this method to sharpen a plan before implementation. Walk the user through the important assumptions, dependencies, tradeoffs, and likely failure modes.
Core behavior
Ask exactly one question at a time and wait for the answer. Give a concrete recommended answer before each question, so the user can accept, correct, or reject something specific.
When available evidence can answer a question, inspect that evidence instead of asking the user. Relevant evidence can include repository files, supplied customer records, project ledgers, research, or approved system exports. Do not assume any of those sources exist or that you have access to them.
Context selection
Load only the context that bears on the decision:
- a relevant current project or decision record for delivery work; - approved organization positioning, capacity, pricing, or policy guidance for an organization-level decision; - supplied opportunity, buyer, process, or evidence records for sales work; - the applicable authoring and evaluation guidance for a new or changed skill.
If required context is unavailable, say what is missing and pressure-test the assumption rather than inventing it.
Interview loop
Repeat until the user says the plan is clear enough to build:
- State the decision under review in one sentence.
- Identify the highest-risk unresolved assumption or dependency.
- Give the recommended answer and the evidence supporting it, if any.
- Ask one question that could confirm, correct, or reject that answer.
- Wait for the reply and update the decision tree before continuing.
Favor questions about the person who must live with the result, prerequisites, timing, budget, data quality, access, system-of-record ownership, required approval, and verification.
For sales or partnership decisions, pressure-test the business problem, the expected value, buyer and reviewer coverage, decision process, proof, pricing anchor, objections, commitments, and next decision. Use a sales qualification framework privately as a completeness check; do not turn it into a scorecard unless requested.
Output format
```markdown Current decision: [one sentence] Recommended answer: [concrete recommendation] Evidence: [optional, concise] Question: [exactly one question] ```
Boundaries
- Do not implement the plan during the interview unless the user explicitly exits the interview and asks for implementation. - Do not create durable records, send messages, publish content, schedule events, spend money, or change external systems. - If the user wants settled decisions captured, hand off a clearly labeled proposal to the host's configured decision-record or project-record process.