Agent skill

Grill

by ntorga in ntorga/agent-starter-kit

Protocol that interviews the user in rounds over the Architect's design tree.

MITAuto-check passedAI & LLM Engineering

Install Grill

skills CLI
$ npx skills add ntorga/agent-starter-kit --skill grill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ntorga/agent-starter-kit grill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ntorga/agent-starter-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grill .claude/skills/grill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
grill
GitHub stars
146
Token cost
~1.3k tokens
SKILL.md length
702 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

Protocol that interviews the user in rounds over the Architect's design tree.

  • Works in 6 steps: Select path. Check long-term memory… → Build the tree. Dispatch the Architect… → Work the frontier in rounds. The… → …
  • AI & LLM Engineering work in your project
  • SKILL.md covers Purpose, Procedure, Post-Grill Execution and Guardrails
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Grill is an agent skill from ntorga/agent-starter-kit. Protocol that interviews the user in rounds over the Architect's design tree. Three paths control depth. Produces plan.md, arch.md, impl.md.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering. The repository describes itself as: The scaffold for your multi-model, personalized Natural Language AI Harness (NLAH) . The licence is MIT.

When your agent uses it

  • AI & LLM Engineering work in your project

Example prompts

  • “/grill”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Select path. Check long-term memory (uses: skills/agent-memory/SKILL.md) for a recorded grill path under ## Preferences. If one exists…
  2. Build the tree. Dispatch the Architect (personas/architect.md) (follows: skills/dispatch/SKILL.md) in tree mode with the selected path…
  3. Work the frontier in rounds. The frontier is every open node in tree.md whose dependencies are all settled. Send up to 5 frontier…
  4. Checkpoint after each round. Transcribe the settled decisions of the round into the relevant artifact files. Create a file if it does not…
  5. Re-tree on scope change. If an answer does not map to a node in the tree — a new branch, a scope change — re-dispatch the Architect…
  6. Terminate. The grill is done when the frontier is empty. Present plan.md, arch.md, and impl.md to the user. Do not act until the user…

What it can do on your machine

Read from SKILL.md and the folder at commit 851e942. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Grill loads about 1.3k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 702 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ntorga/agent-starter-kit at commit 851e942, republished under its MIT licence (© ntorga). 702 words, ~1,264 tokens.

Download SKILL.mdSave it as .claude/skills/grill/SKILL.md (or your agent's skills folder).
name
grill
description
Protocol that interviews the user in rounds over the Architect's design tree. Three paths control depth. Produces plan.md, arch.md, impl.md.
usedBy
maestro
version
0.2.1
lastUpdated
2026-09-12

Purpose

Reach shared understanding with the user before execution. The Architect owns the design tree — the decisions the feature must settle, mapped with dependencies, pruned by path, ranked by impact. You work the frontier in rounds: ask up to 5 frontier questions, wait for the user's answers, transcribe the settled decisions into the artifacts. After the user confirms, execution is autonomous. The user is bothered in rounds, not on every micro-delivery.

Procedure

The path determines which branches the tree explores. Step 1 resolves it from long-term memory, or asks the user when none is recorded:

  • Beginner — business questions only. The Architect infers architecture from the maintenance, lightweight, and safe principles (KISS, single responsibility, safe boundaries — rules/code/general.md). Ceiling: 30 business questions.
  • Tinkerer — business and architecture questions. Ceiling: 30 business, 10 architecture.
  • Pro — business, architecture, and implementation questions. Ceiling: 100 questions per branch.

Artifacts live at .memory/plan/<feature-slug>/:

  • tree.md — the design tree. The Architect owns it.
  • plan.md — acceptance criteria, from the settled business decisions.
  • arch.md — directory structure, layer separation, reference projects. Tinkerer and pro. Beginner gets defaults.
  • impl.md — epics grouped at one day of work, with parallelizable groups.

You transcribe plan.md, arch.md, and impl.md as decisions settle. The Architect owns tree.md and the grounded impl.md.

  1. Select path. Check long-term memory (uses: skills/agent-memory/SKILL.md) for a recorded grill path under ## Preferences. If one exists, proceed with it — state the path in the first message to the user so they can override in one word. If the user overrides, replace the recorded entry. If none exists, ask the user to choose: beginner, tinkerer, or pro. Record the choice under ## Preferences as [grill] path: <beginner | tinkerer | pro>.

  2. Build the tree. Dispatch the Architect (personas/architect.md) (follows: skills/dispatch/SKILL.md) in tree mode with the selected path. The Architect writes tree.md.

  3. Work the frontier in rounds. The frontier is every open node in tree.md whose dependencies are all settled. Send up to 5 frontier questions per round, ordered by impact. Each question carries the tree's recommendation. Wait for the user's answers before the next round.

    Format each round:

    ❓ **Q1** - **<question title>**: <question body>
    
    ➡️ <recommendation from the tree>
    • If the frontier exceeds 5, ask the 5 questions whose answers unblock the most downstream questions.
    • A node that depends on another question open in this round belongs to a later round.
    • A node that depends on a fact in ## Facts: dispatch a host exploration agent (e.g., the host's Explore tool) to find the fact. Never ask the user for a fact you can look up. Do not block the rest of the frontier on a running fact-finder. Record the found fact in tree.md when it lands.
  4. Checkpoint after each round. Transcribe the settled decisions of the round into the relevant artifact files. Create a file if it does not exist. This survives context compaction and keeps the session on track.

  5. Re-tree on scope change. If an answer does not map to a node in the tree — a new branch, a scope change — re-dispatch the Architect (personas/architect.md) (follows: skills/dispatch/SKILL.md) in tree mode to extend tree.md. Settled nodes stay settled.

  6. Terminate. The grill is done when the frontier is empty. Present plan.md, arch.md, and impl.md to the user. Do not act until the user confirms you have reached a shared understanding.

Show full SKILL.md (169 more words)Show less

Post-Grill Execution

After the user confirms, the plan-management flow takes over (follows: skills/plan-management/SKILL.md): ground, review, then the coder per epic.

Interrupt the user only for escalations:

  • A fact that contradicts a settled decision.
  • A business rule the grill did not cover.

The Architect classifies every discovery as adjust (folded into the remaining epics, no user gate) or escalate (user gate). Anything else, the Architect decides and documents inline.

Guardrails

  • Never ask for a path that is recorded in long-term memory. State it; do not ask.
  • The quality filter and the ceilings are applied by the Architect in the tree. Stop when the frontier is empty, not when you hit a ceiling.
  • Send at most 5 questions per round.
  • Never ask the user for a fact you can look up. Dispatch a subagent.
  • Never skip the checkpoint.
  • Never work a node whose dependencies are unsettled.
  • Never act on the tree until the user confirms shared understanding.
  • Never let a persona talk to the user directly. You are the only voice.

© ntorga, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/grill of ntorga/agent-starter-kit.

Open the folder on GitHubat commit 851e942

Compare with similar skills

Grill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Grill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Grill this skillntorga/agent-starter-kit146—~1.3kAutomated safety check: PassMIT
Agent BuildershareAI-lab/learn-claude-code78k6 repos~1.2kAutomated safety check: PassMIT
Planning With Filesjarrodwatts/claude-code-config1.1k5 repos~967Automated safety check: PassNone
Codebase Managementgiancarloerra/SocratiCode3.3k1 repos~1.8kAutomated safety check: PassAGPL-3.0
Context Compressionguanyang/open-agent-hub9732 repos~4.6kAutomated safety check: PassMIT
Looperksimback/looper710—~2.7kAutomated safety check: NotesMIT

Similar skills

  • Agent Builder

    shareAI-lab/learn-claude-code

    Design and build AI agents for any domain. An agent skill from shareAI-lab/learn-claude-code.

    78k GitHub starsUsed in 6 repos~1.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Planning With Files

    jarrodwatts/claude-code-config

    Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage.

    1.1k GitHub starsUsed in 5 repos~967 tokens
    AI & LLM EngineeringAuto-check passed
  • Codebase Management

    giancarloerra/SocratiCode

    Set up, index, and manage SocratiCode codebase indexing. An agent skill from giancarloerra/SocratiCode.

    3.3k GitHub starsUsed in 1 repo~1.8k tokens
    AI & LLM EngineeringAuto-check passed
  • Context Compression

    guanyang/open-agent-hub

    This skill should be used when long-running agent sessions need context compression, structured summarization, compaction, token-per-task optimization, or durable handoff summaries that preserve…

    973 GitHub starsUsed in 2 repos~4.6k tokens
    AI & LLM EngineeringAuto-check passed
  • Looper

    ksimback/looper

    Scaffold a well-designed agent loop with best-practice coaching and a cross-model review council.

    710 GitHub stars~2.7k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Docs Planner

    strands-agents/harness-sdk

    Identify documentation gaps and prioritize the docs backlog.

    8.7k GitHub stars~821 tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed

More from ntorga/agent-starter-kit

All 21 skills in this repo
  • Agent Decision

    ntorga/agent-starter-kit

    Deterministic self-evaluation rubric for decision escalations — scored every run using the FRAME framework.

    146 GitHub stars~1.7k tokensUpdated 25 days ago
    Auto-check passed
  • Agent Memory

    ntorga/agent-starter-kit

    Long-term and session memory across sessions. An agent skill from ntorga/agent-starter-kit.

    146 GitHub stars~2.7k tokensUpdated 25 days ago
    Auto-check passed
  • Architect Design Tree

    ntorga/agent-starter-kit

    Builds the design tree for the grill — decisions mapped as nodes with dependencies, recommendations, and impact, pruned by path.

    146 GitHub stars~1.2k tokensUpdated 25 days ago
    Auto-check passed
  • Architect Impl Grounding

    ntorga/agent-starter-kit

    Grounds the grill's settled decisions in the codebase — annotates impl.md with file paths, signatures, reference files, test specs, and LOC; re-grounds the next epic after each landing.

    146 GitHub stars~944 tokensUpdated 25 days ago
    Auto-check passed
  • Boot

    ntorga/agent-starter-kit

    Session startup — gitignore, auto-update, memory, rules, context, CLI config, and greet.

    146 GitHub stars~937 tokensUpdated 25 days ago
    Auto-check passed
  • Browser Inspect

    ntorga/agent-starter-kit

    Browser inspection and interaction for verifying rendered web UI during development.

    146 GitHub stars~2k tokensUpdated 25 days ago
    Auto-check passed

Questions about Grill

What does Grill do?

Protocol that interviews the user in rounds over the Architect's design tree. Grill is an agent skill from ntorga/agent-starter-kit. Protocol that interviews the user in rounds over the Architect's design tree.

When should I use Grill?

Grill fits situations like: AI & LLM Engineering work in your project.

How do I install Grill in Claude Code?

Run `npx skills add ntorga/agent-starter-kit --skill grill -a claude-code`. Or copy the skill folder (skills/grill in ntorga/agent-starter-kit) into .claude/skills/grill in your project. Claude Code loads it when a task matches its description.

How do I install Grill in Codex?

Run `npx skills add ntorga/agent-starter-kit --skill grill -a codex`. Or copy the skill folder (skills/grill in ntorga/agent-starter-kit) into .agents/skills/grill in your project. Codex loads it when a task matches its description.

Can I use Grill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ntorga/agent-starter-kit --skill grill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grill, .gemini/skills/grill, .github/skills/grill and .opencode/skills/grill in your project.

What does Grill need to run?

SKILL.md names no scripts, command-line tools or credentials: Grill is instructions for the agent only.

Does Grill access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Grill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Grill use?

Grill is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Grill use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Grill?

Skills that share tags, products or a category with Grill: Agent Builder (shareAI-lab/learn-claude-code, 78k stars), Planning With Files (jarrodwatts/claude-code-config, 1.1k stars), Codebase Management (giancarloerra/SocratiCode, 3.3k stars) and Context Compression (guanyang/open-agent-hub, 973 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Grill?

ntorga (a GitHub user) maintains it in ntorga/agent-starter-kit, which has 146 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on September 12, 2026.

Source: ntorga/agent-starter-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.