grill-with-docs

Interrogate project plans against domain models and documented decisions.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/darkmatter/skills --skill grill-with-docs-darkmatter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/darkmatter/skills/tree/main/skills/grill-with-docs
Command: npx skills add https://github.com/darkmatter/skills --skill grill-with-docs-darkmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you stress-test a plan against the existing domain model so you can catch unclear terms, hidden assumptions, and missing decisions before they turn into rework.

Core Features & Use Cases

  • Relentless clarification: Interviews you one question at a time, with a recommended answer for each step, until the plan is fully understood.
  • Codebase-aware analysis: Checks the repository directly when a question can be answered from existing code or documentation.
  • Living documentation updates: Updates CONTEXT.md as terms are resolved and suggests ADRs when a decision is hard to reverse and worth preserving.
  • Use case: Ideal for design reviews, architecture discussions, and language cleanup when a project needs its glossary and decisions aligned with implementation.

Quick Start

Use the grill-with-docs skill to challenge my plan against the repository’s language, ask me one question at a time, and update the relevant documentation as we go.

Frequently Asked Questions about grill-with-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a project plan against my existing architecture and domain model?▼

Architecture documentation stress-testing works by interrogating your plan one question at a time against the existing codebase and domain model to identify unclear terms and hidden assumptions before implementation begins.

What is the best way to capture architectural decisions and update a project glossary during a design review?▼

Updating a project glossary and capturing decisions during design reviews involves resolving terminology through codebase exploration, writing results to a living CONTEXT.md file, and creating ADRs for durable trade-offs discovered during the interview process.

How does codebase-aware documentation analysis work when aligning project terminology?▼

Codebase-aware terminology alignment works by querying the repository directly to answer questions from existing code and documentation, then conducting a one-question-at-a-time interview with recommended answers until the domain model is fully understood.

Can I use inline CONTEXT.md updates and selective ADR creation for any software engineering project?▼

Yes, inline CONTEXT.md updates and selective ADR creation suit any software engineering project requiring design reviews and terminology alignment, provided the repository needs its glossary and architectural decisions documented.

When should I write an ADR versus just updating the project glossary?▼

Write an ADR when a decision involves a durable, hard-to-reverse trade-off worth preserving, whereas routine terminology alignment and resolved definitions are handled through inline updates to the CONTEXT.md glossary.