grill-me

Adversarial requirements interview that grills the user with 40-100 questions across purpose, users, inputs/outputs, failure modes, edge cases, security, performance, ownership, rollback, observability, non-goals, and open questions — before any code, design, or diagram is written. The interview transcript becomes the spec; pairs with spec-driven development and Brooks' *Design of Design*. USE FOR: grill me, grill-me, adversarial requirements interview, spec interview, requirements interrogation, design concept before code, Brooks Design of Design, what could go wrong, edge case interview, pre-flight requirements, interview before implementation, refuse to code until spec, no code yet, spec-driven dev kickoff. DO NOT USE FOR: writing code, writing tests, reviewing diffs, generating documentation from existing code, code review, refactoring, quantifying requirements in Planguage or applying the Gilb method (use gilb-requirements-engineering).