grillpronounced /ɡrɪl/verbquestion closely and relentlessly

Grill the idea before anyone builds it.

An AI reads your Brief and your code, then puts the product questions to the Product lead and the technical ones to the Engineer, a Round at a time, until the decisions are made. Working alone? Take both seats.

You leave with

An approved Spec
Tickets in build order
A pull request

Start a Grill

Runs on your own Anthropic, OpenAI or Google Gemini key.

For you

3 waiting

Product lead

Question 2

Out-of-stock items

What should happen when an item in the original order is no longer available?

How a Grill goes

From a rough idea to Tickets someone can pick up. Each step uses the words you’ll see in the app.

Brief
Start with a sentence or a page.
Describe the feature in your own words. Attach PDFs, images or spreadsheets, and bring in issues from GitHub or Linear. Pick the repository it’s for, or grill the idea on its own.
Then choose how deep the questions go.
How deep should the Grill go?
The AI stops asking at this depth and drafts the Spec. You can wrap up sooner from the Grill at any time.
QuickUp to 2 Rounds · 5–10 QuestionsOnly the decisions that change what gets built. The rest go into the Spec as assumptions you can edit.About 10 min of answeringStandardUp to 3 Rounds · 10–20 QuestionsThe main flows and the failure cases most likely to bite. Edge cases only when the Brief raises them.About 25 min of answeringThoroughUp to 5 Rounds · 20+ QuestionsEvery branch, edge case and naming question, until nothing is left assumed.45 min or more of answering
The Round limit always holds. Question counts and times are typical, not promised.
Rounds
Each of you answers your own half.
Questions arrive in Rounds, each with up to three suggested answers and one recommended. Pick one or write your own, delegate it to the other seat, or defer it and leave it open in the Spec.
Invite the other seat by email. They can answer as a guest, no account needed.
Who’s answering the questions?
The AI asks product questions and engineering questions. Choose who answers them.
With a collaboratorThey answer their side here.They answer their side here. You can pass questions back and forth.Solo, relaying someHand off questions you can’t answer.You answer here and relay the rest as Markdown or an email draft.SoloYou take both seats.You take both seats and answer every question yourself.
Seats
Product leadScope, behavior, UX
Collaborator
EngineerArchitecture, testing
EEYouErin Engineer(you)
The Engineer approves the Spec, edits Tickets and publishes. A guest in that seat claims an account first.
Spec
Leave with a Spec you both agreed to.
When the questions run out, the AI rewrites your Brief with every decision in it. Anything deferred is listed as open, not quietly assumed.
The Engineer edits it if needed and approves it. The full Transcript of every Round stays attached.
Approving is final.
Properties
Drafted
2 min. ago
Pull request
Not opened
Read
On this page
Who it is for
Behaviour
Open decisions
Out of scope
One-click reorder
Account holders can repeat a previous purchase from their order history in one click, without rebuilding the cart by hand.
Who it is for
Signed-in account holders only. Guest orders carry no purchase history to reorder from, so the control is not shown to them.
Behaviour
A Reorder control appears both on the order history list and on the order detail page, so a customer never has to open an order to repeat it. Activating it fills the cart with the original order's line items and takes the customer to the cart — it does not place the order or charge a saved card. Checkout is unchanged.
Items that are no longer available are skipped, and the cart names each one it left out, so the rest of the order still goes through.
Prices come from the current catalog, not the original order, so promotions and price changes apply automatically. Orders already store a price snapshot per line item, so the original prices remain available if that decision is ever revisited.
Open decisions
Reorder rate limiting — whether a second reorder of the same order within a few minutes should be refused, to stop accidental duplicates. Deferred: the cart step gives the customer a chance to back out, so this is not blocking.
Out of scope
Guest reordering, subscriptions and scheduled repeat orders.
Tickets
Hand it to whoever builds it.
The AI breaks the approved Spec into Tickets and the Engineer edits them. Each is a slice you can demo on its own, in the order they unblock each other.
File them to GitHub Issues or Linear, download them as Markdown, or open the Spec as a pull request in your repository.
A signed-in account holder opens a past order and reorders it in one click. The cart fills with the order's line items at current catalog prices and they land on the cart, ready to check out as normal.
Ready to start4 checks
An order containing an item that can no longer be bought still reorders. The unavailable items are left out and the cart names each one it skipped, so the customer knows what changed before they pay.
After 013 checks
The same Reorder control appears on each row of the order history, so a customer repeating a regular order never has to open it first. It behaves exactly as it does on the detail page.
After 01, 023 checks
A customer with no past orders, or whose reorder fails partway, sees a plain explanation and a way forward rather than an empty cart or a stack trace.
After 032 checks