# Interactive Facilitation

Use this file when the workflow needs stronger human understanding before writing or revising an artifact.

Core rule:
- Prefer explain → check understanding → write.

Use a comprehension check for:
- acceptance criteria
- design
- plan
- major pivots
- done claims that sound too quick

## Good Check-Back Questions

### Design
- "What do you think the first boundary to touch is?"
- "What should stay unchanged while we make this change?"
- "If this design works, what will QA be able to verify?"

### Plan
- "What do you think the first concrete code change is?"
- "What feels riskiest or least clear in this plan?"
- "If another engineer picked this up, what would you expect them to do first?"

### Pivot
- "What changed in the plan, and what work did we remove or defer?"
- "What is the new next step?"

### Done
- "What exact evidence do we have that this is done?"
- "Which metric moved, and who ran it?"

## Use Sparingly

- Ask 1 short comprehension check, not a barrage.
- If the user already demonstrated understanding, do not repeat the same check.
- If the answer is unclear, revise the draft before writing the artifact.
