grill-with-docs
Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and decisions crystallise. Use when user wants to stress-test a plan against documented domain language, or mentions "grill with docs".
- License 许可
- MIT
- 最近更新
- 2026-08-07
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- grill-with-docs
- license
- MIT
- metadata
- { "voice": "Matt Pocock — relentless, one-at-a-time, codebase-and-docs-first, ADRs only when 3 criteria are met", "version": "1.0.0", "derived_from": "https://github.com/mattpocock/skills/tree/main/skills/engineering/grill-with-docs", "original_author": "Matt Pocock (@mattpocock)", "original_license": "MIT" }
- description
- Docs-anchored grilling session — challenges a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), and updates those files inline as terminology and decisions crystallise. Use when user wants to stress-test a plan against documented domain language, or mentions "grill with docs".
02 资源文件 8
- 参考文档ADR-FORMAT.md2.9 KB
- 参考文档CONTEXT-FORMAT.md3.3 KB
- 参考文档references/adr_practice.md8.5 KB
- 参考文档references/context_md_as_artifact.md9.2 KB
- 参考文档references/ubiquitous_language.md6.7 KB
- 脚本scripts/adr_scanner.py9.4 KB
- 脚本scripts/context_md_linter.py9.7 KB
- 脚本scripts/glossary_code_consistency.py10.1 KB
03 SKILL.md 正文
Grill with Docs
Derived from Matt Pocock's grill-with-docs (MIT, © 2026 Matt Pocock). Matt's interview discipline + docs-anchored grilling rules preserved verbatim under MIT. Additions in this repo: 3 stdlib validators (CONTEXT.md linter, ADR scanner, glossary↔code consistency check), 3 in-depth references each citing 7+ authoritative sources,
cs-grill-with-docsagent,/cs:grill-with-docscommand. See Wrapper additions below.
<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.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:
- Hard to reverse — the cost of changing your mind later is meaningful
- Surprising without context — a future reader will wonder "why did they do it this way?"
- 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.
</supporting-info>
Wrapper Additions
The additions below are not part of Matt's upstream skill. They operationalize the upstream's rules into deterministic, stdlib-only validators that pair naturally with the interview loop.
Workflow (with wrapper tools)
-
Pre-flight (before the first question):
- Run
scripts/context_md_linter.py CONTEXT.mdif aCONTEXT.mdexists — confirms the glossary is well-formed before grilling against it. - Run
scripts/adr_scanner.py docs/adr/ifdocs/adr/exists — surfaces numbering gaps, malformed ADRs, status-frontmatter inconsistencies. - Run
scripts/glossary_code_consistency.py --context CONTEXT.md --code src/— flags defined-but-unused terms (dead glossary) and code-only common nouns that may need definitions. Use these flags as opening grill questions.
- Run
-
During the session (Matt's rules apply):
- One question per turn, walking depth-first.
- When a term is sharpened: edit
CONTEXT.mdimmediately; re-runcontext_md_linter.pyif the edit is structural. - When an ADR is warranted: write it under
docs/adr/; re-runadr_scanner.pyto confirm numbering.
-
Closing:
- Final
glossary_code_consistency.pyrun to confirm no new orphan terms were introduced. - Summarize: terms added/refined, ADRs written, scenarios discussed, open items.
- Final
Tools (stdlib-only)
| Tool | One-line role |
|---|---|
scripts/context_md_linter.py |
Validate CONTEXT.md against the CONTEXT-FORMAT.md structure. PASS/WARN/FAIL per rule. |
scripts/adr_scanner.py |
Walk docs/adr/, check NNNN-slug.md pattern, numbering integrity, body completeness. |
scripts/glossary_code_consistency.py |
Cross-reference bold terms in CONTEXT.md against codebase usage. Flag dead glossary + code-only common nouns. |
References (citations behind each rule)
references/ubiquitous_language.md— why a glossary belongs in source control (Evans, Vernon, Khononov, Wlaschin, Brandolini, Avram & Marinescu, Fowler)references/adr_practice.md— when an ADR earns its keep (Nygard, Tyree & Akerman, Zimmermann Y-statements, MADR, ThoughtWorks Radar, adr-tools, Backstage)references/context_md_as_artifact.md— CONTEXT.md as living artifact (Khononov on language drift, Kernighan on naming, BoundedContext bliki, Confluent on data contracts, Brandolini on EventStorming glossary)
Companion
- Agent:
cs-grill-with-docs(see../../agents/cs-grill-with-docs.md) - Command:
/cs:grill-with-docs(see../../commands/cs-grill-with-docs.md)
Version: 1.0.0 Derived: Matt Pocock's grill-with-docs (MIT) + this repo's wrapper
04 同仓库更多 Skills
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
stop-slop
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.
ogilvy-copywriting
Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.