agentleFS
ShangBoyang0130ShangBoyang0130/dsh-rules/skills/盘我/SKILL.md

grill-me

Skill1 starsChanged 14 days agoMITView on GitHub

让 agent 反过来追问:对计划或决定做轮次盘问,直到没有默认假设。

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 74 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 78 projects that use this

  • simo97Skill

    request-refactor-plan

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

    Also in 45 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 73 projects that use this

  • RoentekSkill

    loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

    Also in 64 projects that use this

  • +1 more from simo97
  • +1 more from Lesani

The file

Files
SKILL.md

盘我

对用户正在做的计划、决定或想法,做一轮轮的追问,直到设计树的每个分支都被解决。

这个 skill 只由用户手动触发 —— 不被要求就不来盘人。

它绕过的是什么

人不知道自己漏了什么。 知道的以为是显然的,所以不说;对方不知道,也不问 —— 沟通就断在这儿。

让 agent 来问,等于把负担搬到它最擅长的地方:从它的知识出发,列出「要做这件事需要知道 什么」,问出来的正好是用户没想到要说的那些。

方法:决策树 + 前沿 + 轮次

把这件事画成一棵决策树:每个决定分叉出挂在它下面的决定。

前沿 = 前提已经定下来、现在就能问的那些问题,不用猜还没听到的答案。

一轮把整个前沿问完,然后停下等回答。回答会推动前沿外移,解锁原先问不了的问题。

一轮的写法:

❓ Q1 —— <问题标题>
   <问题正文,可以多段、可以带选项>
➡️ 推荐答案:<推荐怎么选,以及为什么>

❓ Q2 —— <同上>

(每题之间空一行)

依赖另一个还没答的问题的那些,属于下一轮 —— 不要挤进这一轮。

两条分工

  • 事实归 agent 查。 需要环境里的事实(文件、配置、命令输出),自己去查,或者派 subagent 去查 —— 不去问用户自己能查的东西。查的同时别阻塞:只有依赖那个事实的问题等结果, 前沿里其余的照问。
  • 决定归用户。 把每个决定摆到用户面前,然后等他答,不替他拍板。

(这跟 AGENTS.md 的「把选择权还给我」是同一条:agent 给天平,用户拨指针。)

三条边界(说清楚)

  1. 问什么,上限是 agent 的领域知识。 它不知道的坑,它问不出来 —— 它不会问 X, 除非它知道 X 有影响。
  2. 得先正确理解任务,否则问的方向就偏。任务含糊时,第一个问题就是澄清任务本身。
  3. 盘问有成本(轮次、时间)。所以它由用户手动触发 —— 觉得「这事值得先对齐」时才付。

完成标准

前沿空了:设计树每个分支都走到,没有东西被默默假设。

到这儿停下,把结论总结一遍,等用户确认「对齐了」再动手。

收尾时做一件事

盘完之后,如果冒出了新词或新的固定说法,问用户要不要收进术语表 —— 那份额外的共享词汇文件是 ~/.dsh\术语表.md:用户可以直接改,也可以由 AI 把候选词 连一句解释先写进去,再让用户确认。

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.