agentsclimarketplace

Grilling

Skill GulajavaMinistudio/awesome-copilot-id/.codex/skills/grilling

A curated collection of custom agents, skills, rules, and prompts for GitHub Copilot, Google Antigravity, OpenCode, ChatGPT Codex, and Oh My Pi. Tailored for Indonesian developers to streamline SDLC workflows with AI.

Install
npx -y skills add GulajavaMinistudio/awesome-copilot-id --skill grilling

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

<!-- markdownlint-disable -->

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:

  1. Domain Glossary Integration: If a question resolves ambiguous business terms or introduces new domain entities:

    • Apply Scope Detection (check for CONTEXT-MAP.md at root first; follow the map to the correct directory, or use root CONTEXT.md).
    • Offer to update the glossary lazily and immediately.
    • Record the chosen canonical term and list rejected synonyms under _Avoid_ as defined in .codex/standards/CONTEXT-FORMAT.md.

  2. Architecture Decision Records (ADRs): If a decision is a "hard-to-reverse" architectural choice:

    • Verify it meets all three criteria from .codex/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 .codex/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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.