ds-grill-me

When invoked, stress-test every aspect of the plan. Walk down each branch of the decision tree, resolving dependencies between decisions one at a time.

Before the first question, look for RETRO.md (current directory, then repo root). Its rule bullets are priors distilled from past releases by /ds-retro: cite a rule when it bears on the question at hand — the user can override it; never let it steer silently.

Arguments

--record [path] — append each resolved decision worth keeping to GRILL.md in the current directory, or to path if you name one, as the interview proceeds. Record the ones that are hard to reverse, surprising without context, or the product of a real trade-off — skip the trivial and the self-evident. One entry per decision: the question, the chosen answer, and a one-line rationale. Plain Markdown, no fixed schema. Without the flag, keep decisions in the conversation only.

Write it where the user works, never into .project/ — that directory holds session state with one writer per file, and this is a work product: something to feed into /ds-spec, a PR description, or the next person. On a project that uses .project/, /ds-project-checkpoint reads the session and distils whatever now constrains future work into one-line # settled entries. The two are independent — the artifact keeps the full reasoning, # settled keeps only what forbids something.

Process

• Ask questions one at a time. Wait for the answer before the next question.
• For every question, provide your recommended answer.
• If a question can be answered by exploring the codebase, explore the codebase instead of asking.
• When the user asserts how something works, check it against the code — if they disagree, surface the conflict: "your code cancels the whole Order, but you said partial cancellation is possible — which is right?"
• Stress-test boundaries with invented edge-case scenarios that force the user to be precise about where one concept ends and another begins.
• Pin down vague or overloaded terms — "you're saying 'account' — the Customer or the User? those are different things."
• Continue until every branch of the decision tree is resolved and you and the user share the same understanding.

Output

End when no unresolved decision branches remain. Summarize the resolved plan. If --record was passed, also report the path it was written to.