why

Reviews and pressure-tests the assistant's immediately prior recommendation on explicit /why invocation.

Updated Aug 30, 2026
One-click install
npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill why-ryanportfolio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: why
Source: https://github.com/ryanportfolio/threejs-interview-test/tree/main/.claude/skills/why
Command: npx skills add https://github.com/ryanportfolio/threejs-interview-test --skill why-ryanportfolio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI assistant recommends a library, approach, or tradeoff, it tends to rubber-stamp its own reasoning on follow-up. This Skill provides a structured self-review of the immediately preceding recommendation, surfacing unstated assumptions, hidden costs, and conditions where the pick is wrong. ## Core Features & Use Cases - Scoped Recommendation Review: Locks onto the assistant's prior turn (or a user-specified pick) and restates it in one line before critiquing. - Fact Grounding: Verifies checkable repo facts and project constraints (naming policies, manual deploy steps, i18n requirements) before defending the pick. - Fresh-Eyes Subagent: Dispatches a single independent subagent with minimal context to find blind spots the self-review cannot see. - Use Case: After the assistant suggests using Wouter over React Router, the user types /why and receives a concise review covering why it matters, the real reasoning, honest gaps, alternatives, and a calibrated bottom line. ## Quick Start Type /why immediately after receiving a recommendation to get an honest pressure-test of that pick.

Frequently Asked Questions about why

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

FAQPage Schema
How do I get an AI assistant to critique its own recommendation?▼

Invoke the /why command immediately after the assistant makes a recommendation. It restates the pick, explains the real reasoning, surfaces hidden costs and edge cases, and gives a calibrated bottom line on whether the call still holds.

What does the /why command review?▼

It reviews the assistant's message directly before the /why invocation by default. You can pass an argument like "/why the caching approach" to scope it to a specific pick, including one from an earlier turn.

Does /why trigger on ordinary questions containing the word why?▼

No. The skill runs only on the explicit /why command. Normal conversational uses of the word "why" never trigger it, and it will not invent a recommendation to review if none exists.

How does /why avoid the assistant rubber-stamping its own pick?▼

It dispatches one fresh subagent with no memory of the session, fed only the recommendation under review. The subagent flags unstated assumptions and edge cases, and the assistant integrates those findings into the final review.

When should I use /why versus a full impartial review?▼

Use /why for a fast, lightweight check of a single recommendation. It deliberately avoids multi-agent panels and broad audits; those belong to a separate /impartial-review style skill for deeper evaluation.