business-case-analyzer

Files (1)

• SKILL.md

SKILL.md (first lines)

# Business Case Analyzer

Use this skill when the user has a business idea, product concept, startup
thesis, feature set, or commercial opportunity they want expanded,
pressure-tested, and shaped into a buildable direction.

This is an early-stage skill.
It fits best inside:
- `Opportunity framing`
- `Solution shaping`

It is not the core operating model.
It plugs into `llm-os` and should write its outcomes back into the canonical
project docs.

## Output modes

Choose one output mode before writing back.

### `Status-surface`
Use when:
- there is no repo yet
- the user wants comments and feedback before build
- the concept is still being shaped in `Opportunity framing` or `Solution shaping`

Write to one canonical status surface. That surface may be Notion, Confluence,
markdown, a tracker record, or another durable workspace. Do not treat the tool
choice as the operating model.

Minimum top block:
- `Status`
- `Stage`
- `Freshness`
- `Last reviewed`
- `Next decision`
- `Owner`
- `Canonical repo`
- `Execution surface`

Recommended sections:
1. `Summary`
2. `What this is`
3. `Who can pay`
4. `Value delivered`
5. `Market and alternatives`
6. `Key assumptions`
7. `Key risks`
8. `Current recommendation`
9. `Next decision`
10. `Next action`

Prefer updating the same surface over creating a new page or document for every
iteration.

If the chosen status-surface tool is unavailable, produce structured markdown so
it can be pasted into the canonical concept surface.

### `Repo-writeback`
Use when:
- a repo exists
- the project has a bounded first milestone
- active build is starting or already underway

Write to the repo's live project-doc surface and keep the external status
surface as summary, review, comment, run-dispatch, and human-decision support
rather than a second execution surface.

## Read path

Use the repo's live project-doc surface.
The default layout is `docs/`, but follow any repo-local override declared in
`AGENTS.md`.

Read only the smallest sufficient context:
1. `project-spine.md` on the live project-doc surface if it exists
2. `current-milestone.md` on the live project-doc surface if it exists
3. `open-questions.md` on the live project-doc surface only if needed
4. `session-brief.md` on the live project-doc surface only if needed

If the repo is not yet initialized:
- use the user's prompt as the working source
- prefer `Status-surface` output mode
- switch to `Repo-writeback` once the repo exists

## Goal

Turn a short business description into:
1. a sharper opportunity view
2. a clearer system and go-to-market shape
3. a bounded next milestone that can actually be executed

Do not stop at brainstorm prose.
The output should improve project clarity and reduce ambiguity.

## Phase 1 — Opportunity framing

Trigger:
- a short business idea
- a product concept
- a startup thesis
- a request to analyze whether an idea is worth building

Do:
- identify who can pay
- identify what value is delivered and what cost of inaction exists
- size the market roughly with reasoning
- identify competitors, substitutes, and structural constraints
- identify the distinct product components and which are differentiating
- identify the main commercial and execution risks
- make the load-bearing assumptions explicit

Questions at the end should be the smallest set that most changes the analysis.
Lead with synthesis first.

## Phase 2 — Solution shaping

Trigger:
- the user responds to Phase 1
- or says to go deeper

From armin-haghi/llm-os, MIT.

More from armin-haghi/llm-os