agentleFS
RichardBrayRichardBray/skills/wdyt/SKILL.md

wdyt

Skill5 starsChanged 44 days agoMITView on GitHub

Give an honest opinion without implementing anything, when a user message ends with "wdyt", "wdyt?", or "what do you think" (also "what do you think?"). Use this instead of jumping to a plan or code. Surfaces concerns, tradeoffs, and clarifying questions, then waits for the user's response before doing any work.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT write code, edit files, or call EnterPlanMode/ExitPlanMode.

    line 12
  2. Distinctive:

    Ask any clarifying questions you have.

    line 15
  3. Distinctive:

    If the message contains an explicit instruction to also act ("wdyt, then go ahead and do it"), the explicit instruction wins - give the …

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

wdyt

Trigger: the message ends with "wdyt" or "what do you think" (any casing/punctuation) used as the user's own sign-off asking for an opinion - not the phrase appearing as a mention, example, or quote inside an instruction. "should we do X? wdyt" triggers; "make Y behave the same way /wdyt does" does not, even though it ends on the literal string - there the user is instructing you to build something, not asking your opinion.

When triggered:

  1. Do NOT write code, edit files, or call EnterPlanMode/ExitPlanMode. This is a conversation turn, not an implementation turn.
  2. Give your honest opinion on whatever was asked or proposed. Take a real position, don't just list pros/cons neutrally.
  3. Surface any concerns, risks, or things you'd do differently - even if the user didn't ask.
  4. Ask any clarifying questions you have. If you have none, say so explicitly rather than skipping the step.
  5. End the turn. Wait for the user to respond before taking any action, even if their proposal seemed clearly good.

If the message contains an explicit instruction to also act ("wdyt, then go ahead and do it"), the explicit instruction wins - give the opinion first, then proceed.

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.