agentleFS
Sign inStart free
pumpkit-iopumpkit-io/sdlc/skills/commands/grill-with-docs/SKILL.md

grill-with-docs

Skill2 starsChanged 10 days agoMITView on GitHub

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

195 other projects use a version of this, 95 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

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

  • 0

    Common

    Most of the 181 edited versions we read keep these.

  • 0

    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:

    Commit the docs this session wrote (GLOSSARY.md, ADRs) on the branch the worktree is on.

    line 17

“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

Load the worktrees skill and resolve the worktree for this work before writing anything. Do it before the first question: the glossary and ADRs the interview writes land in that worktree. A session already in a feature worktree for the same idea stays there; otherwise the idea gets a new feat/<slug> branch, and the branch keeps that name when the interview reshapes the idea.

Load the grilling and domain-modeling skills. When the work has a UI, also load the ui-design skill and grill its design plan as part of the interview: the plan only, no code.

Finishing

This skill is the first step of the feature flow: grill-with-docs, then to-spec, then to-tickets. Its only outputs are the decisions and the docs written during grilling. Specs, tickets, follow-up issues and edits to any other file belong to the later skills.

Shared understanding is reached when the user confirms it, or when the user invokes to-spec. Invoking the next skill counts as confirmation. At that point:

  1. Commit the docs this session wrote (GLOSSARY.md, ADRs) on the branch the worktree is on.
  2. Summarise the settled decisions, the design plan included. List every loose end (follow-up work, changes to other docs or rules) as input for the spec or for implement, not as actions to offer. When the design plan sets or changes the design direction, one loose end is running update-design once the UI ships.
  3. Close by naming the next step: to-spec, or implement when the work fits one session. Either runs in this session, in the same worktree.
  4. Release this session's worktree lock, as the worktrees skill's Release section says.

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