agentleFS
forcedotcomforcedotcom/salesforcedx-vscode/.claude/skills/grill-me/SKILL.md

grill-me

Skill1k starsChanged 27 days agoBSD-3-ClauseView on GitHub

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

193 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about forcedotcom/salesforcedx-vscode

The biggest 5 of 52 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 52

Talked about on GitHub and Stack Overflow (52 times).

On GitHub · 50

45 more on GitHub

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

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create lazily. First new context in a single-context repo → also create CONTEXT-MAP.md.

    line 43
  2. Distinctive:

    Cross-ref code: verify claims. "code cancels whole Orders, you said partial — which?"

    line 50

“Common” is measured: kept by at least 6 in 10 of the 177 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

How to grill

  • Interview until shared understanding. Walk each branch; resolve deps one at a time. Recommend an answer per question.
  • One question at a time. Wait for feedback.
  • Answerable from code → read it, don't ask.

Domain awareness

Existing docs first. Root CONTEXT-MAP.md lists contexts.

Single-context:

/
├── CONTEXT.md
├── docs/adr/
└── src/

Multi-context:

/
├── CONTEXT-MAP.md
├── docs/adr/                ← system-wide
├── .claude/CONTEXT.md       ← AI tooling
├── .github/CONTEXT.md       ← CI YAML
└── packages/
    ├── ordering/CONTEXT.md
    └── billing/CONTEXT.md

Contexts go wherever a coherent vocabulary lives — packages, plus non-source dirs (.claude/, .github/). Narrowest scope owning the term.

Root docs/adr/ + in-scope packages/*/docs/adr/ — why / what-rejected; grill against; avoid re-proposing reverted alternatives.

Create lazily. First new context in a single-context repo → also create CONTEXT-MAP.md; move existing root CONTEXT.md to its proper scope if it doesn't belong at root.

During the session

  • Glossary conflict: "glossary defines 'cancellation' as X, you mean Y — which?"
  • Fuzzy term: propose canonical. "'account' — Customer or User?"
  • Edge cases: probe boundaries.
  • Cross-ref code: verify claims. "code cancels whole Orders, you said partial — which?"
  • Update CONTEXT.md inline as terms resolve. Don't batch. Format: CONTEXT-FORMAT.md. Glossary only — no specs/scratch/decisions.
  • ADRs sparingly. Offer iff all three: hard to reverse, surprising without context, real trade-off. Format: ADR-FORMAT.md.

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.