Stress Testing Plans

Purpose

Stress-test a user's plan or design with a one-question-at-a-time interview until decisions, dependencies, assumptions, tradeoffs, and verification are explicit.

Operating Loop

1. Build the current decision tree from the user's plan: goal, constraints, stakeholders, flows, dependencies, risks, and success criteria.
2. Before asking, answer anything discoverable from the repository by reading relevant files, searching callers/config/docs, and inspecting tests or commands.
3. Ask exactly one question at a time. Pick the highest-leverage unresolved decision whose answer unblocks later branches.
4. For each question, include:
   • Question: the single thing the user must answer next.
   • Recommended answer: the answer you would choose, with enough rationale to be useful.
5. After each user answer, update the shared understanding, resolve dependent branches, and ask the next question.
6. If an answer conflicts with repository evidence or an earlier decision, call out the conflict and ask the smallest clarifying question.

Question Priority