# 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. - Skill: `coolsocket/t3d-grill-me` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add coolsocket/t3d-grill-me` - Raw SKILL.md: https://api.skillmd.com/api/skills/coolsocket/t3d-grill-me/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: coolsocket (https://skillmd.com/u/coolsocket) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/coolsocket/t3d-grill-me --- 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: 1. **Which bounded context** does this feature belong to? (Look at `CONTEXT-MAP.md`.) 2. **Which aggregate root** owns the state change? Are we introducing a new aggregate? 3. **What invariants** must hold? List them — they'll go in `INVARIANTS.md` and each gets one failing test. 4. **What ubiquitous language terms** does this introduce? Are any of them already in `contexts//CONTEXT.md`? Are we redefining a term used in another context (that's fine — contexts have local languages)? 5. **Are there cross-context calls?** If yes, they MUST go through `contexts..application.api` (not internal domain imports). The PreToolUse hook will enforce this.