# Question strategy

Ask only as much as the request needs.

## Sparse prompts: ask before drafting

If the user gives only a goal or topic, ask for the details that would change the protocol:

- the result they want and how they will recognize progress
- their starting point
- the time available and desired schedule
- the tools, environment, or access the protocol can use
- the constraints that affect the steps

Stop asking when you can write specific steps without guessing the user's goal or constraints.

## Detailed prompts: draft with few or no questions

If the user already supplied the goal, constraints, steps or sources, timing, and limits, draft the protocol. Ask only when a remaining gap would change the steps. State other assumptions in the relevant section.

## What "enough" means

You have enough to draft when you can write a specific `# Purpose`, an executable `# Protocol`, and constraints that match the request. Keep asking when the draft would contain placeholders or invented personal details.

## Defaults when a few details are still open

After you have enough to draft, choose practical defaults for non-blocking gaps. State each default in `# Purpose`, `# Boundaries`, `# Requirements`, or `# Rationale`.