القائمة
A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go. Combines grilling with domain-modeling.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a Claude Code session should delegate a well-scoped task to Codex CLI for isolated execution, then summarize Codex report. 适用于在 Claude Code 中让 Codex 执行已明确范围的任务并回报结果。
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Audit Claude Code configuration for malicious hooks, MCP servers, and suspicious commands. Use this skill whenever the user clones a new project, installs a skill/plugin, configures MCP servers, or asks to check security. Also trigger when the user mentions "audit", "security check", "malicious", "hooks", or "is this safe".
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".
| name | grill-with-docs |
| description | A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go. Combines grilling with domain-modeling. |
| install-targets | claude |
| source | Adapted from mattpocock/skills — https://github.com/mattpocock/skills |
Run a /grilling session, using the /domain-modeling skill.
This means:
First, /domain-modeling — establish or review the project's domain language (CONTEXT.md) and create ADRs for key decisions as they emerge during discussion.
Then/meanwhile, /grilling — interview the user relentlessly about every aspect of their plan, resolving each branch of the design tree one question at a time.
Use AskUserQuestion tool for every question, one at a time, with 2-4 concrete multiple-choice options. If a question can be answered by exploring the codebase, explore it instead of asking.
When finished, provide a concise summary of all decisions made and what documentation was created/updated.
