Skip to content

MVPavan/via / .claude/skills/grilling

grilling

Verified

Use when the user explicitly requests a grilling interview to resolve or challenge material decisions. For a written critique, review the artifact directly.

FileKindSize
SKILL.mdskill md1.7 KB
agents/openai.yamlconfig155 B
---
name: grilling
description: Use when the user explicitly requests a grilling interview to resolve or challenge material decisions. For a written critique, review the artifact directly.
---

# Grilling

Interview the user about a plan, decision or idea when they explicitly request
that interaction. A request for written critique does not itself request an interview.

Map material decisions and their prerequisites. Ask a manageable batch of
independent questions whose prerequisites are settled; defer dependent questions
until their answers can use the earlier decisions. Include a recommendation and
its assumptions where useful, allowing the user to disagree.

Look up available facts yourself. Ordinary local or documentation lookups stay
inline; delegate only bounded work that benefits from it. Decisions requiring a
live participant remain pending; do not answer on that participant's behalf.

Recompute the unresolved choices after each answer. Stop when the decisions
needed for the requested outcome are settled, explicitly deferred or identified
as blocked. Do not exhaust every imaginable branch. Summarize material agreements
and remaining uncertainty; carry authorization forward for any next step already
requested, without treating the interview itself as implementation authority.

If the necessary respondent is absent, prepare a questionnaire for their role and
knowledge gap. Ask the present user only for missing recipient context and desired
outcome; do not force two exchanges when these were supplied. Drafting a
questionnaire does not authorize sending it.

Documentation is optional. When requested, use domain-modeling for settled terms
and qualifying ADRs; a repository's existence alone does not authorize these writes.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall