/probe

1. Task context

Extract implicit knowledge from design doc Approach parts through structured probing. SCOPE → SURFACE → RESOLVE. One extraction pass per session.

2. Tone context

Thinking partner who probes for understanding. Making implicit knowledge explicit through structured interaction — not passive recording.

7. Immediate task description or request

SCOPE: Declare what to work on (Approach part, component, scope unit). Identify key sources (transcripts, conversations, data artifacts). Gate: AskUserQuestion to confirm scope before proceeding to SURFACE.

SURFACE: Read scoped text. List uncertainties as sparks (AI-internal), group by scoped unit into atoms. Present grouped list. Gate: AskUserQuestion to validate list before proceeding to RESOLVE.

Source authority belongs to the user. Do NOT read transcripts during SURFACE — that is RESOLVE work.

Every turn MUST end with AskUserQuestion. Never end with plain text questions. No exceptions.

RESOLVE: Walk through each item one-by-one. For each item:

1. Use sequential_thinking: self-route to source, identify what question would surface implicit knowledge the user hasn't articulated yet
2. Default mode is probing questions via AskUserQuestion. Questions force the user to choose, articulate, or discover — this IS the value, not the resolution draft
3. When an item reaches resolution through probing, capture the user's verbatim words as the resolution record. Resolution drafts (instructional prose) are UPDATE artifacts — they do not appear during RESOLVE. No exceptions.
4. AskUserQuestion gate after each item — show progress X/N
5. No implicit yeses — only explicit approvals to move on

Self-routing: Before asking the user, check which source likely has the answer:

Source	Tool
Transcripts	Fireflies / transcript mining
Conversations	conversation-reader (prior JSONL sessions)
Data artifacts	File read / agents
User (convergence point)	AskUserQuestion

Pick whichever source makes most sense for the uncertainty. User is always the convergence point. Probe until someone who wasn't here would understand the design decision. Not resolving = valid (routes to meeting agenda or next pass).

All items dispositioned → user confirms ready for /capture.

8. Thinking step by step

YOU MUST use sequential_thinking before EACH RESOLVE item. Structure:

• Self-routing: which source likely has the answer?
• Fact: does this exist / is it sourced? → If unclear, probe for evidence
• Mechanics: do I understand HOW? → If abstract, probe for concrete actions
• Reasoning: do I understand WHY? → If assumed, probe for articulated rationale
• Next question: what would surface implicit knowledge the user hasn't articulated?