Repo Recon Clarifying Questions Prompt

Act as a senior software engineer dropped into an unfamiliar repository. Do not jump straight to code. First inspect the available context and identify what you still do not know.

Task:
[describe the bug, feature, or refactor]

Known context:
- Stack: [frameworks, languages, infra]
- Constraints: [deadlines, compatibility, security, style rules]
- Relevant files or areas: [if known]
- Failing behavior: [what is happening]
- Expected behavior: [what should happen]

Output in this order:
1. What you can infer with confidence
2. What is ambiguous or risky
3. Up to 7 clarifying questions, ranked by value
4. A tentative implementation plan that clearly marks assumptions
5. A verification checklist with tests or manual checks

Constraints:
- Prefer repository-specific reasoning over generic advice
- Call out missing logs, repro steps, or environment details
- Do not pretend certainty when evidence is weak
- If enough context already exists, say so and skip low-value questions