critique

Critique software development plans against project standards and LSP diagnostics.

13|1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/serbanghita/claude-code-plan-critique --skill critique-serbanghita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critique
Source: https://github.com/serbanghita/claude-code-plan-critique/tree/main/skills/critique
Command: npx skills add https://github.com/serbanghita/claude-code-plan-critique --skill critique-serbanghita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the lack of rigorous validation in development plans by providing an adversarial critique process that identifies architectural flaws, missing edge cases, and unverified assumptions before code is written.

Core Features & Use Cases

  • Adversarial Review: Systematically challenges plan assumptions to ensure only verified findings are reported.
  • Confidence Grading: Distinguishes between confirmed issues verified against the codebase and unverified observations.
  • Use Case: Before implementing a complex database refactor, use this skill to critique your plan against existing project standards and LSP diagnostics to prevent breaking changes.

Quick Start

Run the critique skill to review the current plan in your active session and generate a critique report.

Frequently Asked Questions about critique

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

FAQPage Schema
How do I validate a software development plan before writing code?

To validate a development plan, you can run an adversarial critique process that analyzes project structure, standards, and code logic against defined execution steps to identify architectural flaws before implementation.

What is adversarial plan review in software architecture?

Adversarial plan review is a validation technique that systematically challenges plan assumptions and cross-references IDE diagnostics to ensure only verified findings against the codebase are reported.

How do I find missing edge cases in a database refactor plan?

To find missing edge cases in a database refactor plan, apply an adversarial critique process that distinguishes between confirmed codebase issues and unverified observations to prevent breaking changes.

Do I need LSP tools to critique architectural changes?

Yes, critiquing architectural changes requires integration with LSP tools and IDE diagnostics to verify file paths, type definitions, and method references within your project structure.

Can I use code review techniques for high-confidence execution validation?

Yes, applying code review logic to execution plans provides confidence grading that validates architectural changes and implementation details before the actual development workflow begins.