grill me

Engineering Community

Skill notes

Goal

Reach a shared, unambiguous understanding of what the user wants to build before any implementation begins. Success = a concrete implementation plan the user has approved, with all blocking decisions resolved.

Dependencies

Tools: Read, Grep, Glob (read-only — this skill gathers information, never modifies files) No external services or MCP servers required

Context

This skill reads the existing project (CLAUDE.md, README, config files) to pre-fill known answers before asking any questions. The less the user has to repeat themselves, the better. Reference reference/02-best-practices.md if uncertain about Claude Code patterns. Interview the user about their plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one.

Full Mode (default): /grill-me [topic]

Relentless, thorough interview. Explores every branch of the design tree until zero ambiguity remains. Use for complex features, architecture decisions, or anything where getting it wrong is expensive.

Light Mode: /grill-me lightly [topic]

Quick, focused interview — 5-8 questions max. Gets the essential decisions made without deep-diving every branch. Use for quick setups, small features, or when the user just needs to fill in a few gaps. Skip edge cases and failure modes unless they're critical. Aim for "good enough to start" not "perfectly specified."

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@reedmayhew18 · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Big Picture

What is the user trying to build? Who is it for? What does success look like?

02
Phase 2: Design Tree

For each major component: What are the options? What are the tradeoffs? Which option fits the constraints? What does this decision imply for other decisions?

03
Phase 3: Edge Cases & Failure Modes

What happens when things go wrong? What are the performance constraints? What are the security considerations? What data validation is needed?

04
Phase 4: Synthesis

After all questions are answered: Summarize all decisions made Highlight any tensions or tradeoffs Propose a concrete implementation plan Ask if anything was missed

05
Phase 1: Quick Context

What are you building? (one sentence) What's the most important thing it needs to do? Any hard constraints? (tech stack, timeline, platform)

06
Phase 2: Key Decisions Only

Ask about the 3-5 biggest decisions that would block progress Skip theoretical edge cases — focus on "what do I need to know to start building?"

07
Phase 3: Quick Summary

Summarize decisions in bullet points Note anything deferred for later Recommend next step (usually `/wizard` or `/plan-and-spec`) CHECKPOINT: Present the summary to the user before recommending next steps. Ask: "Does this look right? Ready to move forward, or anything to adjust?"

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.