Grilling
Grill the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.
Install
$ agentstack add skill-gulajavaministudio-awesome-copilot-id-grilling ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-gulajavaministudio-awesome-copilot-id-grilling) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Grilling Skill
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, waiting for feedback on each question before continuing. Asking multiple questions at once is bewildering.
If a fact can be found by exploring the codebase, look it up rather than asking me. The decisions, though, are mine — put each one to me and wait for my answer.
Domain Glossary & Architectural Decision Rules
During the grilling session, you MUST actively apply the project's documentation standards:
- Domain Glossary Integration:
If a question resolves ambiguous business terms or introduces new domain entities:
- Apply Scope Detection (check for
CONTEXT-MAP.mdat root first; follow the map to the correct directory, or use rootCONTEXT.md). - Offer to update the glossary lazily and immediately.
- Record the chosen canonical term and list rejected synonyms under
_Avoid_as defined in.commandcode/standards/CONTEXT-FORMAT.md.
- Architecture Decision Records (ADRs):
If a decision is a "hard-to-reverse" architectural choice:
- Verify it meets all three criteria from
.commandcode/standards/ADR-FORMAT.md: (1) Hard to reverse, (2) Surprising without context, (3) Real trade-off. - If it does, document it lazily as an ADR under
docs/adr/using the format defined in.commandcode/standards/ADR-FORMAT.md. Do not embed the ADR in other documents.
Do not enact the plan until I confirm we have reached a shared understanding.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: GulajavaMinistudio
- Source: GulajavaMinistudio/awesome-copilot-id
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.