An adversarial interview session to pressure-test project plans before implementation.
Install
mkdir -p .claude/skills/grill && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18181" && unzip -o skill.zip -d .claude/skills/grill && rm skill.zipInstalls to .claude/skills/grill
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Adversarial grilling session that stress-tests a plan against xcale's domain model before you build. Interviews you one question at a time, challenges your terms against CONTEXT.md, invents edge-case scenarios, cross-references the actual code for contradictions, and updates CONTEXT.md inline as terms get resolved. Use when the user wants to pressure-test an idea, sharpen a fuzzy plan, align before a feature, or says "grill me". Runs in front of /feature-design.Key capabilities
- →Interview the user about a plan one question at a time
- →Challenge user terms against CONTEXT.md
- →Invent edge-case scenarios to stress-test relationships
- →Cross-reference user statements with actual code for contradictions
- →Update CONTEXT.md inline as terms are resolved
- →Offer to record hard-to-reverse decisions via the /adr skill
How it works
The skill conducts an adversarial grilling session, interviewing the user about a plan, challenging terms against project documentation, inventing edge cases, and cross-referencing code to achieve shared understanding before development.
Inputs & outputs
When to use grill
- →Pressure-testing new feature ideas
- →Sharpening project plans
- →Aligning on domain terms
About grill
Interrogates the user one question at a time against project documentation. It aims to surface contradictions and refine plans before coding starts.
Adversarial grilling session that stress-tests a plan against xcale's domain model before you build. Interviews you one question at a time, challenges your terms against CONTEXT.md, invents edge-case scenarios, cross-references the actual code for contradictions, and updates CONTEXT.md inline as ter
When not to use it
- →When the user wants to proceed directly to feature design or implementation
- →When the user is not interested in pressure-testing an idea
- →When the user does not want to align on domain terms
Limitations
- →It requires existing project documentation like CONTEXT.md and ADRs
- →It focuses on aligning understanding before any design doc or code
- →It updates CONTEXT.md inline, not batching changes
How it compares
This skill actively interrogates and challenges a plan against existing documentation and code, resolving ambiguities and contradictions in real-time, unlike a passive review process.
Compared to similar skills
grill side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| grill (this skill) | 0 | 4mo | No flags | Advanced |
| create-plan | 36 | 10mo | Review | Beginner |
| project-planner | 32 | 1y | Review | Intermediate |
| system-design | 19 | 11mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).
sparc-methodology
ruvnet
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration
spec-workflow
TencentCloudBase
Standard software engineering workflow for requirement analysis, technical design, and task planning. Use this skill when developing new features, complex architecture designs, multi-module integrations, or projects involving database/UI design.