mandate-critic

Name: mandate-critic
Availability: InStock
Author: buchananwill

Critique design proposals by exposing failure modes and requiring concrete alternatives.

2|Updated Mar 17, 2026

Search Tags:#maintenance #complexity #proposal #risk #alternatives #design-review #critic

Ready to run

npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill mandate-critic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mandate-critic
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/mandate-critic
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill mandate-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically critique proposals to expose failure modes, hidden complexity, and maintenance burdens, reducing risk of over-engineered solutions.

Core Features & Use Cases

Defines clear rules of engagement for design critique and ensures criticism is actionable with concrete alternatives.
Applies across product design, software architecture, and process proposals to surface specific improvements and risk indicators.
Facilitates rapid iteration by anchoring feedback in specifics and quantifiable trade-offs.

Quick Start

Provide a structured critique of a given proposal, including concrete alternatives and risk quantification

Frequently Asked Questions about mandate-critic

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

FAQPage Schema

How do I critique a design proposal to expose hidden complexity and maintenance burdens?▼

To critique a design proposal effectively, you must identify failure modes and hidden complexity by grounding criticism in specifics, prompting concrete objections, and requiring actionable alternatives when rejecting the initial proposal.

What is the best way to run a design review that reduces the risk of over-engineered solutions?▼

A design review that reduces over-engineering risk defines clear rules of engagement, anchors feedback in quantifiable trade-offs, and forces reviewers to surface specific improvements and risk indicators rather than offering vague observations.

Can I apply design critique rules to both software architecture and workflow process proposals?▼

Yes, you can apply these design critique rules across product designs, software system architectures, and workflow process proposals to systematically expose failure modes and prompt concrete improvements.

How do I ensure my architecture critique provides concrete alternatives instead of just objections?▼

To ensure an architecture critique provides concrete alternatives, establish rules of engagement that require quantifiable trade-offs and mandate that every rejection of a proposal includes a specific, actionable replacement solution.

Why does my design feedback fail to facilitate rapid iteration during a proposal review?▼

Design feedback fails to facilitate rapid iteration when it lacks specifics, but anchoring criticism in quantifiable trade-offs and concrete alternatives ensures the team can immediately act on the identified maintenance burdens and risks.

When should I not use a structured critique approach for product design proposals?▼

You should not use a structured critique approach requiring concrete alternatives when early-stage ideation demands unrestricted brainstorming, as enforcing strict rules of engagement too early may stifle creative exploration before risks are fully quantified.