A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
npx skills add https://github.com/brilliantrough/agent-skills --skill grill-with-docs按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
Call the Skill tool twice, for "grilling" and "domain-modeling".
matpocockA relentless interview to sharpen a plan or design.
推荐依据: 规划学习
共同关键词: grill · relentless · interview
melvynxInterview the user in batches of 10 questions with recommended answers to sharpen a plan, an idea or an app before building. Use when the user says grill me, wants a rigorous interview, or when create-software, create-internal-app or create-landing needs a confirmed brief.
推荐依据: 规划学习
共同关键词: grill · interview · sharpen
arrayawongsaitaStandalone composite skill that carries one idea from a relentless discovery interview through domain modeling, specification, a bounded design-review gate, and vertical ticket breakdown, then stops at published tickets without implementing.
推荐依据: 规划学习
共同关键词: grill · relentless · interview
brilliantroughReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
brilliantroughBuild and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
brilliantroughTalk a research idea through with the researcher before anything is designed or run. Use when a researcher brings a fuzzy idea, hypothesis, or direction ("我在想……", "你觉得这个方向……") and wants to think together rather than execute. Explore it through evidence-informed rounds of frontier questions, surface overlooked details, and sharpen what the researcher actually wants to observe; stop when both sides know which execution skill comes next — exp-campaign for a staged multi-branch plan, exp-batch for o
brilliantroughRun one-off research spot experiments with minimal ceremony. Use when explicitly requested, or for a missing datapoint, a rerun after failure (OOM, crash), a sanity check of one configuration, a minimal bug reproduction, or a cheap measurement that a campaign needs before deciding. At most one focused question; run, record, report in one line. Escalate to exp-batch if the spot check turns into a branch, or exp-campaign if it reveals a decision tree; if the question itself is still fuzzy, route b
