grill-me

Identify unresolved assumptions and design risks in software plans.

88|15|Updated May 25, 2026
One-click install
npx skills add https://github.com/open-octo/octo-agent --skill grill-me-open-octo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grill-me
Source: https://github.com/open-octo/octo-agent/tree/main/internal/skills/defaults/grill-me
Command: npx skills add https://github.com/open-octo/octo-agent --skill grill-me-open-octo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill exposes unresolved assumptions, hidden trade-offs, and overlooked risks in a plan or design before implementation begins, helping teams reach shared understanding with fewer costly changes later.

Core Features & Use Cases

  • Structured Plan Interviews: Walk through the decision tree one branch at a time using focused questions.
  • Codebase-Grounded Analysis: Explore relevant services, data models, APIs, messaging, caching, and configuration before asking questions.
  • Decision Coverage Checks: Verify that architecture, data models, APIs, messaging, caching, configuration, rollout, and safety concerns have been addressed.
  • Use Case: Use it to pressure-test a new feature design, clarify implementation choices, and produce a resolved decision summary for a technical design document.

Quick Start

Ask the grill-me skill to pressure-test your plan for adding a new feature and ask questions one at a time until every important decision is resolved.

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 technical design before implementation?

To stress-test a technical design, conduct one-question-at-a-time interviews to expose unresolved assumptions, analyze codebase architecture and data models, and perform final coverage checks across APIs, messaging, caching, and rollout safety.

What is the best way to identify hidden trade-offs in a software architecture plan?

Identify hidden trade-offs in an architecture plan by applying codebase-grounded analysis and structured trade-off evaluations during one-question-at-a-time interviews, exposing design risks before implementation begins.

How do I review software architecture decisions using codebase exploration?

Review architecture decisions by exploring relevant repository services, data models, APIs, and configuration to ground the analysis, then resolving implementation choices through focused one-question-at-a-time interviews.

Can I use a plan review to clarify requirements for a new feature design?

Yes, use plan review to clarify requirements for a new feature design by walking the decision tree one branch at a time, verifying that architecture, data models, APIs, and rollout safety concerns are fully addressed.

What are the limitations of design critique in feature planning?

Design critique in feature planning requires active codebase exploration and one-question-at-a-time interviews, meaning it cannot effectively evaluate designs in isolation without relevant repository context for grounding trade-off analysis.