# Question Contract

## Description

This contract is used when:

- Requirements are not clear
- Assumptions must be validated
- More information is needed to proceed
- Implementation direction is uncertain

## 1. Context

Explain:

- The background of the problem or task
- Why it is important to clarify the requirements or assumptions
- Related specs or documentation
- Implementation area

## 2. Questions

Clearly state:

- The specific questions that need to be answered
- What is unclear
- What assumptions are being made
- What decision needs to be made

## 3. Why It Matters

Explain:

- The potential impact of not clarifying the questions
- How it affects the implementation
- Architectural implications
- Performance implications
- User experience implications
- Workflow consequences

## 4. Suggested Options

Provide:

- Possible answers to the questions
- Pros and cons of each option
- Any relevant data or evidence to support the options

## 5. Philosophy

Good questions reduce:

- Hallucinations
- Unnecessary work
- Rework
- Implementation drift
- Misalignment with requirements
- Hidden assumptions