grill

Conduct iterative questioning to refine plans and resolve decision dependencies.

Updated Mar 30, 2026

Search Tags:#project planning #design review #decision-making #stress-test #glossary maintenance

Ready to run

npx skills add https://github.com/weside-ai/claude-code-plugin --skill grill-weside-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: grill
Source: https://github.com/weside-ai/claude-code-plugin/tree/main/we/skills/grill
Command: npx skills add https://github.com/weside-ai/claude-code-plugin --skill grill-weside-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you thoroughly examine and refine your plans or designs by conducting a relentless, one-question-at-a-time interview, ensuring every decision is fully explored and understood.

Core Features & Use Cases

Relentless Questioning: Engage in a detailed, iterative questioning process to uncover all aspects of a plan or design.
Decision Tree Resolution: Walk through each branch of the decision tree, resolving dependencies between decisions.
Glossary and ADRs: Offers guidance on maintaining a project glossary and recording Architectural Decision Records (ADRs) when necessary.
Use Case: Use the /we:grill command to initiate a stress-test on a project plan, ensuring all decisions are well thought out and documented.

Quick Start

Start a grill session by typing /we:grill and respond to the questions posed by the AI to refine your plan or design.

Frequently Asked Questions about grill

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

FAQPage Schema

How do I stress-test a project plan to ensure all decisions are explored?▼

To stress-test a project plan, you can use an iterative questioning process that examines each decision point one question at a time. This method ensures every dependency is resolved and all design choices are fully understood before execution.

What is an Architectural Decision Record and when do I need it?▼

An Architectural Decision Record (ADR) documents significant design choices during a project. You need to maintain ADRs when resolving complex decision trees to ensure that the rationale behind each architectural choice is recorded for future reference.

How do I resolve dependencies in a design review decision tree?▼

Resolving dependencies in a design review decision tree involves walking through each branch iteratively. By systematically addressing one question at a time, you can untangle interrelated decisions and ensure no dependency is left unresolved.

Can I maintain a project glossary while conducting a design review?▼

Yes, you can maintain a project glossary during a design review. As you stress-test your plan through relentless questioning, you can simultaneously define and record project terminology to ensure consistent communication across the team.

What is the best way to document decision-making for complex project planning?▼

The best way to document decision-making for project planning is through an iterative questioning process that records Architectural Decision Records (ADRs). This structured approach guarantees that every design choice and dependency resolution is thoroughly explored and officially logged.