Skip to the usage guide
Grill Meby julianoczkowski

Grill Me Skill.

Resolve a design plan's unanswered decisions through a focused interview.

  • Brief Discovery
  • Constraints
Source Review · grill-meSKILL.md
Task Resolve a design plan's unanswered decisions through a focused interview. Produces A clearer shared understanding of the plan and its dependent decisions. Before You Start The source specifies an interview rather than a required document or implementation artifact.
Editorial summary · source reviewed 2026-11-02 · not a generated example

01 What It Does

Resolve a design plan's unanswered decisions through a focused interview

Challenge a design proposal through dependency-aware questions, repository inspection and a recommended answer for each unresolved decision.

Source-based workflowNot an execution benchmark

The Working Approach

Grill Me turns a rough plan into a structured design conversation. The agent follows each branch of the decision tree and resolves dependencies between decisions before moving on. It fits an early landing-page concept, settings redesign or dashboard plan whose important assumptions have not yet been challenged.

Its central boundary is useful for people working inside a repository: facts available in code, components, styles or tokens should be investigated there. The interview is reserved for decisions the user needs to make. For every question, the source asks the agent to include a recommended answer so the user can assess a proposal rather than invent one from scratch.

Expected Deliverables

  • A clearer shared understanding of the plan and its dependent decisions.
  • Focused questions for unresolved product or design choices.
  • A recommended answer accompanying each question.
See the Example Brief

From Brief to Review

  1. 01
    Read the proposed plan

    Identify the decisions that shape the page or feature. Trace which choices depend on earlier assumptions so the conversation follows a useful order.

  2. 02
    Resolve repository facts

    Inspect the codebase, components, styles and design tokens for answers already available. Avoid asking the user to recite information the agent can obtain directly.

  3. 03
    Interview the remaining decisions

    Work through unresolved branches one by one, explaining a recommended answer with each question. Continue until the user and agent share an understanding of the plan.

02 When to Use It

When to Use It

The source specifies an interview rather than a required document or implementation artifact.

A Good Fit

  • An early ideaA feature concept needs its assumptions challenged before implementation.
  • A disputed approachA designer wants a second perspective on the choices behind a proposed interface.

Limits to Check

  • Conversation outputThe source specifies an interview rather than a required document or implementation artifact.
  • Limited mechanismIt does not supply a scoring framework, user-research protocol or automatic proof that the resulting plan will succeed.

Bring These Inputs

  • Proposed designProvide the idea, plan or screen approach to examine.
  • Repository accessMake existing components and visual conventions available for investigation.
  • Decision contextShare the constraints and unresolved choices that require your judgment.

03 Decisions That Matter

Decisions That Matter

  1. Less repeated explanation

    Codebase inspection answers questions already settled by the current product.

  2. Useful recommendations

    Each remaining question comes with a proposed answer to evaluate.

  3. Decision order

    Dependencies are resolved before downstream details are debated.

04 Try a Focused Brief

Try a Focused Brief

The example brief below has not been tested. Check the skill’s setup before using it.

Review the Source and Setup

Provide the idea, plan or screen approach to examine.

Upstream Source File
https://github.com/julianoczkowski/designer-skills/blob/c259656c76d9758d7ead46b0d2f125cbe84f8665/grill-me/SKILL.md

The reference below opens the upstream instructions. Review the repository setup before using them; it is not an installation command.

Start With One Deliverable

Adapt the scope, source material and constraints in this brief before running the skill.

Example Brief
Use grill-me to challenge my plan for a team activity dashboard. The rough idea is a shared feed with filters for projects and people. Inspect our existing navigation, filter components and design tokens first, and answer any factual questions from the repository yourself. Then work through the unresolved decisions in dependency order: who needs the screen, what action they take after reading it, and which information belongs first. Give a recommended answer with each question and explain the tradeoff. Keep this pass focused on reaching shared understanding before we build.

Inspect the Result

Check the actual output against these observable criteria.

  • Questions concern unresolved choices rather than easily discoverable repository facts.
  • Each question includes a recommendation the user can accept or challenge.
  • Later questions remain consistent with decisions already resolved.

OpenDesign provides a local design workspace for coding agents. This listing does not mean the skill is bundled or that its external tools, credentials and software dependencies are included.

05 Source and License

Source and License

This page describes the pinned source revision linked below. Upstream behavior and requirements can change.

Source Owner
julianoczkowski
Skill File
SKILL.md
License
Apache-2.0
Reviewed Snapshot
2026-11-02 · c259656c76d9
Editorial Source Summary
Resolve a design plan's unanswered decisions through a focused interview.

Original summary by OpenDesign, based on the linked source. Repository stars are a dated popularity signal, not skill usage or a quality score.

06 Questions Before You Start

Questions Before You Start

Does this skill automatically create a brief?

The source does not require a file output. Its intended result is shared understanding through an interview.

What if the repository already contains an answer?

The agent should inspect the relevant code, component, style or token instead of asking the user.

Is it only for landing pages?

No. The source also gives dashboard, settings-page and portfolio ideas as example uses.

OpenDesign

Keep Your Brief and Design Work Together.

Keep your brief, source material and design work together in a local workspace. Check the skill’s own setup before adding it to your workflow.

Upstream Source File
https://github.com/julianoczkowski/designer-skills/blob/c259656c76d9758d7ead46b0d2f125cbe84f8665/grill-me/SKILL.md