diagnose-business

어떤 스킬인가요?

Audit a business across strategy, customers, offer, growth, sales, finance, operations, and team capacity to identify the binding constraint and rank evidence-backed findings. Use when a founder asks what to fix first, why performance is weak, or where to focus. Do not use when the problem is already selected and only an implementation plan is needed.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

interface:
  display_name: "Diagnose Business"
  short_description: "Run a founder-ready Diagnose Business workflow"
  default_prompt: "Use $diagnose-business to help me with this business task."

---
name: diagnose-business
description: Audit a business across strategy, customers, offer, growth, sales, finance, operations, and team capacity to identify the binding constraint and rank evidence-backed findings. Use when a founder asks what to fix first, why performance is weak, or where to focus. Do not use when the problem is already selected and only an implementation plan is needed.
---

# Diagnose Business

Find the constraint whose improvement most changes the business outcome. Do not reward the domain
with the most available data.

## Set the audit

1. Read `.business/context.md`, `.business/metrics.md`, backlog, recent decisions, plans, and
   reviews.
2. Clarify the current objective, time horizon, survival constraints, and non-goals.
3. Choose quick or deep coverage based on stakes and available evidence.
4. Mark missing context rather than delaying the entire audit.

## Map the system

Inspect, where relevant:

- strategy and objective coherence;
- customer evidence and problem severity;
- offer, positioning, pricing, and proof;
- acquisition, activation, retention, referral, and expansion;
- sales stages, conversion, velocity, and concentration;
- revenue quality, margins, cash, runway, and downside;
- delivery capacity, bottlenecks, quality, and dependencies;
- founder load, team capacity, incentives, and critical-person risk;
- governance or professional-review triggers.

Trace relationships between symptoms. Falling sales, for example, may originate in customer
selection, offer quality, pipeline coverage, delivery reputation, or measurement.

## Rank findings

For each finding record:

- current-state evidence and date;
- expected impact;
- urgency and cost of delay;
- effort and reversibility;
- risk;
- confidence;
- dependencies;
- the smallest useful validation step.

Do not average scores into false precision. Use the dimensions to support judgment and explain the
ranking. Keep strategic opportunities separate from diagnosed defects.

With authorization, update `.business/backlog.md`. Preserve rejected or disproven findings with a
reason so they do not recur without new evidence.

## Output contract

### Objective and health

- Current objective, time horizon, and survival constraints.

### Facts

- Cross-domain evidence and observed symptoms.

### Assumptions

- Causal hypotheses, confidence, and falsification tests.

### Estimates

- Any calculated range, formula, unit, period, and sensitivity.

### Confidence

- Confidence by finding and the evidence ceiling for the audit.

### Ranked findings

- Impact, urgency, effort, risk, confidence, and owner skill.

### Recommended focus

- The binding constraint, why it outranks alternatives, and the next focused skill.

### Not enough evidence

- Material unknowns and the fastest way to resolve them.

Do not execute selected recommendations. Route them to a focused skill, `decide-business`, or
`plan-business` after the user chooses the finding.