ad-grill

Clarify fuzzy asks via one-question-at-a-time interviews and route to upstream skills.

728|16|Updated Mar 9, 2026

Search Tags:#workflow #documentation #context #adr #design-decision #grilling #fuzzy-ask

Ready to run

npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-grill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ad-grill
Source: https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime/tree/main/.agents/skills/ad-grill
Command: npx skills add https://github.com/alexandremendoncaalvaro/CorridorKey-Runtime --skill ad-grill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, interview-style grilling workflow that converts fuzzy asks into concrete, design-ready decisions by sequentially surfacing terms and routing to the appropriate upstream skills before research or implementation.

Core Features & Use Cases

One-question-at-a-time grilling to clarify vague requirements and align on terminology.
Automatic routing to upstream workflows (ad-ground, ad-tdg, ad-spike, ad-diagnose) as the question clarifies scope.
Context and ADR capture to document terms and decisions in CONTEXT.md and ADRs.

Quick Start

Provide the first fuzzy ask and trigger the ad-grill flow to begin a one-question-at-a-time clarification session.

Frequently Asked Questions about ad-grill

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

FAQPage Schema

How do I clarify vague project requirements before starting research or implementation?▼

A fuzzy ask is a vague, multi-decision request spanning codebases or projects. The grilling workflow processes fuzzy asks by sequentially clarifying scope and terminology through targeted, one-question-at-a-time interviews before any development begins.

How do I document design decisions and track context during a requirements interview?▼

You document design decisions and track context by capturing essential terms inline and routing qualified decisions to CONTEXT.md and ADRs, ensuring architectural choices are recorded when warranted throughout the grilling session.

What is the best way to handle multiple design decisions across a codebase simultaneously?▼

Handling multiple design decisions across a codebase involves sequentially grilling each fuzzy ask one question at a time, qualifying the scope, and routing to upstream workflows like ad-ground, ad-tdg, ad-spike, or ad-diagnose as decisions mature.

Does the grilling workflow automatically route decisions to upstream skills?▼

Yes, the grilling workflow automatically routes to upstream skills such as ad-ground, ad-tdg, ad-spike, and ad-diagnose as decisions qualify, ensuring each design choice triggers the appropriate downstream research or implementation process.

When should I use an ADR gate in a design decision workflow?▼

You should use an ADR gate when a grilling session surfaces design decisions that warrant formal architectural documentation, ensuring qualified terms and choices are captured in CONTEXT.md and ADRs before proceeding to research or implementation.