What makes Grill With Docs notable?

1.1K downloads. Trust evidence available

How should Grill With Docs be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Grill With Docs

Full design grilling session. I interview you relentlessly about every aspect of your plan until we reach shared understanding. At the end, I generate CONTEX... Skill: Grill With Docs Owner: genortg Summary: Full design grilling session. I interview you relentlessly about every aspect of your plan until we reach shared understanding. At the end, I generate CONTEX... Tags: latest:1.0.0 Version history: v1.0.0 | 2026-06-01T12:24:54.651Z | user Initial release — design grilling session that generates CONTEXT.md and ADRs. Adapted from GSD Core by TÂCHES/open-gsd. Archive index:

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.0.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.0release · observed Jun 1, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s172yhaxa2mvn5n0h9mgjxszyd83r09e:grill-docs

Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-genortg-grill-docs/snapshot"

Documentation

CLAWHUB

7,191 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: grill-with-docs
description: Full design grilling session. I interview you relentlessly about every aspect of your plan until we reach shared understanding. At the end, I generate CONTEXT.md and ADR files from what we discussed.
author: GenorTG
attribution: Adapted from the GSD Core project by TÂCHES / open-gsd (https://github.com/open-gsd/gsd-core)
---

# Grill With Docs

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.

## Domain Awareness

During codebase exploration, 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.

## 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.

`CONTEXT.md` should be **totally devoid of implementation details.** It is a glossary and nothing else — not a spec, not a scratch pad.

### 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

_meta.json

{
  "ownerId": "kn7268msn49z4pk9k7vt791rqx82aza9",
  "slug": "grill-docs",
  "version": "1.0.0",
  "publishedAt": 1780316694651
}

skill-card.md

## Description:

Runs a design grilling session that interviews the user until shared understanding is reached, then generates CONTEXT.md and ADR files from the discussion.

This skill is ready for commercial/non-commercial use.

## Publisher:

[genortg](https://clawhub.ai/user/genortg)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and engineering teams use this skill to clarify project design language, resolve domain decisions through a guided interview, and capture the outcome as repository documentation.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Generated glossary or ADR documentation may misstate project decisions or code behavior.

Mitigation: Review generated CONTEXT.md and docs/adr files before committing or sharing them.

Risk: The skill reads project context and may update repository documentation during the session.

Mitigation: Use it only in repositories where documentation updates are intended, and inspect diffs before accepting changes.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/genortg/skills/grill-docs)
- [GSD Core attribution](https://github.com/open-gsd/gsd-core)

## Skill Output:

**Output Type(s):** [text, markdown, files, guidance]

**Output Format:** [Markdown documentation files and conversational guidance]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [May create or update CONTEXT.md and docs/adr Markdown files during the session.]

## Skill Version(s):

1.0.0 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

templates/adr.md

# ADR Template

Use this template when documenting architecture decisions during a grill-with-docs session.

```markdown
# ADR-NNNN: Title

**Status:** [proposed | accepted | deprecated | superseded]
**Date:** YYYY-MM-DD
**Deciders:** [who was involved]

## Context

[What's the situation? What problem are we solving?]

## Decision

[What did we decide? One clear paragraph.]

## Rationale

[Why this over the alternatives? List 2-3 options considered.]

## Consequences

[What does this mean for the codebase? Trade-offs, migration needs, etc.]
```

templates/context-segment.md

# Context Segment Template

A context segment documents one concept in the project's shared language. Multiple segments compose into CONTEXT.md.

```markdown
## [Concept Name]

**Definition:** One sentence explaining what this is.

**Why it matters:** [Why this concept deserves its own name.]

**Usage in code:**
- Variables, functions, types should use this name
- Related concepts: [list related terms]

**Examples:**
- Good: [correct usage]
- Bad: [misuse to avoid]
```

Github ReposUpdated 2d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.