Use when the user wants a plan, design, or PRD stress-tested before any build — relentlessly interrogates one decision at a time, grounds every question in the codebase, hunts contradictions against the domain language and the code, and challenges the load-bearing assumptions. Triggered by "grill me", "stress-test this plan", "poke holes in my design". Composable — run standalone or as an adversarial pass before /plan feature.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# grill
> **Portable mirror — generated, do not edit.** The canonical workflow lives at
> [`skills/grill/SKILL.md`](../../../skills/grill/SKILL.md); read that file for the full instructions.
> This mirror carries only agentskills.io-spec-legal frontmatter so harnesses that
> discover skills under `.agents/skills/` can find and route to the skill.
>
> Regenerate with `node scripts/generate-agents-skills.mjs`.
Read the linked document in full and follow its complete workflow, including prechecks and stop conditions. Resolve its link relative to this SKILL.md, not the project working directory. The plugin root is three directories above this file. Resolve package paths such as `skills/` and `scripts/` from that root and relative links in the canonical document from its own directory. Keep the user’s project as the target of project operations.
…
The line at the top of this page pins the label git:20260919.176b605, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_xxlypx6dsvygui4q
GET https://markdownregistry.com/api/v1/resolve?ref=kanevry/session-orchestrator/grill
GET https://markdownregistry.com/api/v1/blob/4589bc0ce7cb26dc66f1f09026a40c9699111d72e5ecafcffd1fd07fe1a93633
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
kanevry/session-orchestrator · .agents/skills/architecture/SKILL.md · Use when the user asks to improve architecture, find refactoring opportunities, surface deepening opportunities…
kanevry/session-orchestrator · .agents/skills/autopilot/SKILL.md · Use this skill when running an autonomous session-orchestration loop. Chains session-start → session-plan →…
kanevry/session-orchestrator · .agents/skills/bootstrap/SKILL.md · Use this skill when scaffolding the minimum repository structure required by session-orchestrator. Invoked…
kanevry/session-orchestrator · .agents/skills/brainstorm/SKILL.md · Use when you have a feature idea but the scope or UX is still ambiguous — runs a lightweight Socratic design dialogue…
kanevry/session-orchestrator · .agents/skills/claude-md-drift-check/SKILL.md · Use when detecting drift between CLAUDE.md (or AGENTS.md, the Codex CLI alias) / _meta narrative and live repository…
kanevry/session-orchestrator · .agents/skills/debug/SKILL.md · Use when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging…
kanevry/session-orchestrator · .agents/skills/deepen/SKILL.md · Make a task deeper, not bigger. Use when the user asks for a deeper or more ambitious version of a task (tiefer, geh…
kanevry/session-orchestrator · .agents/skills/discovery/SKILL.md · Use this skill when running systematic quality discovery and issue detection. Runs modular probes adapted to the…
kanevry/session-orchestrator · .agents/skills/dispatcher/SKILL.md · Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates…
kanevry/session-orchestrator · .agents/skills/docs-orchestrator/SKILL.md · Use this skill when orchestrating documentation generation and updates within a session. Maps session scope to…
sethgammon/citadel · skills/grill/SKILL.md · Relentless one-question-at-a-time interview that sharpens a vague plan or design into shared understanding before any…
moonlight-lupin/agent-skills · plugins/dev-pipeline/skills/grill/SKILL.md · Use when a plan is fuzzy and needs hardening before a spec — decision-tree grilling in frontier rounds, every open…
kerberosclaw/kc_ai_skills · grill/SKILL.md · Use when the user says 先討論 / wants to align on a fuzzy idea before building, or before any non-trivial implementation…
kanevry/session-orchestrator · skills/grill/SKILL.md · Use when the user wants a plan, design, or PRD stress-tested before any build — relentlessly interrogates one decision…
kanevry/session-orchestrator · .cursor/skills/grill/SKILL.md · Use when the user wants a plan, design, or PRD stress-tested before any build — relentlessly interrogates one decision…
kanevry/session-orchestrator · .codex-plugin/skills/grill/SKILL.md · Use when the user wants a plan, design, or PRD stress-tested before any build — relentlessly interrogates one decision…
technicalpickles/pickled-claude-plugins · plugins/stay-principled/skills/grill/SKILL.md · Walk a depth-first decision tree anchored to a project's documented principles before brainstorming opens options…
varun-singhh/lfg · plugin/skills/grill/SKILL.md · Interviews the user one question at a time, informed by the code graphs, until the goal, users, acceptance criteria and…
