How do I install the T3d Grill Me skill?

Run npx skillmds@latest add coolsocket/t3d-grill-me in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is T3d Grill Me safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with T3d Grill Me?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is T3d Grill Me free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published T3d Grill Me?

coolsocket (@coolsocket) published this skill. Their other Agent Skills are listed on their SkillMD profile.

T3d Grill Me by coolsocket — Agent Skill

Name: T3d Grill Me
Author: coolsocket

T3d Grill Me

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use BEFORE writing code on any non-trivial feature — bounded context selection, aggregate boundaries, invariants, ubiquitous language. The harness assumes you grill-me first.

coolsocket cf01df9 2 files · 2.9 KB Updated Sep 17, 2026

File contents

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

If a question can be answered by exploring the codebase, explore the codebase instead.

When working in a t3d-harnessed project, prioritize grilling on:

Which bounded context does this feature belong to? (Look at CONTEXT-MAP.md.)
Which aggregate root owns the state change? Are we introducing a new aggregate?
What invariants must hold? List them — they'll go in INVARIANTS.md and each gets one failing test.
What ubiquitous language terms does this introduce? Are any of them already in contexts/<ctx>/CONTEXT.md? Are we redefining a term used in another context (that's fine — contexts have local languages)?
Are there cross-context calls? If yes, they MUST go through contexts.<other>.application.api (not internal domain imports). The PreToolUse hook will enforce this.

Frequently asked questions