agentleFS
Sign inStart free
feiskyerfeiskyer/codex-settings/skills/grill-me/SKILL.md

grill-me

Skill248 starsChanged 4 months agoMITView on GitHub

仅当用户显式调用 `$grill-me`，或明确要求"追问我""挑战这个方案""拷打这个设计"时使用。逐问逐答检验关键假设与取舍，默认在对话中交付；仅按要求维护术语表和 ADR。

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brief-to-tasks, writing-beats and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • julianoczkowskiSkill

    brief-to-tasks

    Break a design brief into an ordered checklist of independently buildable tasks using vertical slices. Saves as a markdown checklist. Use when user wants to break down work, create tasks from a brief, plan implementation order, or mentions "tasks" or "breakdown".

    Also in 7 projects that use this

  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 66 projects that use this

  • simo97Skill

    request-refactor-plan

    Use this skill when user wants to create a refactor plan.

    Also in 43 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 71 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 65 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • +2 more from simo97

The file

Create a free account to mount
Files
SKILL.md

追问会话

聚焦当前方案中会影响实施的关键假设与取舍。关键问题已有答案、剩余问题不影响当前决定时，总结已确认结论与未决事项并结束追问。

按当前问题查阅既有材料：根目录的 CONTEXT.md 或 CONTEXT-MAP.md，以及 docs/adr/ 下相关的 ADR，沿用已确认的概念和决策。

默认在对话中交付。只有用户要求维护术语表或 ADR 时才写入文件，优先使用用户指定的位置；确认讨论结论本身不代表授权写文档。

参考何时读
references/context-md.md第一个术语敲定、要真正写入 CONTEXT.md 时；或需要判断单上下文还是多上下文结构时
references/adr.md一个决策通过了下面三条门槛、要落笔写 ADR 时

核心规则

一次只问一个问题，等回复后再问下一个。一次抛出多个问题会让人无所适从。每个问题都给出你的推荐答案。

能从当前范围内的代码查到的事实就直接查，不要问。把影响当前方案的未决取舍交给用户决定，不重新追问已确认或无关的决策。

在用户明确确认达成共识之前，不要开始执行方案。

追问时的动作

对照术语表质疑。 用户的用词与 CONTEXT.md 里的定义冲突时立即指出："你的术语表把'取消'定义为 X，但你现在似乎指的是 Y —— 到底是哪个？"

磨尖模糊表达。 遇到含糊或多义的词，提出精确的规范术语："你说的'账户' —— 是 Customer 还是 User？这是两个不同概念。"

用具体场景压力测试。 讨论领域关系时构造边界场景，逼出概念之间的精确边界。

与代码交叉验证。 用户陈述某物如何运作时，去看代码是否一致，发现矛盾立即暴露："你的代码取消的是整个 Order，但你刚说可以部分取消 —— 哪个是对的？"

按授权记录。 已获授权维护术语表时，术语敲定就更新 CONTEXT.md 或用户指定的文件；需要首次写入时再创建。

ADR 的门槛

已获授权维护 ADR，且三条全部成立时才写入：

  1. 难以逆转 — 将来改变主意的代价可观
  2. 缺乏上下文则令人费解 — 未来读者会困惑"为什么这样做？"
  3. 确实是权衡的结果 — 存在真正的替代方案，且基于具体理由选了其一

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free