grill-me

Guide users through a decision tree to resolve requirements and document decisions.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/apokamo/kaji-starter-python --skill grill-me-apokamo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/apokamo/kaji-starter-python/tree/main/.claude/skills/grill-me
Command: npx skills add https://github.com/apokamo/kaji-starter-python --skill grill-me-apokamo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents costly rework and ambiguity in complex development tasks by forcing a structured, interactive interview process before any code is written.

Core Features & Use Cases

  • Decision Tree Resolution: Systematically resolves complex branching logic in requirements one step at a time.
  • Provenance Tracking: Records all human-made decisions and AI assumptions directly into the issue body for future auditability.
  • Use Case: Use this when tackling a high-impact feature or architectural change to ensure all stakeholders are aligned on one-way door decisions before the implementation workflow begins.

Quick Start

Invoke the grill-me skill by running the command followed by the target issue ID to begin the interactive requirement interview.

Frequently Asked Questions about grill-me

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

FAQPage Schema
How do I document decision provenance for complex software development issues before implementation?

Document decision provenance by running an interactive interview that records human choices and AI assumptions directly into the issue body. This ensures all architectural decisions are auditable before workflow execution begins.

What is the best way to resolve ambiguities in high-stakes architectural requirements?

Resolving ambiguities in high-stakes requirements requires guiding stakeholders through a structured decision tree. This interactive process systematically addresses branching logic one step at a time to force alignment.

How do I front-load critical decisions for one-way door software changes?

Front-load critical decisions by initiating an interactive requirement gathering process tied to an active issue ID. This forces human participation to validate functional choices before any code is written.

Do I need an active issue ID to start interactive requirement gathering?

An active issue ID is required to start the interactive requirement gathering process. The system uses this identifier to anchor the decision tree resolution and append provenance data to the correct issue body.

When should I use an interactive interview process for issue tracking?

Use an interactive interview process for issue tracking when tackling a high-impact feature or architectural change. It prevents costly rework by forcing stakeholders to validate critical choices before the implementation workflow starts.

Why does requirement gathering require human participation for decision tree resolution?

Requirement gathering requires human participation to validate critical architectural and functional choices. The system operates by guiding users through the decision tree, but humans must actively resolve ambiguities and confirm one-way door decisions.