goat-critique

Name: goat-critique
Availability: InStock
Author: blundergoat

Critique technical artifacts using three specialized sub-agents against a defined rubric.

Updated Feb 19, 2026

Search Tags:#architecture #quality assurance #analysis #review #risk assessment #critique

Ready to run

npx skills add https://github.com/blundergoat/ambient-scribe --skill goat-critique

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: goat-critique
Source: https://github.com/blundergoat/ambient-scribe/tree/main/.agents/skills/goat-critique
Command: npx skills add https://github.com/blundergoat/ambient-scribe --skill goat-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents shipping errors and oversight by forcing a rigorous, multi-perspective critique of your work before it is finalized.

Core Features & Use Cases

Multi-Lens Analysis: Simultaneously applies SKEPTIC, ANALYST, and STRATEGIST perspectives to your artifacts.
Isolated Verification: Uses independent sub-agents to ensure findings are objective and free from context-leak bias.
Use Case: Before deploying a new architecture proposal or a complex refactor, use this Skill to identify hidden risks, unstated assumptions, and alternative implementation paths that you might have missed.

Quick Start

Invoke the goat-critique skill on your current architecture document to perform a full multi-perspective review.

Frequently Asked Questions about goat-critique

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

FAQPage Schema

How do I perform a multi-perspective architecture review before deployment?▼

A multi-perspective architecture review applies skeptic, analyst, and strategist viewpoints to your technical artifacts. This process uses isolated sub-agents to cross-examine findings, identifying hidden risks and alternative implementation paths before finalization.

What is multi-lens critique for technical artifact risk assessment?▼

Multi-lens critique for risk assessment orchestrates specialized sub-agents to verify findings against a defined rubric. It surfaces blind spots by ensuring objective, cross-examined assessments of architecture proposals and project plans.

Can I use this to review security assessments and debug hypotheses?▼

Yes, you can use this critique process to review security assessments and debug hypotheses. The multi-perspective approach applies a defined rubric to verify findings and cross-examine conflicting assessments across various technical artifacts.

How do I identify blind spots in a complex project plan?▼

To identify blind spots in a project plan, apply a multi-lens critique using independent sub-agents. This isolated verification prevents context-leak bias and cross-examines conflicting assessments to surface unstated assumptions and hidden risks.

Does the critique process support isolated verification to prevent context-leak bias?▼

Yes, the critique process supports isolated verification by using independent sub-agents. This architecture ensures findings remain objective and free from context-leak bias during the cross-examination of technical artifacts.

When should I not use an automated multi-perspective critique for quality assurance?▼

You should not use automated multi-perspective critique when your technical artifact lacks sufficient detail for a defined rubric evaluation. The process requires comprehensive architecture proposals or project plans to effectively cross-examine conflicting assessments.