critique

Skeptical, VC-style evaluation of a project idea.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "critique" with this command: npx skills add taylorhuston/local-life-manager/taylorhuston-local-life-manager-critique

/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

  1. Invoke idea-critic Agent

Analysis areas:

  • Problem Validity - Is this a real problem? Evidence?

  • Market Opportunity - Size? Timing? Competition?

  • Solution Fit - Does solution address root cause?

  • Differentiation - Why will this win?

  • Business Model - Revenue? Unit economics?

  • Execution Risk - Team? Timeline? Resources?

  • Technical Feasibility - Can this be built?

  1. 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

daily-review

No summary provided by upstream source.

Repository SourceNeeds Review
General

daily-journal

No summary provided by upstream source.

Repository SourceNeeds Review
General

weekly-review

No summary provided by upstream source.

Repository SourceNeeds Review
General

life-planning

No summary provided by upstream source.

Repository SourceNeeds Review