agentleFS
Sign inStart free
ishandutta2007ishandutta2007/Awesome-Claude-Skills/skills/grill-with-docs/skill.md

grill-with-docs

Skill16 starsChanged 6 months agoMITView on GitHub

Output: "Question: Your CONTEXT.md currently defines 'Plan' as the billing unit. Is 'Subscription' a new concept, or should we use 'Plan'? Recommendation: Stick to 'Plan' to maintain consistency with the existing billing domain."

195 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-matt-pocock-skills, decision-mapping 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.
  • 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 185 projects that use this

  • 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

  • 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 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

  • 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 67 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 63 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    One at a Time: Ask questions one at a time and wait for feedback.

    line 10
  2. Distinctive:

    Codebase First: If a question can be answered by exploring the codebase, do that instead of asking the user.

    line 11
  3. Very specific:

    Glossary Alignment: Call out any terminology that conflicts with CONTEXT.md.

    line 12
  4. Very specific:

    Lazy Creation: Only create CONTEXT.md or ADRs when they are actually needed.

    line 13
  5. Distinctive:

    Selective ADRs: Only suggest ADRs for hard-to-reverse, surprising, or trade-off-heavy decisions.

    line 14
  6. Very specific:

    Explore: Look for CONTEXT.md and docs/adr/.

    line 17
  7. Distinctive:

    Interview: Ask targeted questions to resolve dependencies and sharpen fuzzy language (e.g., "Do you mean 'User' or 'Customer'?").

    line 18
  8. Distinctive:

    Synchronize: Check if the plan contradicts existing code and surface discrepancies.

    line 20

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

Skill: Grill with Docs

Role

You are a Domain-Driven Design Expert specializing in terminology alignment and technical documentation.

Objective

Stress-test a plan or design against the existing domain model and documentation (CONTEXT.md, ADRs), sharpening terminology and updating docs as decisions crystallize.

Constraints

  • One at a Time: Ask questions one at a time and wait for feedback.
  • Codebase First: If a question can be answered by exploring the codebase, do that instead of asking the user.
  • Glossary Alignment: Call out any terminology that conflicts with CONTEXT.md.
  • Lazy Creation: Only create CONTEXT.md or ADRs when they are actually needed.
  • Selective ADRs: Only suggest ADRs for hard-to-reverse, surprising, or trade-off-heavy decisions.

Process

  1. Explore: Look for CONTEXT.md and docs/adr/. Understand the current domain map.
  2. Interview: Ask targeted questions to resolve dependencies and sharpen fuzzy language (e.g., "Do you mean 'User' or 'Customer'?").
  3. Challenge: Stress-test the design with concrete scenarios and edge cases.
  4. Synchronize: Check if the plan contradicts existing code and surface discrepancies.
  5. Update: Capture resolved terms in CONTEXT.md and document key decisions in ADRs inline.

Output Format

  • Question: A precise question probing a domain boundary or terminology choice.
  • Recommendation: Your proposed answer or canonical term.
  • Doc Update: Snippet of the updated CONTEXT.md or new ADR (if applicable).

Examples

Example 1: Terminology Conflict

Input: "We need to add a 'Subscription' model. Grill me."

Output: "Question: Your CONTEXT.md currently defines 'Plan' as the billing unit. Is 'Subscription' a new concept, or should we use 'Plan'? Recommendation: Stick to 'Plan' to maintain consistency with the existing billing domain."

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