agentmods.dev

claude-code-spec-boilerplate: Command for Claude Code

.claude/commands/biz:validate.md

biz:validate is a command for Claude Code from reinhardhq/claude-code-spec-boilerplate. It costs 19 tokens per session (1,285 once invoked), scanned A, original, MIT.

A business-validation command that creates a plan for testing a customer problem and a proposed solution.

In plain words
What is it for?
Use it to plan an MVP, recruit early users, collect feedback, measure adoption or continued use, and decide whether to improve, continue, or change the idea.
Why use it?
It helps replace assumptions with evidence from prototypes, landing pages, interviews, or manually delivered services. It defines what to measure, how long to test, and what risks to examine.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is reinhardhq/claude-code-spec-boilerplate's own configuration. It tells Claude Code how to work on claude-code-spec-boilerplate itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-spec-boilerplate configures →

not rated 2repo 1y ago A scan 19 tokens original MIT
View source ↗ reinhardhq/claude-code-spec-boilerplate
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/reinhardhq/claude-code-spec-boilerplate/main/.claude/commands/biz:validate.md
Clone the repo
git clone --depth 1 https://github.com/reinhardhq/claude-code-spec-boilerplate

Made for: Claude Code.

Wrote 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.

agentmods badge for biz:validate

README.md
[![agentmods](https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-validate/github.svg)](https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-validate)
Your own site
<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-validate"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-validate/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.

agentmods 80×15 button for biz:validate

Your own site · 80×15
<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-validate"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,285 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.01285
Opus 5.5 $0.00008 $0.00514
Sonnet 5.5 $0.00004 $0.00257
Haiku 4.5 $0.00002 $0.00128

Measured 2mo ago against content hash cd7aab1ba83f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

biz:validate 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 2mo 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.

.claude/commands/biz:validate.md · 124 lines

What it actually says

Business Validation Plan

ユーザーの課題と解決策に基づいて、実行可能な検証プランを作成します。

入力情報:

  • ユーザーの課題: $USER_PAIN
  • 提案する解決策: $SOLUTION

Task: 検証プランの作成

1. 課題と解決策の分析

提供された情報から以下を抽出・分析：

  • 課題の本質的な要因
  • 解決策の核となる価値提案
  • 仮説となる前提条件
  • 検証すべきリスク要因

2. 検証方法の設計

A. MVPアプローチの選定

以下から最適な検証方法を選択：

  • コンシェルジュMVP: 手動でサービスを提供し価値を検証
  • ランディングページMVP: 需要を事前に測定
  • プロトタイプMVP: 最小限の機能で体験を提供
  • ウィザード・オブ・オズMVP: 自動化を装った手動運用
B. 検証ステップの詳細化

  1. 準備フェーズ (1-2週間)

    • 必要なリソースの準備
    • 検証環境の構築
    • 初期ユーザーの募集

  2. 実行フェーズ (2-4週間)

    • データ収集方法
    • ユーザーインタビュー計画
    • 反復改善のサイクル

  3. 評価フェーズ (1週間)

    • データ分析手法
    • 意思決定基準

3. 成功指標の定義

定量的指標
  • 採用率: 目標 X%以上
  • 継続率: Y日後の継続利用率 Z%以上
  • NPS: 推奨度スコア A以上
  • 変換率: 特定アクションの達成率 B%以上
定性的指標
  • ユーザーフィードバックの分析軸
  • 行動観察から得る洞察
  • 期待と実際のギャップ分析

4. リスクと対策

主要リスク
  1. 市場リスク: 需要が想定より小さい
    • 対策: 早期の需要検証、ピボット準備
  2. 技術リスク: 実現可能性の課題
    • 対策: 技術的実証実験の優先実施
  3. 競合リスク: 既存/新規参入者の脅威
    • 対策: 差別化要素の明確化と保護

5. 検証プランの出力

✅ 検証プラン

課題と解決策

  • 課題: $USER_PAIN
  • 解決案: $SOLUTION

検証方法

  • MVPタイプ: [選定したMVPアプローチ]
  • 検証期間: [具体的な期間]
  • 対象ユーザー: [具体的なセグメント]

成功指標

定量的:

  • [具体的な数値目標1]
  • [具体的な数値目標2]
  • [具体的な数値目標3]

定性的:

  • [評価軸1]
  • [評価軸2]

実行ステップ

  1. Week 1-2: [準備内容]
  2. Week 3-6: [実行内容]
  3. Week 7: [評価内容]

リスクと対策

  • 最大リスク: [内容] → 対策: [具体的アクション]
  • 技術的課題: [内容] → 対策: [具体的アクション]

🔍 次のステップ

検証プランの承認後：

  1. タスク分解: /biz-tasklist stage=PoC spec="[検証プランの要約]"
  2. レビュー取得: /biz-review context=validation_plan perspective=PM previous="[本出力]"
  3. 実装開始: 承認されたタスクから着手

📍 現在の進捗

[ アイデア ] → [ 仕様 ] → [ 検証計画 ✅ ] → [ タスク分解 ⏳ ] → [ 実装 ] → [ 評価 ]

Instructions

  1. 入力を深く分析 - 表面的な課題から本質的な問題を抽出
  2. 実行可能な計画 - 具体的で測定可能な検証方法を設計
  3. リスク重視 - 早期に失敗を発見できる設計
  4. 段階的アプローチ - 最小限のリソースで最大の学習
  5. 明確な判断基準 - Go/No-Goの意思決定を可能に

この検証プランにより、最小限のリソースで最大限の学習を得られる構造化されたアプローチを提供します。

Changes

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.

  1. 2mo ago First seen · 124 lines · 19 tokens per session scan A cd7aab1ba83f

Subscribe to this mod's changes

biz:validate is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 19 tokens to every session and 1,285 once invoked, about $0.0001 per session on Opus 5.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.

Planning
Related

biz:validate compared with commands from other repositories

biz:validate next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
biz:validatereinhardhq/claude-code-spec-boilerplateCommand21y agoMITA19Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code