forger-grill

Review engineering proposals through cross-model adversarial analysis and generate failure hypothesis reports.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/RyanDev1st/FORGER --skill forger-grill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forger-grill
Source: https://github.com/RyanDev1st/FORGER/tree/main/skills/forger/phases/grill
Command: npx skills add https://github.com/RyanDev1st/FORGER --skill forger-grill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents the deployment of flawed engineering proposals by subjecting them to rigorous, cross-model adversarial review before any implementation budget is spent.

Core Features & Use Cases

  • Cross-Model Adversarial Review: Invokes a reviewer from a different model family to identify failure modes, blind spots, and logical inconsistencies in your proposal.
  • Deep-Mode Blind Review: Optionally runs a blind reviewer that evaluates the Definition of Works without seeing the proposal, ensuring architectural assumptions are sound.
  • Resolution Loop: Forces the executor to either add tests, provide counter-evidence, or escalate concerns, ensuring no high-severity risks remain unaddressed.

Quick Start

Run the forger-grill skill on the current workspace to perform an adversarial audit and generate a failure hypothesis report.

Frequently Asked Questions about forger-grill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is cross-model adversarial review for engineering proposals?

Cross-model adversarial review validates engineering proposals by invoking a reviewer from a different model family to identify failure modes and logical inconsistencies before implementation budget is spent.

How do I validate architectural assumptions before starting high-stakes development?

You validate architectural assumptions by running a deep-mode blind review, where a reviewer evaluates the Definition of Works without seeing the proposal, ensuring foundational design soundness before implementation begins.

Does this adversarial review pipeline require multi-model consensus to pass proposals?

Yes, the pipeline enforces multi-model consensus through a resolution loop that forces the executor to add tests, provide counter-evidence, or escalate concerns, ensuring no high-severity risks remain unaddressed.

Can I use deterministic gate-keeping for engineering risk mitigation?

Yes, the pipeline satisfies requirements for deterministic gate-keeping by applying evidence-based resolution of failure modes, ensuring architectural assumptions are rigorously validated before any development pipeline proceeds.

What is the best way to identify failure hypotheses in a software engineering pipeline?

The best way to identify failure hypotheses is performing an adversarial audit on the current workspace, generating a comprehensive failure hypothesis report that highlights blind spots and logical inconsistencies in your proposal.