Skip to main content
skill CX Codex

critique-plan — Claude Code skill for plan reviews

The critique-plan Claude Code skill challenges strategic plans, architectural decisions, and proposals before approval. It surfaces counterarguments, hidden assumptions, and alternatives.

MIT ★ 26 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add wrg32786/aigent-os --skill critique-plan -a claude-code
Open on GitHub

What critique-plan does

The skill examines a plan before a decision is made. It searches vault/ for related notes and earlier decisions, then identifies the strongest objection, unstated assumptions, and alternatives the proposal leaves out. Its available tools are Read, Grep, Glob, and WebFetch.

The review follows a structured format with confidence labels, conditions that could address each weakness, and changes that would strengthen the plan. The strongest counterargument comes first. The skill is read-only; it cannot use Write, Edit, or Bash.

What it helps with

  • find the strongest objection to a strategic plan
  • surface assumptions behind an architectural decision
  • compare a proposal with alternatives it overlooks
  • state what would resolve a plan’s main weakness

Example prompts for the agent

  • Critique this plan and lead with the strongest counterargument.
  • Challenge this architectural decision before we commit to it.
  • What assumptions are we missing, and what alternatives should we consider?

How to install critique-plan

1Skills CLI (Vercel)

npx skills add wrg32786/aigent-os --skill critique-plan -a claude-code

2Manually: put the files in place

~/.claude/skills/critique-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/critique-plan/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about critique-plan

How do I install critique-plan in Claude Code?

Run npx skills add wrg32786/aigent-os --skill critique-plan -a claude-code, then open ~/.claude/skills/critique-plan/SKILL.md.

What does critique-plan do?

It reviews plans, proposals, and architectural choices before commitment. The skill leads with the strongest counterargument, identifies hidden assumptions, and lists alternatives with confidence labels.

Can critique-plan change project files?

No. It is restricted to read-only work and can use Read, Grep, Glob, and WebFetch. Write, Edit, and Bash are unavailable.

Source text

SKILL.md · MIT
---
name: critique-plan
agent: hypatia
description: "Critique plans with counterarguments, hidden assumptions, and alternatives. Use when challenging a strategic plan, architectural decision, or proposal before commitment."
allowed-tools: Read, Grep, Glob, WebFetch
user-invocable: true
triggers:
  - critique this plan
  - critique plan
  - challenge this
  - adversarial review
  - pre-decision review
  - what am I missing
  - poke holes in this
  - steelman the opposition
  - review before committing
  - what could go wrong
---

# Critique Plan

You are Hypatia performing pre-commitment adversarial review. You find the fatal flaw before it becomes a sunk cost. Read-only.

## What this skill does

Challenge a plan, proposal, or architectural decision before it hardens into commitment. Name the strongest counterargument first. Surface hidden assumptions. Name alternatives not considered. State what would need to be true to overcome each weakness. Confidence-labeled throughout.

## Protocol

### Step 1: Read before critiquing

Pull relevant vault notes and prior decisions on this topic before forming any position. Critique from evidence, not intuition.

Grep `vault/` for:
- Prior decisions on this topic
- Related plans or strategies that succeeded or failed
- Any commitments that would be affected

### Step 2: Formulate the strongest counterargument

This goes first. If there is a fatal flaw, it goes at the top. Do not bury it.

### Step 3: Surface hidden assumptions

The dangerous assumptions are the ones no one listed. Name them explicitly. Ask: "What would have to be true for this plan to work?" Then check whether those things are actually true.

### Step 4: Name alternatives not considered

What else could solve this problem? What's the simplest version that achieves the core goal? What would a skeptic propose instead?

### Step 5: Return structured critique

```
## Critique: <plan name>

### Strongest counterargument (HIGH confidence)
<The main reason this plan could fail. Direct. No hedging.>
**What would need to be true to overcome it:** <specific condition>

### Hidden assumptions
- <Assumption 1> — **Confidence this is actually true:** High / Medium / Low
- <Assumption 2> — ...

### Alternatives not considered
- <Alternative A> — <one sentence on why it wasn't considered and whether it should be>
- <Alternative B> — ...

### Secondary concerns (MEDIUM confidence)
- <Concern> — **What would need to be true:** <condition>

### Remote risks (LOW confidence)
- <Risk> — <why it's low confidence but worth flagging>

### What would make this plan stronger
<Constructive close — what changes would resolve the strongest counterargument>
```

## Constraints

- Read vault context before critiquing. Evidence-based only.
- Strongest counterargument goes first — never buried.
- Confidence labeled on every concern: High / Medium / Low.
- Constructive close is mandatory — Hypatia blocks nothing, she strengthens decisions.
- No Write, Edit, or Bash tools. Read-only always.

© wrg32786 · MIT · wrg32786/aigent-os

Similar skills

SKILL.md skills catalog →

From the same set58

The whole set →
digest The digest Claude Code skill reviews staged entries in MEMORY_CANDIDATES.md. It presents choices for each one: promote it, skip it, or replace an existing entry. CX Codex +1 ★ 26repo stars Diagnose Diagnose — a Claude Code skill that traces faults across aigent-OS components and settings. It investigates broken hooks, skill routing failures, and unexpected changes in agent behavior. CX Codex +1 ★ 26repo stars deep-recon The deep-recon Claude Code skill coordinates several agents to investigate a topic and create a structured recon document. It can draw on notes and web sources, with interactive or autonomous rounds. CX Codex +1 ★ 26repo stars decide This Claude Code skill weighs a decision against selected criteria and returns a structured recommendation. Run /decide to compare options or ask for help choosing a course of action. CX Codex +1 ★ 26repo stars context-hygiene This Claude Code skill archives old session log entries and trims active priorities. Run /context-hygiene to clean the context files. CX Codex +1 ★ 26repo stars context-capsule The context-capsule Claude Code skill saves the current project state in a capsule for later work. Run it to checkpoint before risky changes, mark a completed milestone, or hand work to another session. CX Codex +1 ★ 26repo stars compact-note The compact-note Claude Code skill condenses long notes and logs while keeping the reasoning behind decisions. It runs on requests to shorten a note, log, or memory. CX Codex +1 ★ 26repo stars comms-summarize The comms-summarize Claude Code skill summarizes unread messages from an inbox, channel, or thread. It flags items that need action and separates them from FYI and stale messages. CX Codex +1 ★ 26repo stars

Project sponsors

Companies that keep this analytics open