# Questions and saved plans

Canonical: https://synthcrew.io/docs/questions-plans

## Answer a question [#answer-a-question]

When the agent needs a decision, read the question and the consequence of each option. Select the intended answer or enter a different answer where offered. For a group of questions, check which question is active and whether the interface is waiting for more answers.

Keyboard navigation inside questions is different from the composer: Tab moves between answer controls rather than changing Plan mode. Use the visible submission action to confirm the full response when required. Cancel or Stop is not an affirmative answer.

Do not supply passwords, MFA codes, API keys or access tokens through a question. Authenticate with the legitimate provider flow instead.

## Read a proposed plan [#read-a-proposed-plan]

A saved plan describes intended work; it is not a record of applied modifications. Review the goal, assumptions, deliverables and acceptance checks. Open its preview to inspect the complete document, not only the streamed excerpt.

If implementation is offered, approve only after the plan matches your request. To change direction, explain the specific adjustment instead of accepting an unclear plan. Saving or opening a plan must not silently start an Agent run or apply an existing candidate.

## Preserve provenance [#preserve-provenance]

The plan belongs to its request and conversation. Editing the user request creates a new revision; earlier questions and approvals must not automatically authorize that revision. Candidate review and Apply still require their own checks.

## Interrupted or missing question [#interrupted-or-missing-question]

A provider or application interruption may make a question no longer answerable. Preserve the conversation and inspect its terminal status. Do not assume an old response was received or use an unrelated Reply control to resume it. Follow [interrupted requests](/docs/interrupted-runs) and include the question state in a support report.