# Skill: Spec Interview

Purpose: Elicit clear, unambiguous requirements before drafting a technical spec.

## Steps
1. Ask what problem is being solved and for whom.
2. Identify the affected stack(s) (ASP Classic, VB6, C#, PHP, and which database engine).
3. Clarify inputs, outputs, and edge cases (invalid input, empty data, concurrency).
4. Confirm acceptance criteria in Given/When/Then format.
5. Identify files/modules likely affected.
6. Confirm rollback or backward-compatibility needs if database schema changes are involved.
7. If `.devfoundry/references/environments.md` or `.devfoundry/references/data-dictionary.md` lacks project facts needed by Builder or QA, ask before drafting the spec and record the answer in the relevant reference file. Do not guess. At minimum, confirm build/test/lint commands, runtime versions, database engine and schema source, driver constraints, and legacy error-log paths when they apply.
8. Summarize findings back to the user for confirmation before drafting the spec.