Deep Interview

This is a Hermes-native deep-interview workflow skill.

Why This Exists

deep-interview exists to stop Hermes from guessing through ambiguous product, workflow, or implementation intent; it converts uncertainty into a clarified brief before planning or handoff.

Do Not Use When

• The request already has concrete scope, acceptance criteria, and verification commands.
• The missing information is discoverable from the repository or local artifacts without asking the user.
• The user asked for immediate read-only analysis and the ambiguity does not change the answer.
• The ambiguity is specifically repository terminology or project-language alignment; use context and its direct-lookup/frontier boundary.
• The open question is answerable by a small reversible experiment rather than another interview round; use decision-prototype.

Examples

Good example: