business-review

name	Business Review
description	Pressure-test a business, product, offer, market, or operating problem and identify the next concrete move.
metadata	{"dependsOn":{"integrations":[],"skills":[]}}

Business Review

Use this skill to pressure-test and sharpen a business direction. The goal is better judgment, not a long memo.

This is not Business Idea Onboarding. Business Idea Onboarding creates or refreshes durable project context. Business Review interrogates a business question, exposes weak assumptions, and turns ambiguity into one concrete next move.

When to use

Use this skill when the user wants to:

• evaluate a new business, product, offer, or market
• decide what to do next
• pressure-test strategy, positioning, pricing, distribution, or operations
• understand why a plan feels weak or vague
• identify the narrowest useful proof
• choose between competing directions

Do not use this skill for routine execution after the goal is already clear. In that case, continue with the requested work or use a more specific skill.

Workflow

Step 1: Frame the question

Start by restating the business question in one or two sentences. Name the likely customer, current offer, and uncertain assumption if they are visible.

If the context is thin, ask one focused question before judging. If the next useful move is already clear, do not ask a question just to fill the format.

Step 2: Separate facts from assumptions

Distinguish:

• what the user knows from evidence
• what is inferred
• what is only a hope or preference
• what would change the recommendation if false

Preserve uncertainty. Do not convert a vague idea into fake confidence.

Step 3: Pressure-test the useful edge

Look for the smallest meaningful proof:

• who specifically has the problem
• what they do today instead
• why now is a good time to switch
• what makes the offer easier, cheaper, faster, safer, or more desirable
• what distribution path could reach the first buyers
• what operational constraint could break the plan

Ask at most one focused question per turn. The question should change the recommendation, not collect generic business-plan fields.

Step 4: End with one next move

End with a compact review and one recommended next action. Prefer actions you can help with immediately:

• define the first customer segment
• draft customer interviews
• write a landing-page pitch
• design a validation experiment
• compare pricing models
• identify the first operational bottleneck
• decide what not to build yet

Reference files

• open references/question-patterns.md for focused questions
• open references/review-modes.md for different review lenses
• open references/anti-patterns.md to avoid weak review behavior
• open templates/review-summary.md when writing a durable review note