agentleFS
Sign inStart free
GGGODLINGGGODLIN/gggodlin-cc-harness/skills/grill-with-docs/SKILL.md

grill-with-docs

Skill73 starsChanged 10 days agoMITView on GitHub

Grilling session that stress-tests a plan against the project's documented domain model, recording terms and decisions as they crystallise. Wrapper — runs grill-me then domain-modeling. Use when user wants to stress-test a plan against their project's language and documented decisions (openspec/glossary.md, openspec/decisions/). Do not use for: plan grilling with no documentation to maintain (grill-me alone), or terminology/ADR work with no plan to grill (domain-modeling alone).

195 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-matt-pocock-skills, decision-mapping and 8 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

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

  • 0

    Common

    Most of the 181 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. Distinctive:

    Call the Skill tool twice, for "grill-me" and "domain-modeling".

    line 9
  2. Very specific:

    Run the grilling per grill-me's rules.

    line 11

“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

Call the Skill tool twice, for "grill-me" and "domain-modeling".

Run the grilling per grill-me's rules; as terms and decisions crystallise during the session, record them per domain-modeling's rules (openspec/glossary.md inline, decisions sparingly). Do not enact the plan until the user confirms shared understanding.

踩過的坑

  • 2026-08-18 塌成 wrapper：原全文停在上游 2026-05 版、pin ed37663 從未真確（該 commit 只動 to-tickets）——「pin 指向 wrapper 化之後、內容停在 wrapper 化之前」讓週雷達永遠報綠。全文能力已由本機 grill-me（rounds 版）＋ domain-modeling（openspec 落點）覆蓋；CONTEXT.md / docs/adr/ 舊慣例與 2026-08-02 openspec 拍板矛盾，隨塌併移除本目錄 CONTEXT-FORMAT.md、ADR-FORMAT.md（domain-modeling 自帶 GLOSSARY-FORMAT.md / 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.

Check your setup, free