Module 03: Precision Requirements: Using /grill-me to Kill Bugs Before Writing Code

Over 80% of software bugs are not caused by bad programming syntax. They are caused by bad requirements—unspoken assumptions, vague edge cases, and missing error paths. In the Antigravity workflow, the /grill-me command turns your AI into an aggressive Staff Engineer who refuses to write a line of code until you resolve the ambiguities.

1. What Happens During a /grill-me Session?

When you trigger /grill-me on a feature concept (e.g., "I want to add a customer subscription cancellation flow"), Antigravity pauses standard execution and initiates a structured Socratic interview:

• "What happens to the user's access if a payment fails mid-cycle? Do they retain access until the end of the billing month, or are they downgraded immediately?"
• "How do we handle idempotency if the user double-clicks the cancel button?"
• "Do we need a soft-delete retention period for GDPR compliance, or is it hard deletion?"
• "Should we send an automated webhook to the billing provider before or after updating the local database?"

2. The Socratic Interview Pattern

Developer: "/grill-me on building a rate limiter for our public API"

Antigravity:
"Before we design this, I need to understand 4 critical constraints:
1. Algorithm: Are you looking for a Token Bucket, Leaky Bucket, or Fixed Window? 
   (Token bucket handles bursts; fixed window is simple but susceptible to boundary spikes).
2. Storage Layer: Where should rate counters live? In-memory (single server) or Redis (distributed)?
3. Header Contract: Should we return standard IETF headers (RateLimit-Limit, RateLimit-Remaining)?
4. Bypassing: How do we handle authenticated enterprise users vs unauthenticated crawlers?"

3. Why This Beats a 3-Day PRD Review

In traditional corporate workflows, these 4 questions would be caught weeks later in QA or after a production outage. With /grill-me, the entire debate happens in a 5-minute interactive dialogue.

Once you answer, Antigravity synthesizes the decisions into a bulletproof specification, guaranteeing that the code written in the next phase matches your exact architectural intent.