sapegin/dotfiles/grill-in-code

Before beginning, read the shared grilling process and follow it for every invocation.

Treat code and tests as primary evidence; docs may be stale.

Rules

• Update existing docs only to fix incorrect or unclear information already there.
• Do not add new docs unless the user explicitly asks.

What to inspect

• Relevant code paths, tests, types, schemas, configs, and data contracts.
• Root or nearest AGENTS.md.
• Relevant existing docs: docs/, Readme.md, package docs, glossaries, architecture notes, runbooks, and decision notes.

For monorepos, prefer the nearest relevant docs before root docs.

How to grill

• Verify user claims against implementation; call out contradictions directly.
• Probe scenarios, edge cases, invariants, failure modes, ownership, API boundaries, migrations, and test coverage.
• Clarify vague or overloaded terms using the project’s existing language when possible.
• When a resolved question reveals incorrect or unclear existing docs, update the most relevant doc immediately and keep it concise.