Borrowing it
Nothing to install: this file belongs to reinhardhq/claude-code-spec-boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/reinhardhq/claude-code-spec-boilerplate/main/.claude/commands/biz:spec.mdgit clone --depth 1 https://github.com/reinhardhq/claude-code-spec-boilerplateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-spec)<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-spec"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-spec/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-spec"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.02308 |
| Opus 5 | $0.00015 | $0.01154 |
| Sonnet 5 | $0.00006 | $0.00462 |
| Haiku 4.5 | $0.00003 | $0.00231 |
Grade A, and why
biz:spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Specification Generator
アイデアの概要から包括的な事業仕様書を生成し、特定された弱点に基づいて最適な次のアクションを提案します。
入力: $IDEA_OUTLINE
Context Analysis
Existing Documents Check
- 既存仕様: !
[ -d .kiro/specs ] && find .kiro/specs -name "*.md" | head -5 || echo "No existing specs found" - 参考資料: !
[ -d .kiro/references ] && ls -la .kiro/references/ || echo "No reference materials"
Task: 事業仕様の生成と分析
1. アイデア分析と構造化
A. コアコンセプトの抽出
入力されたアイデアから以下を明確化：
- 価値提案: 何を解決するのか
- 独自性: 既存の解決策との差別化
- 実現可能性: 技術的・運用的な実現性
- スケーラビリティ: 成長可能性
B. ビジネスモデルキャンバスの作成
- 顧客セグメント: 具体的なペルソナ定義
- 価値提案: 顧客の課題と解決策
- チャネル: 顧客接点と流通経路
- 顧客関係: エンゲージメント戦略
- 収益モデル: マネタイズ方法
- 主要リソース: 必要な資源
- 主要活動: コア業務プロセス
- 主要パートナー: 協力関係
- コスト構造: 主要な費用項目
2. 詳細仕様の策定
A. ターゲット市場分析
- TAM (Total Addressable Market): 最大市場規模
- SAM (Serviceable Addressable Market): 獲得可能市場
- SOM (Serviceable Obtainable Market): 現実的な獲得市場
- 成長率: 市場の拡大予測
B. 競合分析と差別化
- 直接競合: 同じ課題を解決する既存サービス
- 間接競合: 代替となる解決方法
- 差別化要因: 独自の強み
- 参入障壁: 競合優位性の持続性
C. Go-to-Market戦略
- 初期獲得戦略: アーリーアダプター向け
- 成長戦略: メインストリーム展開
- チャネル戦略: 流通・販売経路
- 価格戦略: プライシングモデル
3. リスク評価と反証仮説
A. 事業リスクマトリクス
| リスクタイプ | 影響度 | 発生確率 | 対策優先度 |
|---|---|---|---|
| 市場リスク | 高/中/低 | 高/中/低 | A/B/C |
| 技術リスク | 高/中/低 | 高/中/低 | A/B/C |
| 競合リスク | 高/中/低 | 高/中/低 | A/B/C |
| 規制リスク | 高/中/低 | 高/中/低 | A/B/C |
B. 検証すべき仮説
- 顧客仮説: ターゲットは本当に存在するか
- 課題仮説: 課題は十分に深刻か
- 解決策仮説: 提案する解決策は有効か
- 収益仮説: 顧客は対価を支払うか
4. 成功指標とKPIの定義
A. フェーズ別KPI
-
検証フェーズ (0-3ヶ月)
- ユーザーインタビュー数
- プロトタイプテスト完了率
- 初期需要の確認
-
立ち上げフェーズ (3-12ヶ月)
- 月次アクティブユーザー数
- 顧客獲得コスト (CAC)
- 月次経常収益 (MRR)
-
成長フェーズ (12ヶ月以降)
- 年間経常収益 (ARR)
- 顧客生涯価値 (LTV)
- チャーンレート
5. 弱点分析と次のアクション
A. 仕様の完成度評価
各要素を5段階で評価し、弱点を特定：
- 顧客理解: ペルソナの具体性
- 課題定義: 問題の明確さ
- 解決策: 実現可能性と独自性
- 収益モデル: 持続可能性
- 市場戦略: 実行可能性
B. 動的な次ステップの提案
弱点に基づいて最適なアクションを推奨
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 190 lines · 30 tokens per session scan A c951f6d3afb6
biz:spec is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 30 tokens to every session and 2,308 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.