agentleFS
Sign inStart free
ntaffziintaffzii/Skill-Agents/skills/productivity/grill-with-docs/SKILL.md

grill-with-docs

Skill4 starsChanged 2 months agoMITView on GitHub

Planning interview skill that asks sharp questions before execution and turns decisions into durable project docs, domain language, PRDs, or ADR notes. Use when the user has an idea, feature, plan, product change, or unclear request that needs alignment before implementation.

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

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 11

    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:

    Use this skill before implementation when alignment matters.

    line 8
  2. Distinctive:

    Ask what outcome the user wants, who it is for, and what must not change.

    line 13
  3. Distinctive:

    Ask what can be deferred.

    line 18
  4. Distinctive:

    Prefer one precise term over repeated explanatory phrases.

    line 25
  5. Distinctive:

    Create or update lightweight docs only when they will help future sessions.

    line 28
  6. Distinctive:

    Use PRD for product behavior.

    line 29
  7. Distinctive:

    Use ADR for architectural decisions.

    line 30
  8. Distinctive:

    Use glossary/context docs for domain language.

    line 31
  9. Distinctive:

    Ask the fewest questions that unblock execution.

    line 43
  10. Distinctive:

    Do not interview forever; once enough context exists, recommend a path.

    line 45
  11. Distinctive:

    If the user is absent, make conservative assumptions and label them.

    line 46

“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

Grill With Docs

Use this skill before implementation when alignment matters.

Workflow

  1. Establish intent
    • Ask what outcome the user wants, who it is for, and what must not change.
    • Identify success criteria and failure modes.
  2. Challenge scope
    • Find the smallest useful version.
    • Ask what can be deferred.
    • Surface hidden dependencies, permissions, data needs, and integration points.
    • Separate must-have, should-have, nice-to-have, and out-of-scope items when the request is large.
  3. Build shared language
    • Name the domain concepts in the user's words.
    • Define ambiguous terms.
    • Prefer one precise term over repeated explanatory phrases.
  4. Convert decisions into docs
    • Create or update lightweight docs only when they will help future sessions.
    • Use PRD for product behavior.
    • Use ADR for architectural decisions.
    • Use glossary/context docs for domain language.
  5. End with an execution-ready brief
    • Goals
    • Non-goals
    • Decisions
    • Open questions
    • First implementation slice
    • Validation plan

Question Rules

  • Ask the fewest questions that unblock execution.
  • Group related questions.
  • Do not interview forever; once enough context exists, recommend a path.
  • If the user is absent, make conservative assumptions and label them.

Verification

  • The brief has a clear goal and non-goals.
  • Decisions are separated from open questions.
  • The first implementation slice is small enough to execute.
  • Any assumptions are labeled.

Output Format

End with:

  • Goals
  • Non-goals
  • Scope
  • Decisions
  • Open questions
  • First implementation slice
  • Validation plan

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