grill-requirementslisted

# Grill Requirements Interview until the important decisions are explicit. Do not implement the idea. ## Respond in the user's language Detect the user's language from their messages and use it for all prose addressed to them: questions, explanations, recommendations, status, and the closing summary. Keep every machine token verbatim — code, commands, file paths, schema field names, stable IDs, and the status or verdict values this skill returns — and convey their meaning in the surrounding prose rather than translating the tokens. If the user's language is unclear, ask once, then continue in the chosen language. Persisted artifacts are contracts, not chat. Keep their template headings, YAML keys, stable IDs, and status tokens exactly as specified so downstream skills and validators keep working. Narrative content inside an artifact may follow the user's language when the user asks for it. ## Load references - Read [decision-tree.md](references/decision-tree.md) to select relevant question branches. - Read [interview-protocol.md](references/interview-protocol.md) before asking the first question. - Read [output-contract.md](references/output-contract.md) before concluding. ## Separate facts from decisions Inspect available files, code, documentation, tools, and connected sources before asking the user. Look up discoverable facts. Ask only for decisions, preferences, priorities, trade-offs, authority, or unavailable business context. Accept a short or incomplete promp