grill-with-docs is agent-read markdown (skill) from badmuriss/my-llm-kit: Grill a plan against the documented domain model, updating CONTEXT.md and ADRs inline. use_when: stress-test a plan against the project's own language and recorded decisions. do_not_use_when: there is no domain documentation, use grill-me..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
<what-to-do>
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing.
If a question can be answered by exploring the codebase, explore the codebase instead.
</what-to-do>
<supporting-info>
## Domain awareness
During codebase exploration, also look for existing documentation:
### File structure
Most repos have a single context:
```
/
├── CONTEXT.md
├── docs/
│ └── adr/
│ ├── 0001-event-sourced-orders.md
│ └── 0002-postgres-for-write-model.md
└── src/
```
If a `CONTEXT-MAP.md` exists at the root, the repo has multiple contexts. The map points to where each one lives:
```
/
├── CONTEXT-MAP.md
├── docs/
│ └── adr/ ← system-wide decisions
├── src/
│ ├── ordering/
│ │ ├── CONTEXT.md
│ │ └── docs/adr/ ← context-specific decisions
│ └── billing/
│ ├── CONTEXT.md
│ └── docs/adr/
```
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_5rkalclv6qkjtns6
GET https://markdownregistry.com/api/v1/resolve?ref=badmuriss/my-llm-kit/grill-with-docs
GET https://markdownregistry.com/api/v1/blob/a9b75b510cce48ef14e6589fdebcc43298e79959e9ebf09f9843a7ae814c6c5b
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
badmuriss/my-llm-kit · skills/agent-graph/SKILL.md · Run durable task graphs when independent work needs ownership, integration checks and recovery. Use for graph…
badmuriss/my-llm-kit · skills/computer-use/SKILL.md · Inspect and operate local browser or desktop interfaces. Prefer Jev Ultrafast for supported browser-only goals when its…
badmuriss/my-llm-kit · skills/frontend-visual-validation/SKILL.md · Verify rendered UI changes with reproducible screenshots and vision review on their supported platforms.
badmuriss/my-llm-kit · skills/grill-me/SKILL.md · Adversarial interview about a plan until you reach shared understanding. use_when: "grill me", stress-test a plan or…
badmuriss/my-llm-kit · skills/impl/SKILL.md · Implement a requested change or approved plan, verify its outcomes, and report concrete blockers. Use graph execution…
badmuriss/my-llm-kit · skills/ingest/SKILL.md · Extract content from documents when their format or layout prevents reliable direct reading. Verify reading order and…
badmuriss/my-llm-kit · skills/readme-pass/SKILL.md · Make a public repository README easier to understand and use. Apply when README structure or presentation is requested.
badmuriss/my-llm-kit · skills/remove-ai-marks/SKILL.md · Inspect and remove requested metadata or invisible marks from user-owned files. Use when provenance cleanup is…
badmuriss/my-llm-kit · skills/research/SKILL.md · Research external questions and compare evidence with source attribution. Use for research or fact-checking, not facts…
badmuriss/my-llm-kit · skills/rule-curator/SKILL.md · Audit an existing corpus of agent instructions for conflicts, duplication and unnecessary process. Use for a…
akillness/jeo-skills · .agent-skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. Use when the…
outlinedriven/odin-claude-plugin · plugins/odin-knowledge/skills/grill-with-docs/SKILL.md · Use when a repository decision needs an interview plus durable terminology and decision records. Not for remote…
vodailocz/kilo-kit-mcp · skills/productivity/grill-with-docs/SKILL.md · Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates…
rudycity/superagent · .agents/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
mambo-wang/codewiki-plus · .codebuddy/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
mambo-wang/codewiki-plus · .trae/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
ethanyoq/skill-hub · archives/user-installed-skills/grill-with-docs/1c4086b10bce8596/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
chinkan/rustfox · .agents/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
