agentleFS
lutzseverinolutzseverino/repo-standards/.agents/skills/grill-with-docs/SKILL.md

grill-with-docs

Skill0 starsChanged 5 days agoMITView on GitHub

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

196 other projects use a version of this, 98 of them edited.

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

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 2

    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:

    Read the contribution guide's Triage rules for publication, inference and amendments.

    line 9
  2. Distinctive:

    If one is missing, report it and stop that step rather than inventing a substitute.

    line 36
  3. Distinctive:

    If missing, report the missing definition and stop that step.

    line 38

“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

A prompt or brief naming this skill is its invocation.

Read the contribution guide's Triage rules for publication, inference and amendments. Invoke grilling and domain-modeling through the session's supported skill mechanism, with the request, recorded decisions and dated sources as context. Apply the guide's Triage inference and question-routing rules during the interview, and gather missing facts yourself. Invoke codebase-design and apply its Ownership check to proposed designs during the interview.

Once the interview and the guide's applicable owner gates are complete, invoke to-spec, then to-tickets. Pass the dated decisions and quoted words to both publication steps. Return the issue links, actual native parent/blocker relationships, inferences and open factual verification to the orchestrating agent for the guide's split decision and independent acceptance. At each native write, inspect the response; on failure, stop and report the exact missing edge and platform failure under the guide's publication rule.

For an amendment under the guide's Triage rules, interview, record the specification revision and invoke to-tickets on the delta. Return the changed contracts and native links for acceptance under the guide's Readiness section.

Reads

Paths are relative to each responsible repository root.

  • CONTRIBUTING.md: Triage, implementation contracts and readiness. If missing, use this method with independent review and grilling's missing-guide fallback.
  • The grilling, domain-modeling, to-spec and to-tickets skills: interview, domain documents and publication methods. If one is missing, report it and stop that step rather than inventing a substitute.
  • The codebase-design skill: the design check applied during the interview. If missing, report the missing definition and stop that step.

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.