skills.rest
serbanghita
serbanghitaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan:critique

Critique markdown execution plans for feasibility, architecture, and standards.

13|1|Updated Jan 12, 2026
Search Tags:#automation#planning#architecture#quality assurance#code review#adversarial
One-click install
npx skills add https://github.com/serbanghita/claude-code-plan-critique --skill plan-critique-serbanghita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan:critique
Source: https://github.com/serbanghita/claude-code-plan-critique/tree/main/.gemini/skills/plan-critique
Command: npx skills add https://github.com/serbanghita/claude-code-plan-critique --skill plan-critique-serbanghita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of poorly defined execution plans by providing an adversarial, evidence-based critique that identifies architectural flaws, missing edge cases, and verification gaps before code is written.

Core Features & Use Cases

  • Adversarial Review: Systematically challenges plan assumptions to ensure only verified findings are reported.
  • Evidence-Based Feedback: Links every critique point to specific file lines, command outputs, or test failures.
  • Use Case: Before executing a complex refactor, use this skill to validate that your plan accounts for all dependencies, project standards, and potential breaking changes.

Quick Start

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

Frequently Asked Questions about plan:critique

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

FAQPage Schema
How do I validate a software execution plan before coding?▼

Adversarial plan review validates a software execution plan by systematically challenging assumptions to verify technical feasibility, architectural integrity, and project standards. It identifies risks and missing dependencies before code is written.

How does adversarial codebase inspection find missing edge cases in planning documents?▼

Adversarial codebase inspection finds missing edge cases by performing static analysis on markdown-based planning documents. It systematically challenges plan assumptions and links evidence-backed feedback to specific file lines and command outputs.

Does plan critique require specific language LSP plugins to work?▼

Yes, plan critique requires integration with IDE diagnostics and language-specific LSP plugins. These dependencies provide the actionable, evidence-backed feedback needed to verify technical feasibility during static analysis.

What is the best way to ensure architectural integrity during a complex refactor?▼

The best way to ensure architectural integrity during a complex refactor is using an evidence-based critique system. It verifies that your plan accounts for all dependencies, project standards, and potential breaking changes through static analysis.

What are the limitations of static analysis for execution plan review?▼

Static analysis for execution plan review relies on IDE diagnostics and language-specific LSP plugins. It is limited by its dependency on markdown-based planning documents and requires these specific environment integrations to provide actionable, evidence-backed feedback.

Related Skills

Explore More Software Engineering Skills→
luissimon96luissimon96

graph-bug-hunter

Automate bug discovery via static analysis, LSP diagnostics, and error catalog mining.

Community
Advanced
InverterNetworkInverterNetwork

test-driven-development

Enforce the Red-Green-Refactor cycle with failing tests before implementation.

Official
Advanced
starrank-softstarrank-soft

autoreview

Review local git repositories for bugs, security risks, and architectural inconsistencies.

Official
Advanced
hagajihagaji

kensho

Verify proposals, plans, and artifacts for alignment with intent.

Community
Basic