stacks-grilling

Interviews users in structured rounds to stress-test plans and design decisions before coding.

625|19|Updated Apr 26, 2022
One-click install
npx skills add https://github.com/stacksjs/stacks --skill stacks-grilling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stacks-grilling
Source: https://github.com/stacksjs/stacks/tree/main/storage/framework/defaults/ai/skills/stacks-grilling
Command: npx skills add https://github.com/stacksjs/stacks --skill stacks-grilling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans, designs, and architectural decisions often contain hidden assumptions that only surface after code is written. This Skill stress-tests thinking through a structured interview process, mapping every decision as a design tree so nothing is silently assumed before implementation begins.

Core Features & Use Cases

  • Round-based frontier interviewing: Maps work as a design tree and asks every currently-unblocked decision in numbered rounds, each with a recommended answer.
  • Fact gathering from the codebase: Reads config files, models, routes, CLI help, and CONTEXT.md in Stacks projects so users only answer decisions, never lookups.
  • Shared interview primitive: Used directly or embedded by other workflows like plan review, product ideation, and redesign sessions.
  • Use Case: Before building a new feature, run a grilling session to settle questions about data models, API surface, and configuration drivers, then hand the settled understanding to a planning step.

Quick Start

Ask the assistant to grill you on your feature plan or design decision before any code is written.

Frequently Asked Questions about stacks-grilling

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

FAQPage Schema
How do I stress-test a design decision before writing code?

Run a grilling session that maps your work as a design tree and interviews you in rounds. Each round asks every decision whose prerequisites are settled, with recommended answers, until no assumptions remain.

What is the round-and-frontier interview method?

The frontier is the set of decisions whose prerequisites are already settled and can be asked now. Each round asks the whole frontier at once, answers push the frontier outward, and dependent questions wait for later rounds.

Does the grilling skill write any code during the session?

No, it never produces code during an interview. If a question needs a runnable answer, it defers to a prototyping step and brings the result back into the conversation.

Can this interview approach work with Stacks framework projects?

Yes, it reads Stacks project files directly, including config/*.ts, app/Models, routes, buddy CLI help, and CONTEXT.md, so factual questions are answered from the codebase rather than asked of the user.

When should I use a structured interview instead of planning directly?

Use it when a plan or design contains branching decisions that depend on each other, or when you want your thinking challenged. Direct planning works only after the decision tree is fully settled.