grill-with-docs

Challenge project plans against existing domain models and documented decisions.

7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ste-bah/archon-cli --skill grill-with-docs-ste-bah
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/ste-bah/archon-cli/tree/main/assets/skills/grill-with-docs
Command: npx skills add https://github.com/ste-bah/archon-cli --skill grill-with-docs-ste-bah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you rigorously test a proposed plan against the project's existing language and decisions so you can catch ambiguity, hidden dependencies, and terminology drift before implementation.

Core Features & Use Cases

  • Relentless questioning: It walks through a plan one decision at a time and keeps asking until the shape of the solution is clear.
  • Domain-language enforcement: It cross-checks your terms against existing context documentation and flags mismatches immediately.
  • Living documentation: It updates context notes and ADRs inline as decisions crystallise, keeping the design record aligned with the conversation.

Quick Start

Use the grill-with-docs skill to interview me one question at a time about my plan, check the repository for existing terminology and decisions, and update the relevant documentation as we resolve them.

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 domain model?

To stress-test a project plan against your domain model, the Skill interviews you one question at a time, inspecting your codebase and glossary to flag terminology drift before implementation begins.

What is the best way to align architecture decisions with my project's glossary?

Aligning architecture decisions with your glossary requires cross-checking proposed terms against existing context documentation. This Skill enforces domain language by flagging mismatches immediately during the design discussion.

Can I automatically update ADR files while reviewing a proposed architecture?

Yes, you can update ADR files inline as decisions crystallize. The Skill keeps your living documentation aligned with the conversation by selectively writing to context notes and ADR files.

How do I catch hidden dependencies and terminology drift before coding?

Catching hidden dependencies and terminology drift before coding requires relentless questioning of your plan. The Skill walks through each decision sequentially, comparing your terms against documented decisions in the codebase.

Do I need existing context documentation and ADRs to use this architecture review process?

Existing context documentation and ADRs are necessary to compare against your proposed plan. The Skill requires codebase inspection and glossary comparison to effectively challenge your decisions and resolve ambiguities.