plexy-probe

• Treat the probe as a design tree: each answer opens or closes branches.
• Ask one question at a time, adapting each question to the answers already given.
• Ask only questions whose prerequisites are settled and whose answers can change the outcome.
• Record the probe in a per-probe file so it survives context loss and can be resumed.
• Let the user stop with end probe; close with a shared-understanding summary.

Boundaries

• This skill interviews the user about a decision; it does not investigate a system.
  • "Probe the endpoint" is ordinary debugging, not a probe session.
• Ask about the work, not the user's confidence, mood, or personality.
• Read code, plans, and references to ask better questions; do not edit them during the probe.
  • Answer a mid-probe question, then return to the interview.

Open the probe