Ijfw Critique

Challenge decisions, surface counter-arguments, flag assumptions. Trigger: 'should I', 'is this right', 'critique', 'poke holes', 'second opinion', 'devil's advocate'. Auto-fired by ijfw-intent-router.

43 stars 17 forksOther

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add FerroxLabs/wayland-core --skill ijfw-critique
Manual install
git clone --depth 1 https://github.com/FerroxLabs/wayland-core.git /tmp/wayland-core
mkdir -p ~/.claude/skills
cp -r /tmp/wayland-core/crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-critique ~/.claude/skills/ijfw-critique

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

Before you agree, disagree. Before you advise, stress-test.

When the user asks you to critique, review a decision, or give a second
opinion -- or when the intent router flags critique intent -- follow this
pattern rather than answering from the same frame they asked from.

## Four-step critique

1. **Steelman first.** In one sentence, state the strongest version of the
   current plan / decision / design. Not to flatter -- to make sure you're
   critiquing the real thing, not a caricature.

2. **Surface the assumptions.** Name 2-3 assumptions the plan rests on.
   These are the load-bearing beliefs that, if wrong, collapse the argument.
   Be specific: "assumes traffic stays under 10k qps", not "assumes scale".

3. **Three concrete counter-arguments.** Each should be:
   - *Non-obvious* (if the user already considered it, skip)
   - *Bounded* (state when it applies; rarely are counter-arguments universal)
   - *Actionable* (each comes with a "watch for X" or "test by Y")

   Prefer counter-arguments that come from different angles: operational,
   social/organizational, economic, correctness. One bug-class concern is
   worth less than one operational + one social + one correctness concern.

4. **State your verdict briefly.** After laying out the counters, give a
   1-line recommendation: proceed / proceed with X mitigation / stop and
   rework because Y. Own the verdict -- don't just hedge.

## Refactor reframe (single-line trigger)
Read the full skill on GitHub

Details

Skill name
ijfw-critique
Path
crates/wayland-ijfw/snapshots/ijfw-source/claude/skills/ijfw-critique/SKILL.md
License
Apache-2.0
Repo updated
3 November 2026

FAQ

What does the Ijfw Critique skill do?

Challenge decisions, surface counter-arguments, flag assumptions. Trigger: 'should I', 'is this right', 'critique', 'poke holes', 'second opinion', 'devil's advocate'. Auto-fired by ijfw-intent-router.

How do I install the Ijfw Critique skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add FerroxLabs/wayland-core --skill ijfw-critique. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Ijfw Critique popular?

It lives in FerroxLabs/wayland-core, which has 43 GitHub stars and 17 forks.

Related skills

Browse the most popular Claude skills, all other skills, or write your own with the skills generator.