grillkit

Interrogates ideas, plans, and designs through structured question rounds with recommended answers.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/mimukit/skills --skill grillkit-mimukit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grillkit
Source: https://github.com/mimukit/skills/tree/main/skills/grillkit
Command: npx skills add https://github.com/mimukit/skills --skill grillkit-mimukit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ideas, plans, and designs often contain hidden assumptions, unresolved decisions, and vague edge cases that only surface during implementation, causing rework. This Skill stress-tests a concept before any building starts by systematically surfacing every open decision and forcing each one to be settled with the user. ## Core Features & Use Cases - Design-tree interrogation: Maps the subject as a tree of decisions and asks the unblocked frontier in numbered rounds, each question carrying stakes, trade-off-laden options, and a recommended answer. - Fact gathering via sub-agents: Looks up codebase facts itself instead of asking the user, dispatching sub-agents for environment questions and marking blocked questions as pending. - Plan hardening with provenance: Folds settled decisions back into an existing plan file and stamps it with a Grilled: YYYY-MM-DD line that downstream tooling reads as readiness provenance. - Use Case: Before implementing a new architecture, ask the agent to grill your plan file; it returns the same file hardened with every decision resolved and stamped, ready to be converted into issues or built. ## Quick Start Ask the agent to grill your current plan or idea and pressure-test every unresolved decision before you start building.

Frequently Asked Questions about grillkit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test a plan before implementing it?

Ask the agent to grill your plan file or idea. It maps the subject as a design tree, asks each round of unblocked decisions with recommended answers, and folds the settled decisions back into the plan with a Grilled date stamp.

What kinds of subjects can be grilled with this approach?

Any concept works: a rough idea, a design in your head, an existing plan file, an architecture, or a pull request. No formal plan document is required to start the interrogation.

Does the grilling process update my existing plan file?

Yes. When started from an existing plan file, settled decisions are folded back into that same file in place, and a Grilled: YYYY-MM-DD stamp is added under the title. For other inputs, it asks where the decisions should be recorded.

When should I not use a structured grilling workflow?

Skip it when the task is a small, well-understood change with no open design decisions, or when you want implementation to start immediately. The grill ends at shared understanding and never begins building on its own.

How does the skill handle questions that need facts from the codebase?

It never asks the user for discoverable facts. It looks them up itself or dispatches a sub-agent, marks dependent questions as pending with a waiting indicator, and asks the rest of the round without blocking.