Critical Feedback FAQs

Question 1

When should I use this Claude Code skill?

Accepted Answer

Use this skill when you are in a decision-making phase, such as asking 'Should I use this library?' or 'Is this approach sound?' It is ideal for code architecture planning, PR reviews, and any scenario where you need an unbiased, blunt assessment of a technical proposal.

Question 2

Does this skill always disagree with the user?

Accepted Answer

No. The goal isn't constant disagreement, but rigorous assessment. If your idea is logically sound and backed by evidence, Claude will signal high confidence in its validity. It simply removes the tendency to agree just to be polite, ensuring that agreement is actually earned.

Question 3

What does the Critical Feedback skill do?

Accepted Answer

This skill transforms Claude from a standard assistant into a rigorous critical thinking partner. It allows Claude to evaluate your ideas, decisions, and proposals as hypotheses, providing honest, pressure-tested feedback that identifies blind spots and logical flaws without unnecessary hedging or false agreement.

Question 4

How does this skill improve my developer workflow?

Accepted Answer

It helps you avoid costly mistakes by catching reasoning errors early. By eliminating 'yes-man' behavior from the AI, you get a realistic view of your project's risks, allowing you to refine your strategy based on logic and evidence rather than just validation.

Question 5

What specific capabilities does it provide?

Accepted Answer

The skill provides structured feedback including claims and alternatives, calibrated confidence signaling (High, Moderate, or Low certainty), and a direct communication style. It uses specific patterns to identify why a claim might fail and proposes better alternatives when they exist.

Critical Feedback

Critical Feedback

Características Principales

Casos de Uso

Características Principales

Casos de Uso