Use when adding new error messages to React, or seeing "unknown error code" warnings.
npx skills add TaylorHuston/local-life-manager --skill "critique"
Install specific skill from multi-skill repository
# Description
Challenge idea assumptions with skeptical VC-style evaluation. Use when user requests critique, validation, or 'is this a good idea' assessment.
# SKILL.md
name: critique
description: "Challenge idea assumptions with skeptical VC-style evaluation. Use when user requests critique, validation, or 'is this a good idea' assessment."
model: claude-opus-4-5-20251101
allowed-tools: Read, Write, Edit, Glob, Grep
/critique
Skeptical, VC-style evaluation of a project idea.
Usage
/critique # Critique current project
/critique --project coordinatr # Specific project
/critique --focus market # Market validation focus
/critique --focus technical # Technical feasibility focus
/critique --focus business # Business model focus
Output Location
ideas/[project]/critiques/YYYY-MM-DD.md
Prerequisites
REQUIRED: project-brief.md must exist
ls ideas/{project}/project-brief.md
# If missing: "Run /brief first"
Execution Flow
1. Load Project Context
Read: ideas/{project}/project-brief.md
Read: ideas/{project}/competitive-analysis.md (if exists)
Read: ideas/{project}/README.md
Glob: resources/research/*.md
2. Invoke idea-critic Agent
Analysis areas:
1. Problem Validity - Is this a real problem? Evidence?
2. Market Opportunity - Size? Timing? Competition?
3. Solution Fit - Does solution address root cause?
4. Differentiation - Why will this win?
5. Business Model - Revenue? Unit economics?
6. Execution Risk - Team? Timeline? Resources?
7. Technical Feasibility - Can this be built?
3. Generate Critique Document
---
created: YYYY-MM-DD
verdict: strong | promising | needs_work | reconsider
confidence: high | medium | low
---
# Critique: [Project Name]
## Executive Summary
[Honest 1-2 paragraph assessment]
## Critical Concerns
### High Priority
1. **[Concern]**: [Why concerning]
- Evidence needed: [What would resolve]
### Medium Priority
1. **[Concern]**: [Why matters]
- Suggestion: [How to address]
### Strengths
1. **[Strength]**: [Why valuable]
## Analysis by Area
[Problem Validity, Market, Solution Fit, etc.]
## Hard Questions to Answer
1. [Tough question]
2. [Another challenge]
## Recommendations
### If You Proceed
- [De-risk action]
- [Research needed]
### If You Pivot
- [Alternative direction]
Focus Modes
--focus market
- Market size/dynamics
- Competition landscape
- Customer validation
- Timing and trends
--focus technical
- Technical feasibility
- Architecture complexity
- Skill requirements
--focus business
- Revenue model
- Pricing strategy
- Unit economics
- Go-to-market
When to Use
- After completing project brief
- Before significant time investment
- When seeking honest feedback
- Before presenting to others
Not for: Ideas still forming (use /brief), when needing encouragement
Workflow
/brief -> /critique -> /research -> /spec
# Supported AI Coding Agents
This skill is compatible with the SKILL.md standard and works with all major AI coding agents:
Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.