mine.grill

Interrogate ideas across product, design, engineering, scope, and adversarial lenses.

8|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Olatisunkanmi/claudefiles --skill mine-grill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mine.grill
Source: https://github.com/Olatisunkanmi/claudefiles/tree/main/skills/mine.grill
Command: npx skills add https://github.com/Olatisunkanmi/claudefiles --skill mine-grill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and builders surface overlooked assumptions, risks, and gaps in raw ideas before committing to design or engineering work, reducing wasted effort and costly pivots.

Core Features & Use Cases

  • Targeted interrogation across lenses: Asks focused, adaptive questions from product, design, engineering, scope, and adversarial perspectives to reveal blind spots.
  • Context-aware questioning: Checks the codebase or provided documents to skip answered questions and ground the conversation in existing patterns.
  • Actionable output: Produces a structured brief suitable for handoff to specification or challenge workflows, and offers next-step options (challenge, specify, build).
  • Use Case: A product manager uses this Skill when evaluating a proposed feature to identify hidden assumptions, narrow scope, and create a concise brief for engineers and designers.

Quick Start

Grill my idea: "A subscription meal-planning app that auto-generates weekly menus from pantry inventory and dietary preferences."

Frequently Asked Questions about mine.grill

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

FAQPage Schema
How do I surface hidden assumptions during product ideation before engineering starts?

Conduct risk assessment on proposed features by asking focused, adaptive questions from product, design, engineering, scope, and adversarial perspectives. This context-aware interrogation checks existing documents to skip answered questions, generating targeted questions and a structured brief for handoff.

What is the best way to evaluate a proposed feature and narrow scope for engineers?

The best way to evaluate a proposed feature and narrow scope is through targeted interrogation that identifies hidden assumptions and risks. By probing the idea from multiple perspectives, you produce a concise, structured feature brief consumable by downstream specify and build workflows.

How do I generate a structured feature brief from a raw idea?

Generate a structured feature brief from a raw idea by interrogating it with context-aware, multi-angle questioning. This process skips already answered questions by checking provided documents, yielding a targeted brief with actionable next-step options like challenge, specify, or build.

Does multi-angle questioning work for pre-pipeline exploration of feature planning?

Multi-angle questioning works effectively for pre-pipeline exploration and feature planning by applying adversarial lenses to surface unanswered questions. It grounds the conversation in existing patterns and produces a structured brief consumable by downstream specify and build workflows.

When should I not use adversarial questioning for product ideation?

You should not use adversarial questioning for product ideation when your idea is already fully specified and ready for build, as this process targets pre-pipeline exploration. It is designed to interrogate raw ideas to surface assumptions and risks before committing to design or engineering work.