grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- License 许可
- MIT
- 所属仓库
- ASoudy/AGS
- 最近更新
- 2026-05-23
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- grill-me
- license
- MIT
- metadata
- { "voice": "Matt Pocock — relentless, one-at-a-time, explores-codebase-first", "version": "1.0.0", "derived_from": "https://github.com/mattpocock/skills/tree/main/skills/productivity/grill-me", "original_author": "Matt Pocock (@mattpocock)", "original_license": "MIT" }
- description
- Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
02 资源文件 6
- 参考文档references/companion_tooling.md3.2 KB
- 参考文档references/forcing_question_patterns.md6.6 KB
- 参考文档references/when_to_stop_grilling.md6.5 KB
- 脚本scripts/decision_tree_extractor.py4.6 KB
- 脚本scripts/grill_session_tracker.py8.3 KB
- 脚本scripts/question_generator.py5.4 KB
03 SKILL.md 正文
Grill Me
Derived from Matt Pocock's grill-me (MIT). Matt's interview discipline preserved verbatim. Additions: extraction + question + session tools + references + cs-* wrapper (see references/companion_tooling.md).
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.
Rules (preserved + amplified)
- One question per turn. Never bundle.
- Provide a recommended answer with each question. Defaulting to "what do you think?" is lazy.
- Explore the codebase before asking. If
grep/Readresolves it, do that first. Saves a turn. - Walk the tree depth-first. Finish a branch before opening another.
- Track dependencies. If decision B depends on decision A, ask A first.
Workflow
- User provides a plan or design (or path to one).
- Run
scripts/decision_tree_extractor.pyto extract branches. - Run
scripts/question_generator.pyto produce the question list with recommendations. - Start a session:
scripts/grill_session_tracker.py --action start. - Walk the tree, one question at a time, recording answers in the session.
- When all branches resolved: report "shared understanding reached" + the locked-in decisions.
Output Pattern
Per question turn:
Q[i]/[total]: [question]
Recommended answer: [your call + 1-sentence rationale]
(Or: I explored the codebase and found [evidence]. Confirm?)
Tooling
See references/companion_tooling.md. Tools: extractor + generator + tracker. Agent: cs-grill-master. Command: /cs:grill-me.
Version: 1.0.0 Derived: Matt Pocock (MIT) + this repo's wrapper
04 同仓库更多 Skills
web-typography
Select, pair, and implement typefaces for web projects. Use when the user mentions "font pairing", "which typeface", "line height", "responsive typography", "web font loading", "type hierarchy", "variable fonts", "FOUT/FOIT", or "typographic scale". Also trigger when choosing between system fonts and web fonts, optimizing font loading performance, or designing readable long-form content layouts. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.
ux-heuristics
Evaluate and improve interface usability using heuristic analysis. Use when the user mentions "usability audit", "UX review", "users are confused", "heuristic evaluation", "form usability", "navigation problems", "Nielsen heuristics", "cognitive walkthrough", or "usability testing". Also trigger when reviewing a design for usability issues, improving form completion rates, or evaluating information architecture and navigation. Covers Nielsens 10 heuristics, severity ratings, and information architecture. For visual design fixes, see refactoring-ui. For conversion-focused audits, see cro-methodology.
traction-eos
Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "Entrepreneurial Operating System", or "business operating system". Also trigger when a growing company needs meeting structure, goal-setting frameworks, or a systematic approach to solving recurring organizational issues. Covers the six EOS components: Vision, People, Data, Issues, Process, Traction. For team motivation design, see drive-motivation. For lean experimentation, see lean-startup.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "premium website", "portfolio site", "scroll animations", "Awwwards quality", "brand experience", "cinematic web design", "parallax storytelling", or "agency-quality site". Also trigger when building landing pages that need to impress, designing creative portfolios, or elevating a standard website to a memorable digital experience. Covers dramatic typography, purposeful motion, scroll-based composition, and performance-optimized animation. For foundational UI, see refactoring-ui. For type selection, see web-typography.
system-design
Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues. Use when the user mentions "system design", "scale this", "high availability", "rate limiter", "design a URL shortener", "system design interview", "capacity planning", or "distributed architecture". Also trigger when estimating infrastructure requirements, choosing between microservices and monoliths, or designing for millions of concurrent users. Covers common system designs and back-of-the-envelope estimation. For data fundamentals, see ddia-systems. For resilience, see release-it.
storybrand-messaging
Clarify brand messaging using narrative structure that positions the customer as hero. Use when the user mentions "brand message", "website copy", "elevator pitch", "one-liner", "messaging isnt resonating", "brand script", "StoryBrand framework", or "customer as hero". Also trigger when rewriting homepage copy, crafting email nurture sequences, or creating consistent messaging across sales collateral and marketing materials. Covers landing page copy, marketing collateral, and consistent communication. For memorable messaging, see made-to-stick. For product positioning, see obviously-awesome.