A guided discussion command for testing an idea or specification from a chosen viewpoint, such as an engineer, investor, designer, or customer, and in a chosen tone.

It is for reviewing product ideas, technical designs, business proposals, user experience, legal concerns, sales plans, and customer value through role-based questions and feedback.

It helps expose assumptions, risks, weak points, and possible improvements that one person might miss.

How reinhardhq/claude-code-spec-boilerplate configures Claude Code

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:wall.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-wall/github.svg)](https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-wall)

Your own site

<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-wall"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-wall/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/reinhardhq/claude-code-spec-boilerplate/biz-wall"><img src="https://agentmods.dev/badge/commands/reinhardhq/claude-code-spec-boilerplate/biz-wall.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,690 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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.02690
Opus 5.5	$0.00011	$0.01076
Sonnet 5.5	$0.00006	$0.00538
Haiku 4.5	$0.00003	$0.00269

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

Security

Grade A, and why

biz:wall 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:wall.md · 263 lines

How it starts

The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Wall Discussion Facilitator

アイデアや仕様に対して、指定された役割（PM、投資家、エンジニア等）と対話トーン（批判的、友好的、建設的）で壁打ちを行い、改善点を明確にします。

入力パラメータ:

対象内容: $TARGET
役割: $ROLE (PM/投資家/エンジニア/デザイナー/法務/営業/顧客)
トーン: $TONE (critical/friendly/constructive)

Task: 壁打ちセッションの実施

1. 役割とトーンの設定

A. 役割別の特性

PM (プロダクトマネージャー)

関心: ユーザー価値、市場適合性、優先順位
評価軸: 実現可能性、インパクト、リソース効率
質問スタイル: Why/What/How

投資家

関心: ROI、成長性、リスク
評価軸: 市場規模、収益性、競合優位性
質問スタイル: 数字とエビデンス重視

エンジニア

関心: 技術的実現性、アーキテクチャ、保守性
評価軸: 複雑性、スケーラビリティ、技術負債
質問スタイル: 実装詳細と edge case

デザイナー

関心: UX、ビジュアル、一貫性
評価軸: 使いやすさ、美しさ、ブランド適合
質問スタイル: ユーザー中心の問い

法務

関心: コンプライアンス、リスク、契約
評価軸: 法的適合性、責任範囲、知財
質問スタイル: リスクシナリオ

営業

関心: 販売可能性、顧客ニーズ、競合
評価軸: 差別化、価格設定、販売サイクル
質問スタイル: 顧客の声と市場実態

顧客

関心: 価値、使いやすさ、コスト
評価軸: 問題解決度、投資対効果、信頼性
質問スタイル: 実利用シーンでの疑問

B. トーン別のアプローチ

Critical (批判的)

鋭い質問と課題指摘
弱点を容赦なく突く
前提を疑い、根拠を求める
最悪のシナリオを想定

Friendly (友好的)

励ましと共感を示す
良い点を認めつつ改善提案
一緒に解決策を考える姿勢
ポジティブな可能性を探る

Constructive (建設的)

バランスの取れた評価
具体的な改善提案を重視
実現可能な代替案を提示
段階的なアプローチを推奨

2. 対象内容の分析

A. 内容の理解

核となる提案の把握
想定される価値の確認
潜在的な問題点の洗い出し
改善の余地の特定

B. 評価の準備

役割視点での関心事項リスト
予想される質問の準備
代替案の検討
参考事例の想起

3. 壁打ちの実施

A. 対話の構造

オープニング: 役割とトーンに応じた導入
理解確認: 提案内容の要約と確認
深掘り質問: 核心を突く質問の連続
課題指摘: 問題点の明確な指摘
改善提案: 建設的な代替案の提示
クロージング: 次のアクションへの誘導

B. 質問技法

オープンクエスチョン: 思考を広げる
クローズドクエスチョン: 明確化を促す
仮説検証型質問: 前提を確認
シナリオ型質問: 具体的状況を想定

4. フィードバックの構造化

A. 指摘事項の整理

重要度による優先順位付け
カテゴリ別の分類
影響範囲の明確化
対処の緊急度

B. 代替案の提示

実現可能性を考慮
段階的実装の提案
リソース効率的な選択肢
リスク軽減策

5. アクションプランの提示

A. 即座に対応すべき事項

B. 中期的に検討すべき事項

C. 将来的な可能性

Output: 壁打ち結果

🧱 壁打ちセッション (Role: $ROLE / Tone: $TONE)

対象の理解

対象内容の要約: [提供された内容を2-3文で要約]

💭 $ROLE としての初見

[$TONE に応じた口調での第一印象]

「[役割の立場から見た率直な感想を、指定されたトーンで表現]」

🔍 深掘り質問と議論

質問1: [核心を突く質問]

「[具体的な質問内容]」

なぜこれを聞くのか: [質問の意図] 期待される回答: [理想的な答え] 現状の懸念: [回答が不明確な場合のリスク]

Read the full file on GitHub · 263 lines

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.

2mo ago First seen · 263 lines · 28 tokens per session scan A 6021bfd572db

Subscribe to this mod's changes

biz:wall is a command published in the GitHub repository reinhardhq/claude-code-spec-boilerplate (2 stars, last pushed 1y ago), licensed MIT. It adds 28 tokens to every session and 2,690 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

biz:wall next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
biz:wallreinhardhq/claude-code-spec-boilerplate	Command	2	1y ago	MIT	A	28	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

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