agentleFS
Sign inStart free
rengwurengwu/wayfinder-maps/skills/.optional/grill-with-docs/SKILL.md

grill-with-docs

Skill137 starsChanged 4 months agoMITView on GitHub

A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 3

    Distinctive

    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:

    Ask the questions one at a time, waiting for feedback on each question before continuing.

    line 9
  2. Distinctive:

    If a *fact* can be found by exploring the codebase or project files, look it up rather than asking me.

    line 11
  3. Distinctive:

    Do not enact the plan until I confirm we have reached a shared understanding.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 178 edited versions of this file we could read. “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

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.

If a fact can be found by exploring the codebase or project files, look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.

Throughout the session, apply the domain-modeling skill: challenge my terms against the glossary in CONTEXT.md, sharpen fuzzy language into canonical terms, stress-test relationships with concrete edge-case scenarios, and update CONTEXT.md and docs/adr/ inline as terms and decisions crystallise — creating those files lazily if they don't exist yet.

Do not enact the plan until I confirm we have reached a shared understanding.

Download now (ZIP)

  • Other versions192 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 96

    1. mattpocock/skills★ 309k54% same
    2. QuivrHQ/quivr★ 40k54% same
    3. GreyDGL/PentestGPT★ 16k56% same
    4. formbricks/formbricks★ 13k54% same
    5. ArcReel/ArcReel★ 6k54% same
    6. withcoral/coral★ 4.9k54% same
    7. bestofjs/bestofjs★ 3.1k56% same
    8. CelestoAI/SmolVM★ 1.1k54% same
    9. moeru-ai/xsai★ 66454% same
    10. stevesolun/ctx★ 58350% same

    86 more not listed

    Wrote their own version · 96

    1. vinvcn/mattpocock-skills-zh-CN★ 5.5ksame name
    2. bholmesdev/hubble.md★ 1.5ksame name
    3. sanity-io/next-sanity★ 956same name
    4. nodetool-ai/nodetool★ 603same name
    5. devcxl/mattpocock-skills-zh★ 522same name
    6. victorgarciaesgi/regle★ 508same name
    7. openvetta/open-vetta★ 302same name
    8. danielvm-git/bigpowers★ 286same name
    9. brickbots/PiFinder★ 250same name
    10. InditexTech/weavejs★ 246same name

    86 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use decision-mapping, setup-matt-pocock-skills 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.
    • FabienDehopreSkill

      decision-mapping

      Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.

      Also in 9 projects that use this

    • GoogleSkill

      setup-matt-pocock-skills

      Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

      Also in 163 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 58 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 33 projects that use this

    • RoentekSkill

      loop-me

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

      Also in 48 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 59 projects that use this

  • In this repository13 other files it gives its agents.

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