Documents & Data · IN-DEPTH PROFILE

grill-with-docs

Grill With Docs combines deep design questioning with domain-model documentation.

Best for

Teams maintaining domain-heavy codebases

What you get

Clarify domain language + Test scenarios

Main limitation

It assumes the repository has, or is willing to adopt, domain glossaries and decision records.

First risk

Documentation churn. Over-eager updates can turn exploratory language into policy. Review every glossary or ADR change before committing it.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-08-20

Pinned revision · 885e2ca4

Open pinned commit
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

30-SECOND BRIEF

What it does—and when it fits

Grill With Docs combines deep design questioning with domain-model documentation. It grounds the conversation in code, CONTEXT.md glossaries, and ADRs; challenges fuzzy terminology; tests decisions against scenarios; and updates durable documentation only when the discussion produces a real decision.

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project scope.claude/skills/grill-with-docs/
Personal scope~/.claude/skills/grill-with-docs/

Use project scope for team sharing and personal scope across repositories. The installer defaults to project scope; add -g for personal scope.

Install command (project scope)npx skills add mattpocock/skills --skill grill-with-docs --agent claude-code
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence

TYPICAL WORKFLOW

A practical workflow

01

Clarify domain language

Resolve conflicting terms and keep the shared glossary precise.

02

Test scenarios

Apply design choices to concrete cases to reveal weak boundaries.

03

Capture decisions

Update CONTEXT.md or ADRs when the outcome warrants durable documentation.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to mattpocock/skills.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. It assumes the repository has, or is willing to adopt, domain glossaries and decision records.
  2. The workflow invokes related grilling and domain-modeling Skills, so results depend on those instructions too.

BEST FIT

Who it is for

Teams maintaining domain-heavy codebases

Architects who want decisions tied to durable context

BEFORE YOU USE IT

Risks to review before use

Medium

Documentation churn

Over-eager updates can turn exploratory language into policy. Review every glossary or ADR change before committing it.

Medium

Upstream instruction drift

Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

domain-modelingadrdesign-review

Manually expanded from the current upstream SKILL.md and linked source at mattpocock/skills, checked 2026-08-19. This is an original summary, not an execution result or security certification.