grill-me

Interviews users one question at a time to stress-test plans and high-criticality requirements.

7|3|Updated Sep 23, 2025
One-click install
npx skills add https://github.com/islamu-ngo/Event --skill grill-me-islamu-ngo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/grill-me
Command: npx skills add https://github.com/islamu-ngo/Event --skill grill-me-islamu-ngo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans and high-criticality tasks often start with underspecified requirements, leading to costly design mistakes discovered late. This Skill runs a structured decision-tree interview that resolves ambiguities before implementation begins. ## Core Features & Use Cases - One-Question-at-a-Time Interviews: Asks exactly one self-contained question per response, always with a recommended answer and rationale. - Repository Evidence Resolution: Inspects the codebase to answer questions from existing facts instead of asking the user unnecessarily. - High-Criticality Intake Trees: Provides focused decision branches for Tier 0 (payments/Stripe Connect), Tier 1 (auth, tenancy, migrations), and Tier 2 (PII erasure, privacy) work. - Use Case: Before implementing a Stripe Connect payout flow, activate this Skill to resolve hold expiration races, payout authority routing, and refund fee allocation through a guided interview. ## Quick Start Ask the assistant to grill you on your implementation plan for the payment payout feature before writing any code.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I stress-test a software design plan before implementation?▼

Use a decision-tree interview that asks one question at a time, each with a recommended answer and rationale. It resolves upstream decisions first, checks the repository for existing evidence, and continues until every relevant branch is resolved.

How to gather requirements for payment or Stripe Connect features?▼

For payment-critical work, the interview focuses on hold expiration versus payment finalization races, payout authority routing between organizers and instance admins, and partial refund fee allocation boundaries before any code is written.

Can the interview answer questions from the codebase instead of asking me?▼

Yes. When repository evidence can answer a question, the Skill inspects the codebase and treats the finding as resolved rather than asking the user, reducing the number of questions needed.

What topics does the high-criticality intake cover?▼

It covers three tiers: Tier 0 sovereign money flows like Stripe Connect, Tier 1 security concerns like token extraction fallback order and cross-tenant isolation, and Tier 2 privacy topics like erasure commit ordering and anti-resurrection fencing.

When should I not use a one-question-at-a-time interview workflow?▼

Avoid it for low-risk, well-specified tasks where requirements are already clear, since the sequential interview adds overhead. It is designed for underspecified plans and high-criticality work where missed decisions are expensive.