bizanalysis

Category: Business & Operations | Uploader: pillip | Downloads: 0 | Version: v1.0（Latest）
Analyzes and critiques business viability. Use after /brainstorm and before /prd.
Changelog: Source: GitHub https://github.com/pillip/claude-dev-kit
Directory Structure

Current level: tree/main/skills/bizanalysis/
📄 SKILL.md 4.9 KB
📄 SKILL.md.tmpl 3.0 KB
SKILL.md

<!-- AUTO-GENERATED by scripts/gen_skills.py — DO NOT EDIT. Edit SKILL.md.tmpl instead. -->
---
name: bizanalysis
description: Analyzes and critiques business viability. Use after /brainstorm and before /prd.
argument-hint: [output file path, default docs/business_analysis.md]
disable-model-invocation: false
allowed-tools: Read, Glob, Grep, Write, Edit, WebSearch, WebFetch
---

## Kit Preamble — bizanalysis

### Kit Update Check
Run silently at the start:
```bash
python3 scripts/kit_update_check.py 2>/dev/null
```
If exit code is 1 (update available), show the output to the user once. Do not block the workflow.

### Project Context Detection
Run these checks silently at the start. Use results to adapt behavior:
- `[ -f issues.md ]` — if true, this project uses the sprint system. Respect issue numbering and STATUS.md.
- `[ -f docs/sprint_state.md ]` — if true and Status shows `running`, a sprint is active. Be aware of parallel work in worktrees.
- `[ -f docs/prd_digest.md ]` — if true, read it for quick project context before starting.

### Behavioral Rules
- Verify `gh auth status` before any GitHub operation.
- Never commit secrets, API keys, or credentials. Use environment variables.
- Prefer parallel Read/Glob/Grep tool calls when reading multiple independent files.
- When uncertain about intent, ask the user rather than guessing.
- Respect existing project conventions (package manager, test framework, code style).

### Contributor Mode
At the start of this skill, check if contributor mode is enabled:
```bash
python3 scripts/kit_config.py get contributor_mode
```
If the result is `true`:
1. At the end of each major workflow step, self-rate your experience with the kit 0–10.
2. If rating < 10 and there is an actionable improvement, file a field report:
   ```bash
   python3 scripts/contributor_report.py --skill <name> --step "<step>" --rating <N> --notes "<friction or suggestion>"
   ```
3. Maximum 3 reports per session. Skip if a report for the same step already exists.
4. Do NOT stop the workflow to file reports — do it inline.
5. Only report kit/skill issues (unclear instructions, missing checkpoints, bad ergonomics). Do NOT report user-app bugs or network errors.
Steps:
1) Determine the output path ($ARGUMENTS or `docs/business_analysis.md`).
2) Check if the file already exists at that path.
3) Check if `docs/brainstorm_notes.md` exists. If it does, read it and use as
   context — problem space, target users, chosen direction.

### If the file does NOT exist (New Analysis):
4a) If brainstorm notes exist, summarize the idea from them. Otherwise, ask the user to describe their idea.
5a) **Market Research**: Use WebSearch/WebFetch to investigate market size, trends, TAM/SAM/SOM. Cite sources.
6a) **Competitive Analysis**: Identify competitors and alternatives. Build a comparison table.
7a) **Business Model Exploration**: Explore revenue model candidates and pricing strategy directions.
8a) **Risk Assessment**: Identify key risks (market, technical, regulatory, competitive) and propose mitigations.
9a) **Critique**: Produce a SWOT analysis and a Go/Pivot/No-Go recommendation. Discuss with the user.

### If the file DOES exist (Continue Analysis):
4b) Read the existing analysis and present a brief recap.
5b) Ask the user which section they want to develop, challenge, or update.
6b) Repeat research and analysis as needed for the chosen area.
7b) Merge new insights into the existing analysis.

### Common (both modes):
10) Present the draft to the user and incorporate feedback.
11) Save the final analysis to the output path with five sections:
    - Executive Summary (one-line + Go/Pivot/No-Go)
    - Market Analysis (size, trends, TAM/SAM/SOM)
    - Competitive Landscape (comparison table, differentiation)
    - Business Model (revenue models, pricing direction)
    - Risks & Mitigations (risks, severity, mitigation strategies)
12) Inform the user they can run `/prd` next — business analysis and brainstorm notes will be automatically used as context.

## Error Handling
- If the output path is not writable: report the error and ask for an alternative path.

## Quality Criteria

**NEVER:**
- Fabricate market size numbers — back up with web research or label as "rough estimate"
- Unconditionally praise the user's idea — provide honest critique
- Ask more than 3 questions at a time — keep it conversational
- Jump to conclusions without analysis — show your reasoning

**INSTEAD:**
- Cite sources when presenting market data
- Present both strengths and weaknesses
- Use concrete numbers and comparisons
- Clearly state uncertainty when data is unavailable
- Propose actionable next steps for each risk

## Guidelines
- This is an interactive, conversational skill — engage naturally.
- If the user says "that's enough" or similar, produce the best analysis possible with available information.
- After saving, suggest next step: `/prd` to create a PRD using both business analysis and brainstorm notes as context.
Comments 0
Latest | Hot
Please login before commenting.
No comments yet. Be the first one!
bizanalysis

Directory Structure

SKILL.md

Report

Notice
