skills.rest
ralvarezdev
ralvarezdevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

grill-with-docs

Stress-test plans against CONTEXT.md and ADRs during design reviews.

3|Updated Feb 26, 2026
Search Tags:#documentation#adr#decision-making#design-review#stakeholder-interview#context.md#grill-with-docs
One-click install
npx skills add https://github.com/ralvarezdev/ralvaskills --skill grill-with-docs-ralvarezdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-with-docs
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/workflows/grill-with-docs
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill grill-with-docs-ralvarezdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to stress-test plans and designs against existing domain documentation (CONTEXT.md, ADRs) to surface gaps, align stakeholders, and crystallize decisions before implementation.

Core Features & Use Cases

  • Interactive grilling: interview stakeholders to surface assumptions, dependencies, and edge cases in a plan.
  • Inline documentation updates: reflect decisions and resolutions directly into CONTEXT.md and ADRs as they crystallize.
  • Codebase-aware exploration: dive into the repository when needed to verify choices against the codebase.
  • Decision traceability: maintain an auditable trail of questions, answers, and resulting decisions.

Quick Start

Start a grilling session by guiding the user through a plan one decision at a time and update docs inline as decisions crystallize.

Frequently Asked Questions about grill-with-docs

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

FAQPage Schema
How do I validate a design plan against existing ADRs and CONTEXT.md files?▼

To validate a design plan against ADRs and CONTEXT.md, you can run an interactive grilling session that interviews stakeholders step-by-step to surface assumptions and verify choices against the codebase.

What is the best way to stress-test technical decisions before implementation?▼

Stress-testing technical decisions involves interactively questioning a plan to expose edge cases, align stakeholders, and crystallize resolutions directly into domain documentation like CONTEXT.md and ADRs.

How do I ensure decision traceability during a design review?▼

Decision traceability during a design review is ensured by maintaining an auditable trail of interview questions, answers, and resulting decisions while updating CONTEXT.md and ADRs inline as resolutions form.

Can I update CONTEXT.md and ADRs in place while interviewing stakeholders?▼

Yes, you can update CONTEXT.md and ADRs in place while interviewing stakeholders, reflecting decisions and resolutions directly into the domain documentation as they crystallize during the session.

Do I need existing CONTEXT.md files to start grilling a design plan?▼

You need an existing plan to validate and ideally domain documentation like CONTEXT.md and ADRs to check against, though the session can also explore the codebase directly to answer questions when needed.

How does codebase exploration work during stakeholder interviews?▼

Codebase exploration during stakeholder interviews allows the session to dive into the repository on demand to verify technical choices, surface dependencies, and answer questions against the actual code.

Related Skills

Explore More Content & Communication Skills→
ogprotegeogprotege

repo-doc-auditor

Audit repository documentation against code and recent changes.

Community
Advanced
cslsoftwarescslsoftwares

governance-spec-reviewer

Audit SPEC and PRD for security, database edge cases, and rollback gaps.

Community
Advanced
vessuxvessux
1

grill-with-docs

Challenge project plans to align domain language and update CONTEXT.md and ADRs.

Community
Advanced
cyalcalacyalcala
1

documentation-and-adrs

Record architectural decisions with ADR templates and inline context.

Community
Intermediate