Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file 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/
```
…
The line at the top of this page pins the label git:20260922.7ea4a67, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_rp33iwz36nga6che
GET https://markdownregistry.com/api/v1/resolve?ref=maomaochong-ai/open-astravia/grill-with-docs
GET https://markdownregistry.com/api/v1/blob/3e35025119ba03efe7983dfdec3c8b96918142e3978512f3c2bf66d428310c7e
Your AI assistant 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.
maomaochong-ai/open-astravia · .agents/skills/compose-component-design/SKILL.md · Use when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout…
maomaochong-ai/open-astravia · .agents/skills/compose-state-and-effects/SKILL.md · Use when writing or reviewing Jetpack Compose state ownership, remember state, state hoisting, screen state holders…
maomaochong-ai/open-astravia · .agents/skills/design-taste-frontend/SKILL.md · Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right…
maomaochong-ai/open-astravia · .agents/skills/expo-overview/SKILL.md · Framework (OSS). Entry point and router for every Expo or EAS task. Load this skill first — before writing code and…
maomaochong-ai/open-astravia · .agents/skills/expo-project-structure/SKILL.md · Framework (OSS). Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo…
maomaochong-ai/open-astravia · .agents/skills/expo-router/SKILL.md · Framework (OSS). Navigation and routing for Expo Router. Covers file-based routes, groups and dynamic routes, folder…
maomaochong-ai/open-astravia · .agents/skills/find-skills/SKILL.md · Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is…
maomaochong-ai/open-astravia · .agents/skills/frontend-design/SKILL.md · Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with…
maomaochong-ai/open-astravia · .agents/skills/grill-me/SKILL.md · Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of…
maomaochong-ai/open-astravia · .agents/skills/handoff/SKILL.md · Compact the current conversation into a handoff document for another agent to pick up.
zhongkaifu/tensorsharp · TensorAgent/skills/grill-with-docs/SKILL.md · Interview a plan, record agreed terms and decisions, and return saved document links before questions. Tested with…
kunolu/640-skills · sbtd-workflow-onboard/assets/external-skills/stable/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.
asymmetric-al/core · .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.
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.
mart337i/odoo-skills · skills/grill-with-docs/SKILL.md · Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates…
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…
