agentleFS
Sign inStart free
vpeetla-aivpeetla-ai/multi-agent-system-pattern/.cursor/skills/grill-with-context/SKILL.md

grill-with-context

Skill2 starsChanged 5 months agoMITView on GitHub

Interview the user about a plan or design until decisions are resolved, while updating CONTEXT.md terms and noting ADR candidates. Use before large features, cross-repo integrations, or when requirements feel vague.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Do not start coding until grilling is complete

    line 34
  2. Distinctive:

    Do not ask five questions in one message

    line 35
  3. Distinctive:

    Prefer multiple-choice when options are finite

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Context

Inspired by mattpocock/skills grill-with-docs — org-specific version.

When to use

  • New feature spanning multiple stack layers
  • Unclear which repo should own the change
  • User says "build X" without success criteria

Process

  1. Restate the goal in one sentence; ask if correct
  2. Grill — ask one question at a time until resolved:
    • Which stack layer? (see governed-ai-stack)
    • What defines done? (test, demo URL, metric)
    • Side effects? (gateway/HITL required?)
    • Stub mode or live API keys?
  3. Sharpen vocabulary — if the user uses vague terms, propose CONTEXT.md entries
  4. ADR candidates — flag decisions that need an ADR in ai-architecture-portfolio
  5. Output — short plan with repo, files, test strategy, out-of-scope list

Rules

  • Do not start coding until grilling is complete
  • Do not ask five questions in one message
  • Prefer multiple-choice when options are finite

After grilling

Suggest tdd-agent-loops for implementation or to-prd equivalent: write plan to docs/plans/<slug>.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