메뉴
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when executing implementation plans with independent tasks in the current session
Convert Claude's persisted memory into a structured high-level outline and save it to the project Obsidian vault. Use to archive and organize accumulated session knowledge as a navigable vault note.
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
Set up and operate an LLM-maintained personal knowledge base wiki. Use when building a persistent, compounding knowledge base from source documents -- articles, papers, notes, transcripts, or any source material.
| name | grill-me |
| version | 2.0 |
| category | productivity |
| execution_speed | fast |
| token_efficiency | high |
| triggers | ["grill me","stress-test plan","stress test design","interview relentlessly"] |
| cache_key | grill-me-2.0 |
| dependencies | [] |
| description | Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me". |
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time. Stop and wait for the user to respond before asking the next question.
If a question can be answered by exploring the codebase, explore the codebase instead.
