---
id: gh-grill-with-docs
name: "grill-with-docs"
url: https://skills.yangsir.net/skill/gh-grill-with-docs
author: mattpocock
domain: ai-software-architecture-engineering
tags: ["architecture", "documentation", "planning", "review", "terminology"]
install_count: 138100
rating: 4.80 (120 reviews)
github: https://github.com/mattpocock/skills/tree/main/skills/engineering/grill-with-docs
---

# grill-with-docs

> 此技能通过严格的“拷问”会话，将您的计划与现有领域模型进行对比，明确术语定义，并随着决策的明确，实时更新 CONTEXT.md 和 ADRs 等文档。它旨在帮助用户针对项目的语言和已记录的决策，对计划进行压力测试，确保架构一致性与规范性。

**Stats**: 138,100 installs · 4.8/5 (120 reviews)

## Before / After 对比

### 决策返工率

**Before**:

缺乏严格的计划审查和术语统一，导致项目决策频繁返工，耗费大量时间和资源，延误项目进度。

**After**:

通过严谨的“拷问”会话，确保计划与领域模型一致，决策返工率显著降低，项目推进更顺畅高效。

| Metric | Before | After | Change |
|---|---|---|---|
| 决策返工率 | 30% | 5% | -83% |

### 架构评审时长

**Before**:

架构评审过程冗长且效率低下，因术语模糊和文档缺失导致反复讨论，难以达成共识，拖慢开发周期。

**After**:

AI辅助的“拷问”会话能快速识别并解决计划中的不一致和模糊点，将架构评审时长缩短，加速决策。

| Metric | Before | After | Change |
|---|---|---|---|
| 架构评审时长 | 240分钟 | 60分钟 | -75% |

## Readme

<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/
```

Create files lazily — only when you have something to write. If no `CONTEXT.md` exists, create one when the first term is resolved. If no `docs/adr/` exists, create it when the first ADR is needed.

## During the session

### Challenge against the glossary

When the user uses a term that conflicts with the existing language in `CONTEXT.md`, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"

### Sharpen fuzzy language

When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."

### Discuss concrete scenarios

When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.

### Cross-reference with code

When the user states how something works, check whether the code agrees. If you find a contradiction, surface it: "Your code cancels entire Orders, but you just said partial cancellation is possible — which is right?"

### Update CONTEXT.md inline

When a term is resolved, update `CONTEXT.md` right there. Don't batch these up — capture them as they happen. Use the format in [CONTEXT-FORMAT.md](./CONTEXT-FORMAT.md).

`CONTEXT.md` should be totally devoid of implementation details. Do not treat `CONTEXT.md` as a spec, a scratch pad, or a repository for implementation decisions. It is a glossary and nothing else.

### Offer ADRs sparingly

Only offer to create an ADR when all three are true:

1. **Hard to reverse** — the cost of changing your mind later is meaningful
2. **Surprising without context** — a future reader will wonder "why did they do it this way?"
3. **The result of a real trade-off** — there were genuine alternatives and you picked one for specific reasons

If any of the three is missing, skip the ADR. Use the format in [ADR-FORMAT.md](./ADR-FORMAT.md).

</supporting-info>


---
*Source: https://skills.yangsir.net/skill/gh-grill-with-docs*
*Markdown mirror: https://skills.yangsir.net/api/skill/gh-grill-with-docs/markdown*