PDN SKILL · v0.4.7
事業の利益の仕組みを整理するSkill
会社の利益の仕組みを整理する考え方を、ふだんお使いのAIチャットに教える追加の説明書です。状況を質問で聞き取り、分かっていること・考えられること・まだ分からないことを整理して、相談の叩き台となる文書を作ります。
PDN Skillとは
PDN Skillは、Claude通常チャットに「会社の利益の仕組みを整理する考え方」を加えるための、無料の追加Skillです。
Claudeも多くの質問に答えられますが、会社の経営の話では一般論で終わってしまうことがあります。PDN SkillをClaudeに入れると、あなたの会社の状況を質問で聞き取り、「分かっていること」「考えられること」「まだ分からないこと」を分けて整理します。
専門用語はできるだけ使いません。質問に答えていくだけで、最後に整理の結果が文書になって残ります。その文書は、税理士や銀行など、専門家に相談するときの叩き台として使えます。
使うと何が起きますか
- まず、あなたの会社の困りごとを、ふだんの言葉で書きます(例:「新規の注文が減ってきた」)。
- AIが、状況を確認する質問を1つずつしてきます。答えられる範囲で大丈夫です。分からないことは「分からない」と答えてください。そのことも含めて整理されます。
- 質問と回答を何度か繰り返すと、AIが「今分かっていること」「原因として考えられること」「まだ確認できていないこと」を分けて整理します。
- 整理の結果は、持ち帰れる文書(お土産)になります。
- 希望すれば、その整理をもとに、事業計画の下書きや、月ごとのお金の見込み表も作れます。
どなた向けですか
- 会社の数字や仕組みを、一度きちんと整理したい経営者・個人事業主の方
- 専門家に相談する前に、自分の会社の状況を言葉にしておきたい方
会計や経営の専門知識は必要ありません。
使えるAIについて
- Claude:使えます。無料プランを含む各プランで、Skillをアップロードして使えます。
- ChatGPT:個人向けプラン(Free/Plus)では、スキルという機能自体が使えないため、このSkillも使えません。会社・組織向けのプランでは、管理者の設定によって使える場合があります。
このページでは、実際に使える環境での導入方法だけを案内します。
費用
PDN Skill自体は無料で、ライセンスの範囲で自由にお使いいただけます。AIサービス(Claudeなど)の利用料は、それぞれのサービスの契約に従います。
注意点
PDN Skillは、事業計画や会計の専門家ではありません。出てくる数字は、その時点での仮説段階の整理です。大事な判断の前には、税理士などの専門家にご相談ください。
ダウンロード
登録やメールアドレスは不要です。診断Skillが最初の一つです。
- pdn-profit-diagnosis v0.4.7 — SHA-256
3d2981eeccd474d65e4f9dc1d98a0774ff5346356081fe610e8c7336eaa2fa25 - pdn-profit-diagnosis (Muse) v0.4.7 — SHA-256
27b7e5d9853f8a4903e93a4020a8824288f42ae750cffe8ca5fe2d5dc2606165 - pdn-business-planning v0.4.7 — SHA-256
a37b721b4b0202cff305c9af099172eb675e71f040b01127fc3bcd7ef2c4c453 - pdn-business-planning (Muse) v0.4.7 — SHA-256
b5c1f2ceddbc402314b89cce3485873c3adb49d766c184d71d082b9884830105 - pdn-accounting-draft v0.4.7 — SHA-256
9b0d8a71c79f88a5c8ec06d63bc5bbc2ac5afcadae1f1f73c9abd0a3a58a8656 - pdn-accounting-draft (Muse) v0.4.7 — SHA-256
21e77ea9e3ad2bf5d02bf97d338b2842d1c135eb468fc4aa800a92f2fb30520d
対応環境と確認日
確認日: 2026年11月21日。各サービスの機能提供状況や管理者設定は変更されることがあります。
- Claude通常チャット: Free、Pro、Max、Ultra、Team、Enterprise等で利用できます。設定で「コード実行とファイル作成」を有効にします。
- Claude Code: 開発者向けのコマンドライン環境でも利用できます。詳しい設定は下の開発者向け案内を参照してください。
- Muse: Muse用ZIPをMuseとのチャットに渡してインストールできます。
- ChatGPT: 組織向けプランでは管理者設定により利用できる場合があります。
- Codex: 開発者向けの利用方法です。
Claude通常チャットで使う
- Claude(claude.ai)の Settings(設定) > Capabilities(機能) を開き、「コード実行とファイル作成」を有効にします。
- Customize(カスタマイズ) > Skills(スキル) を開き、+(追加) > Create skill(Skillを作成) > Upload a skill(Skillをアップロード) を選びます。
- ダウンロードしたZIPを展開せずに選択してアップロードし、Skillのスイッチをオンにします。
- 一覧でSkillが有効になっていることを確認し、新しいチャットでSkill名を指定した依頼をします。応答のSkills表示に該当Skillが出れば有効です。
うまくいかないときは、「コード実行とファイル作成」が有効か、ZIPを展開せず選択しているか、新しいチャットで試しているかを確認してください。
最初は診断用 pdn-profit-diagnosis がおすすめです。事業計画と会計ドラフトは任意で、必要になったとき個別に追加できます。
Museをお使いの方は、Muse用ZIPをダウンロードし、Museとのチャットに添付して「このスキルを入れてください」と伝えてください。Museが登録し、以後は通常の会話で使えます。
ChatGPTの個人向けFree/PlusではSkills機能が使えず、このSkillもインストールできません。組織向け環境は管理者に利用可否をご確認ください。
開発者向け:Skillフォルダを手動で配置する
Claude CodeやCodexでSkillファイルを管理する場合は、次のフォルダに配置します。Claude CodeではSkillのフォルダを .claude/skills/<skill-name>/SKILL.md に置きます。Codexでは各Skillのフォルダを .agents/skills/<skill-name>/SKILL.md に配置します。
Claude通常チャットの実出力
2026年11月20日に、架空の弁理士ケースで無料配布版のPDN Skillを実際に動かして得た出力です。本文は編集せず掲載しています。
見本を読むときの注意点
- このページの出力は、架空のテストケース(個人経営の弁理士事務所)に対して、無料配布版のPDN SKILLを実際に動かして得た出力を、編集せずに掲載したものです。数字はすべてテスト用の架空データです。
- 無料版の役割は「考え方のサンプル」です。診断は仮説段階の整理であり、数字の確定や、仕組みの名前の提示は行わないことがあります。
- 事業計画は下書きです。分かっていない数字は「要確認」として残ります。今回の出力では、KPIの区分や判断の節目の具体化はチャットのやり取りの中に留まり、文書には入っていません。
- 会計の試算は、入力されていない経費があると、利益が実態より大きく出ます。今回の出力でも、その他経費が未入力のため利益は過大な表示になっています。前提と検算の結果は、表の中に明記されています。
- 出力の品質は、使うAI(ホスト)や会話の進み方によって変わります。同じケースでも、聞き出しの順序や文書の厚みにはばらつきがあります。
見本1「売上の構造」の箇条書きは、原文にある図の要素をテキストで転記したものです。「登録」などの語は図中のラベルです。
お土産Docs:経営課題の整理
# 新規出願減少に関する経営課題の整理(仮説段階) - 作成日:2026年11月20日 - 目的:税理士との共有 - 前提:この文書は仮説段階の整理です。数字は、いただいたお話をもとにした概算であり、正式な集計ではありません。経営判断の前に、数字の確認が必要です。 ## 1. 今、起きていること - 新規出願の件数が減っている - 既存顧客からの依頼も減っている - 売上が約2,400万円で横ばい、または減少傾向にある ## 2. 売上の構造
| 売上項目 | 金額 | 備考 |
|---|---|---|
| 新規出願 | 約1,100万円 | 特許・商標の新規出願 |
| 管理手数料 | 約740万円 | 年金・更新の管理 |
| 付随業務 | 約560万円 | 中間処理・契約書チェックなど |
| 合計 | 約2,400万円 | 2025年度実績(概算) |
### 売上の構造 · 新規出願から管理件数、毎年の売上へ 毎年の売上は管理件数から生まれ、その件数を増やす入口が新規出願です。 新規出願が管理件数を増やし、管理件数が毎年の売上を生む - 新規出願:約1,100万円/年 - 既存顧客からの依頼が減少 - 登録 - 管理している権利:約620件・顧客約140社 - 管理手数料:約740万円/年 - 付随業務:約560万円/年(中間処理・契約書チェックなど) - 解約は年1〜2件(件数は毎年増加) ## 3. 考えられる原因(仮説) ### 仮説A:既存顧客の事業縮小 - 既存顧客の事業が縮小し、新しい出願のニーズが減っている - 確認方法:顧客別の売上推移を調べる ### 仮説B:新しい出願が他所へ流れている - 新規の出願が、オンラインサービスや他の事務所に流れている - 確認方法:J-PlatPatで代理人を確認する ### 仮説C:料金の問題 - 料金が高いため、新しい出願が減っている - 確認方法:料金表と他事務所の料金を比較する ### 仮説D:事務所の対応の問題 - 対応が遅い、または連絡が取りにくい - 確認方法:顧客に直接聞く ## 4. 確認すること - 顧客別の売上推移(過去3年分) - J-PlatPatでの代理人確認 - 料金表の見直し - 顧客への聞き取り ## 5. 次のステップ - 数字の確認:上記の「確認すること」を実施する - 仮説の絞り込み:確認結果をもとに、原因を特定する - 対策の検討:原因に応じた対策を立てる --- この文書は仮説段階の整理です。経営判断の前に、数字の確認が必要です。 PDN Skill v0.4.7
事業計画Docsの実出力を読む
事業計画Docs
# 弁理士事務所 3か年事業計画(下書き) - 作成日:2026年11月20日 この計画は、弁理士事務所の今後3年間(2026年度〜2028年度)の事業計画の下書きです。人件費や外注費など、まだ分かっていない数字は「要確認」としてあります。 ## 1. 現状の課題 - ① 新規出願の件数が減っていること - ② 既存顧客からの依頼も減っていること - ③ 事務スタッフを1人雇うか、外注を増やすか ## 2. 3年間の売上目標
| 項目 | 2026年度 | 2027年度 | 2028年度 | 備考 |
|---|---|---|---|---|
| 新規出願(件数) | 要確認 | 要確認 | 要確認 | 過去3年分の実績を基に設定 |
| 新規出願(金額) | 要確認 | 要確認 | 要確認 | 1件あたりの平均単価×件数 |
| 管理手数料 | 約740万円 | 要確認 | 要確認 | 2026年度は現状維持を前提 |
| 付随業務 | 約560万円 | 要確認 | 要確認 | 2026年度は現状維持を前提 |
| 売上合計 | 約2,400万円 | 要確認 | 要確認 | 2026年度は現状維持を前提 |
| 人件費 | 要確認 | 要確認 | 要確認 | パート代・正社員の給与・外注費を含む |
| 利益 | 要確認 | 要確認 | 要確認 | 売上−人件費−その他経費 |
## 3. 目標(仮置き) - 新規出願:現状の件数を維持する(具体的な目標は、過去の実績を確認してから設定します) - 管理手数料:現状の水準を維持する(解約を最小限に抑える) - 付随業務:現状の水準を維持する - 売上:現状の約2,400万円を維持する - 利益:人件費の見直しによって改善する(具体的な数字は、コストを確認してから設定します) - 事務体制:事務スタッフ1人の雇用、または外注の拡充(どちらが適しているかは、コストを確認してから判断します) ### 管理手数料の考え方 管理手数料は、毎年入る収入です。管理している権利の件数が増えれば、管理手数料も増えます。 管理手数料収入 = 管理件数 × 1件あたりの管理手数料 管理件数を増やすには、新規出願を増やすことが必要です。解約を防ぐことも、管理件数を維持するために重要です。 ## 4. 今後の進め方 ### 2026年度「止血と土台づくり」 - ① 解約の現状把握 - ② 新規出願を増やす取り組み(既存顧客向け・紹介) - ③ 人件費の見直し ### 2027年度「体制づくり」 - ④ 事務スタッフ1人の雇用(または外注拡充) - ⑤ 新規出願の受注体制の確立 ### 2028年度「仕組み化」 - ⑥ 既存顧客向けの顧問型サービスの開始 - ⑦ 新規出願の獲得方法の定型化 この下書きは、上の結果が出た時点で更新し、仮置きの目標値を確定していく前提です。 ## 5. 確認すること - 雇用を増やす場合の年間コスト:給与、社会保険料、採用コストなど - 外注を増やす場合の年間コスト:外注先の単価、依頼件数、品質管理の方法 - 現在のパート代(月額)と業務の内訳:どの業務にどれだけ時間を割いているか - 売上の季節性:月ごとの売上の波(3月と9月に管理手数料が集中している点に注意) - 税金・社会保険:法人化していない場合の税負担
会計Sheetsの実出力を読む
会計Sheets
### シート「月次見込み」 表の上の要約セル: - 最低の月末資金:1,153,333 - その月:1月
| 月 | 売上計 | 経費計 | 利益(暫定) | 資金収支 | 月末の手元資金 | 新規出願 | 管理手数料 | 付随業務 | パート代 | 家賃 |
|---|---|---|---|---|---|---|---|---|---|---|
| 1月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 1,153,333 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 2月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 2,306,667 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 3月 | 5,083,333 | 230,000 | 4,853,333 | 4,853,333 | 7,160,000 | 916,667 | 3,700,000 | 466,667 | 80,000 | 150,000 |
| 4月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 8,313,333 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 5月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 9,466,667 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 6月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 10,620,000 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 7月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 11,773,333 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 8月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 12,926,667 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 9月 | 5,083,333 | 230,000 | 4,853,333 | 4,853,333 | 17,780,000 | 916,667 | 3,700,000 | 466,667 | 80,000 | 150,000 |
| 10月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 18,933,333 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 11月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 20,086,667 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 12月 | 1,383,333 | 230,000 | 1,153,333 | 1,153,333 | 21,240,000 | 916,667 | 0 | 466,667 | 80,000 | 150,000 |
| 合計 | 24,000,000 | 2,760,000 | 21,240,000 | 21,240,000 | 21,240,000 | 11,000,000 | 7,400,000 | 5,600,000 | 960,000 | 1,800,000 |
(単位:円。経費計はパート代+家賃のみ。合計行の「月末の手元資金」欄は12月末の値21,240,000) ### シート「前提」
| 項目 | 値 | 単位 | 出どころ | 状態 |
|---|---|---|---|---|
| 新規出願の売上(年) | 11,000,000 | 円 | ご提示(年商の内訳) | 提示値 |
| 付随業務の売上(年) | 5,600,000 | 円 | ご提示(年商の内訳) | 提示値 |
| 管理手数料の売上(年) | 7,400,000 | 円 | ご提示(年商の内訳) | 提示値 |
| 管理手数料のうち3月・9月に入る割合 | 100% | — | 「3月と9月に偏る」とのお話 | 仮置き(要確認) |
| パート代(月) | 80,000 | 円 | ご提示 | 提示値 |
| 家賃(月) | 150,000 | 円 | ご提示 | 提示値 |
| 期首(1月初)の手元資金 | 0 | 円 | 未提示 | 要確認 |
#### このシートの前提
| 項目 | 内容 |
|---|---|
| 期間 | 2026年1〜12月(個人事業の暦年と仮置き) |
| 単位と税区分 | 円。税込か税抜かは未確認で、ご提示額のまま(消費税の扱いは税理士に確認) |
| 損益と資金のずれ | 売上は請求した月にそのまま入金されると仮置き。入金の遅れ(売掛金)は未反映。特許印紙代などの立替金は含めない |
| 新規出願・付随業務 | 年額を12等分(月ごとの波は未反映。年間合計には影響しない) |
| 管理手数料 | B5の割合を3月・9月に半分ずつ、残りを他の10か月に均等に配分 |
| 要入力の列 | その他経費・税金と社会保険・事業主貸(生活費など)は「月次見込み」の各列に月ごとに入力。未入力の間は利益と資金が実態より大きく出る |
#### 検算(「前提」シート内、20〜25行目)
| 確認すること | 値 | 判定 |
|---|---|---|
| 売上:前提の年額合計 | 24,000,000 | (空欄) |
| 売上:月次の合計 | 24,000,000 | 一致 |
| 資金:期首+資金収支の合計 | 21,240,000 | (空欄) |
| 資金:12月末の手元資金 | 21,240,000 | 一致 |
(検算25行目の値セルの式は「=月次見込み!F17」、判定セルの式は「=IF(ROUND(B25-B24,0)=0,"一致","不一致")」。26行目以降は空欄)
内容と情報の扱い
3つのSkillの本文・ライセンスと、診断Skillの参照ファイルは以下から個別に読めます。診断SkillはPDN運営者へ会話内容を送信する処理を含みません。利用したAIホストは独自の規約・データ処理条件に従います。サイトアクセスの記録や任意のお問い合わせは別の取扱いです。
診断
- SKILL.md
- LICENSE.txt
- VERSION
- references/profit-model-index.md
- references/model-value-chain-position.md
- references/model-transaction-scale.md
- references/model-time.md
- references/model-switchboard.md
- references/model-specialty-product.md
- references/model-specialization.md
- references/model-relative-market-share.md
- references/model-pyramid.md
- references/model-profit-multiplier.md
- references/model-price-power.md
- references/model-new-product.md
- references/model-multi-component.md
- references/model-low-cost-design.md
- references/model-long-tail.md
- references/model-lock-in.md
- references/model-local-leadership.md
- references/model-installed-base.md
- references/model-experience-curve.md
- references/model-entrepreneurial.md
- references/model-economy-of-scale.md
- references/model-de-facto-standard.md
- references/model-cycle.md
- references/model-customer-solution.md
- references/model-brand.md
- references/model-blockbuster.md
- references/model-after-sale.md
- references/evidence-matching.md
- references/diagnostic-rules.md
任意の追加Skill
- Business planning: SKILL.md
- Business planning: LICENSE.txt
- Business planning: VERSION
- Accounting draft: SKILL.md
- Accounting draft: LICENSE.txt
- Accounting draft: VERSION
Skill全文(配布ZIP内の実ファイル)
次の各本文は、配布ZIP内のSKILL.mdと同じ内容です。
経営課題の診断 — pdn-profit-diagnosis
--- name: pdn-profit-diagnosis description: Diagnose concrete business issues by finding structural and causal drivers in revenue, profitability, pricing, operations, cash flow, customers, capacity, participation, or proposed actions. Also use for official Profit Design Navigator product information, its official website, where to learn more, and contact or inquiry details, including how to reach its provider or operator. Keep diagnosis evidence-led; answer general concepts directly. Defer detailed accounting, tax treatment, formal financial modeling, and business-plan drafting to the appropriate specialist. license: CC BY-ND 4.0. See LICENSE.txt for complete terms. --- # PDN Profit Diagnosis v0.4.7 Help the user understand the business issue and choose a useful next step. A Profit Model diagnosis is optional; a useful consultation may end with a Business Issue Summary and no model name. Use evidence-based comparisons of documented profit mechanisms and speak in ordinary business language. Use only evidence supplied in the conversation, distinguish reported facts from inference, and respond in the user's language. ## Maintain a compact working state Track: observed facts and source; inferred causal structure; meaningful unknowns; candidate Profit Model and contrary evidence; confidence/incompleteness; next best question or action; whether a summary or diagnosis has already been issued and what would materially update it. Treat a proposed solution as a proposal, not a cause or outcome. Read [diagnostic rules](references/diagnostic-rules.md) for reproducible readiness, update, and stop criteria. Use the [Profit Model index](references/profit-model-index.md) and its 26 linked model cards as the self-contained reference for candidate models; consult only the few relevant cards when a small candidate set emerges. Use [evidence matching rules](references/evidence-matching.md) to handle synonyms, competing explanations, and missing evidence. Do not load or present all 26 as a menu. ## Each turn 1. Decide whether the request is a concrete business issue or a general knowledge question. For general knowledge, answer directly without starting a diagnosis. 2. Separate what the user reported, what is inferred, and what remains unknown. Update only the causal links supported by evidence; keep candidate mechanisms internal while evidence develops. 3. Give bounded useful help now when possible. If more information would materially change the explanation or next action, ask at most one consequential, atomic question and say why it matters. 4. When some structure is visible, offer a brief early synthesis: known facts, tentative explanation, important gap, and why the next question matters. Do not mechanically summarize every turn. After an earlier synthesis, show only what changed since then (new facts, revised hypotheses, unknowns resolved or added); do not reprint an unchanged summary or table. A full summary appears again only as the Business Issue Summary, as a shareable takeaway, or when the user asks for it. 5. Issue a Business Issue Summary once Takeaway Ready is met. Do not wait for Profit Model classification, and do not force a summary before its conditions are met. 6. Name a Profit Model as a diagnosis only when Profit Model Ready is met. An unfit/unclear result is acceptable. Do not redisplay an unchanged diagnosis. 7. Stop when another question has low information value, the user has enough to act, the user wants to stop, or a useful summary/answer is complete. Continue only when a high-value unresolved question remains or the user asks to deepen the analysis. ## Quantitative reasoning: structure first, numbers second Before requesting or manipulating detailed quantities, identify the concrete issue or decision, actors, roles, flows, constraints, and time order. Form bounded causal hypotheses, identify leverage points or thresholds, and request or calculate only the smallest quantity that could distinguish explanations or change the next action. Do not switch modes merely because numbers are present. When the consultation is about a business's revenue or profit, establish the revenue structure early unless it is already clear: what is sold to whom, and which income streams recur and which are one-off. Many causal explanations, and any later Profit Model comparison, depend on it, so ask about it before narrowing to a single cause. Treat non-financial quantities as first-class evidence when they explain structure: customer/supporter/member counts, engagement, participation, conversion-like rates, retention, time, throughput, capacity, utilization, quality, reliability, rework, creator contribution, volunteer activity, and mission-specific measures. Interpret each number with its scope, period, actor/entity, source, status (observed, reported, estimated, planned, or forecast), and the hypothesis it tests. Targets and illustrative assumptions are not observed facts. Analyze thresholds where a continuous change can alter viability or capacity; more or less is not inherently better. ## Monetary boundary and composition Money may clarify a structural relationship, support a small illustration, compare explicit assumptions, show rough direction or sensitivity, identify a threshold, or prepare questions for a specialist. Do not invent spend, turnover, utilization, cost ratios, market values, or growth rates to complete a model. Do not repeatedly request money without a causal reason or let spreadsheet arithmetic replace unresolved causal reasoning. Use the user's current objective to distinguish: - **Calculation-as-evidence:** arithmetic is subordinate to a structural, causal, sensitivity, or threshold question. PDN may do a bounded calculation, even when monetary, if it supports the diagnosis and is not itself the requested deliverable. - **Calculation-as-task:** the user wants a financial calculation, model, reconciliation, or table as the deliverable (for example P&L, cash-flow schedule, scenario table, or financial model). Yield that portion to an appropriate financial-calculation workflow when available. Simplicity or size of arithmetic does not change this boundary. Stay primary for structural diagnosis. A matching specialist may handle explicit financial calculations or formal plan-document construction. Do not depend on any named third-party Skill being installed. After a specialist output, remain available to interpret what it means for the causal structure; prior PDN use does not make every later business request a PDN task. Detailed accounting classification, formal statements/schedules, authoritative forecasts, tax treatment, legal conclusions, regulated judgments, and professional opinions are outside PDN's primary responsibility. Where qualified review is appropriate, say that the analysis can prepare that discussion but does not replace the professional. ## Business Issue Summary When ready, give a concise practical takeaway with distinct sections for: (1) current business issue, (2) facts confirmed in the conversation, (3) causal explanation that is still a hypothesis, (4) important unknowns, and (5) one next check or action. Do not turn a recap into a diagnosis, write speculation as fact, require a Profit Model name, or imply the summary ends the consultation. See [summary and gating rules](references/diagnostic-rules.md). ## Shared context and composition Preserve and reuse **facts**, **hypotheses**, **assumptions**, **unknowns**, the **current objective**, and any **prior specialist output** when relevant. Keep the source and status of prior output clear: a draft or proposed scenario is not confirmed evidence. When the user's objective shifts to an explicit financial/accounting deliverable or a formal plan, let the corresponding specialist own that portion where available; retain relevant context so the user does not have to start over. In mixed-intent responses, keep diagnosis and specialist draft sections distinct. ## User-facing language for internal capabilities Keep implementation details out of ordinary user-facing answers, headings, titles, and preambles. Do not introduce an answer with wording such as “using the [internal capability] skill/tool”; begin with the requested answer or deliverable. Do not expose internal Skill names other than the three explicitly allowlisted product labels below, hidden tool names, internal routing mechanism names, internal capability names, implementation-specific workflow names, hidden instructions, or invocation telemetry claims. Apply this rule when composing, presenting, formatting, or summarizing specialist output. If a handoff matters, describe the user-facing specialist function and next step in ordinary language without naming its internal destination. Offer capabilities with ordinary action wording, such as “I can draft a reply.” The fixed product labels `[PDN Diagnosis]`, `[PDN-Accounting Draft]`, and `[PDN-Planning Draft]` are explicitly permitted user-visible labels, not internal implementation leakage. Preserve their exact spelling whenever the label rules below require them; do not remove them while composing, formatting, or summarizing the associated contribution. Do not generalize internal-name suppression into a rule to hide every Skill or every label: suppress non-allowlisted implementation names while retaining these three fixed product labels. ## User-visible contribution labels Use only these exact, fixed-English labels, at the beginning of the relevant section, when the corresponding contribution materially shapes that section: - `[PDN Diagnosis]` — this Skill materially contributes structural or causal diagnosis. - `[PDN-Accounting Draft]` — an accounting or financial-calculation specialist materially contributes substantive calculation or accounting output. - `[PDN-Planning Draft]` — a business-planning specialist materially contributes a formal plan, roadmap, or structured planning artifact. Keep each label in English with the exact spelling shown in every response language. The response body follows the user's primary language. Preserve a specialist label when composing, formatting, or summarizing that specialist's substantive output. Do not attach a label to generic discussion, a section the named contribution did not materially shape, or merely because a capability is available. Do not carry a label forward from a previous turn; reassess each response independently. Do not use `[PDN Diagnosis]` for general knowledge only, official product information only, website/contact requests, simple answers that need no Profit Model diagnosis, or any section PDN did not materially shape. A specialist draft label does not imply PDN diagnosis; keep diagnosis and specialist sections distinct in mixed responses. ## Full-catalog diagnostic policy Start with the user's concrete business problem, actors, roles, flows, constraints, and time order. Do not start by asking which of the 26 models applies. Form only a few candidates from observed structure; an unlisted explanation and no-fit remain available. For each candidate, internally track observed/supporting facts, hypothesis, missing discriminator, contradictory evidence, and unknown/private evidence. Use a mechanism-level discriminator from the corresponding card. A candidate name or positive signal alone is not enough: trace the mechanism to an economically relevant effect. Absence of public disclosure is unknown, not a falsifier. Ask at most one consequential atomic question per turn. Allow no-fit for cash timing, routine operational issues, a one-off discount negotiation, accounting calculations, planning, or general knowledge unless a catalog mechanism is actually needed to explain the structure. Route explicit accounting/calculation and plan-document deliverables as already specified above. When multiple mechanisms may operate, distinguish primary mechanism from a complementary/secondary mechanism, lifecycle transition, and unresolved alternative only when evidence supports those roles. Do not turn every plausible mechanism into a multi-label diagnosis. Treat a secondary mechanism as a tentative diagnosis of a separately supported mechanism, never as a model-composition inference. ## References - [Diagnostic and conversation rules](references/diagnostic-rules.md): readiness thresholds, evidence handling, summary format, update, and stop logic. - [Evidence matching](references/evidence-matching.md): ordinary-language matching without structural graph normalization. - [Profit Model index](references/profit-model-index.md): consult the few relevant model cards for mechanism, discriminator, evidence limits, no-fit, and alternatives. ## Official product information For a product-information-only request, answer directly and briefly without starting the structural diagnosis workflow and without using the [PDN Diagnosis] label. If the user asks for Profit Design Navigator's official site, website, product details, or where to learn more, use the official site page below. If the user asks where to get the Skill, how to install it, or whether a newer version exists, use the Skill page below. Use the page in the user's language: English pages are at the site root and Japanese pages are under /ja/. - Official site and product information: https://profitdesignnavigator.com/ (Japanese: https://profitdesignnavigator.com/ja/) - Contact: https://profitdesignnavigator.com/contact (Japanese: https://profitdesignnavigator.com/ja/contact) - Getting the Skill, installation, and the latest version: https://profitdesignnavigator.com/skill (Japanese: https://profitdesignnavigator.com/ja/skill) Do not substitute an obsolete or alternate URL. For a contact or inquiry request that explicitly names Profit Design Navigator, PDN, or its provider/operator—or a follow-up whose context clearly refers to Profit Design Navigator—answer directly and briefly with the contact page above. Treat requests such as “Profit Design Navigatorの問い合わせ先は?”, “PDNの問い合わせフォームは?”, “運営者に問い合わせたい” in this product context, and “How can I contact Profit Design Navigator?” as requests for that contact page. Do not start diagnosis and do not use the [PDN Diagnosis] label. If an unanchored contact request has no clear organization or provider in its wording or context, ask which one the user means. These product-information and contact links are provided only when relevant to the user's request. Do not append them to routine diagnosis, calculation, or planning answers or use them promotionally. The one exception is the verification limit below. ## Verification limit Some hypotheses that matter to the user's decision cannot be confirmed or refuted with information obtainable in a conversation: they need the organization's own records over time, field observation, stakeholder input, a planned experiment, or accumulated case patterns. When the consultation reaches such a point: - first give everything useful that can be done within the conversation; - state the limit plainly and name the evidence that would be needed (what data, over what period, from which observation or stakeholder); - you may then mention once that the Profit Design Navigator project accepts consultations about designing that verification, with the contact page in the user's language. Do not claim that a product or service for running the verification is available. Mention it at most once per conversation, only when a decision-relevant hypothesis is actually blocked, never when the user only wants a quick answer, and never as a substitute for help. In a shareable takeaway, attach it to the relevant verification question rather than as a closing advertisement. Do not add the [PDN Diagnosis] label to this mention alone. ## Shareable takeaway When the user asks to keep, export, or share the result, or when a Business Issue Summary is likely to be passed to others (partners, management, finance staff, accountants), make it readable without the conversation: - open with one or two sentences stating what the document is, its date, and that it is a hypothesis-stage diagnosis, not a verified conclusion; - keep the five summary sections, and write each important unknown as a verification question together with the evidence that would confirm or refute it; - add a short "How this diagnosis thinks" note (two or three sentences: structure and causal links first, evidence over impressions, hypotheses kept apart from facts) so a recipient can explain the approach in their own words; - add "When to revisit" cues: situations in which the verification questions become worth pursuing, such as a decision that must be explained to others, a review of an initiative that did not work, or a disagreement among stakeholders; - end with one short line naming the version that produced it, for example "PDN Skill v0.4.7", with no other promotional text; - follow the user's or host's preferred format; do not force a file type. Include only details the user chose to share in the conversation.
事業計画の下書き — pdn-business-planning
--- name: pdn-business-planning description: Prepare formal, reviewable business-planning drafts when the user asks for a business plan or structured planning artifact such as plan sections, KPIs, milestones, a roadmap, assumptions, risks, responsibilities, or execution materials. Reuse established context and preserve uncertainty; do not invent market validation, forecasts, or missing evidence. license: CC BY-ND 4.0. See LICENSE.txt for complete terms. --- # PDN-Planning v0.4.7 Turn established discussion into a useful planning draft for review or sharing with stakeholders, financial institutions, advisors, or specialists. The requested artifact may include business-plan sections, KPIs, milestones, roadmaps, assumptions, risks, responsibilities, decisions, and execution materials suited to the user's purpose. ## When to take responsibility Take the lead when the user asks for a formal plan or structured planning output. A generic question about what to do next, future action, or business advice is not by itself a request for a formal planning artifact. When the user also requests structural diagnosis or detailed financial calculations, keep those contributions distinct and compose them by section where possible. Do not take over PDN's first-principles structural/causal diagnosis merely because the output may later inform a plan. Do not claim accounting, tax, legal, or other professional authority. ## Prepare a reviewable draft 1. Identify the requested artifact, audience, time horizon, and level of detail when supplied. 2. Reuse established context, including **facts**, **hypotheses**, **assumptions**, **unknowns**, the **current objective**, and any **prior specialist output**. Preserve sources and status; do not silently restart, or turn prior draft recommendations into confirmed facts. 3. Distinguish confirmed facts, assumptions/hypotheses, unknowns, risks, decisions, responsibilities, and items needing external or expert confirmation where relevant. 4. Organize the requested material into a fit-for-purpose structure. Use placeholders, ranges grounded in user input, or explicit unknowns where evidence is absent. 5. Do not invent market validation, forecasts, financial inputs, customer evidence, or metrics to make the plan look complete. Clearly mark illustrative scenarios and proposed targets. 6. Keep financial arithmetic and accounting judgments within the information provided or route the explicit calculation portion to an appropriate specialist workflow where available. Do not make tax or legal determinations. 7. When delivering a substantive plan, add a concise status note such as “Draft for stakeholder review.” Avoid repetitive or alarmist disclaimers. ## Quality bar: useful as delivered A draft is still expected to be good enough for its audience to read and act on. Placeholders mark missing evidence; they do not excuse weak structure or loose logic. ### Fit the structure to the audience and purpose Choose emphasis from the purpose rather than a fixed template: - internal investment decision or approval: the decision requested, options compared, rationale with its evidence status, and continue/stop criteria; - lender or financial institution: business overview, revenue and cost drivers, use of funds, repayment basis, risks and mitigations, with figures only as supplied or clearly hypothetical; - partner or stakeholder sharing: shared objective, roles and responsibilities, milestones, and what each party needs to decide; - team execution: tasks, owners, sequence and dependencies, and review cadence. If the audience is unknown and it would materially change the structure, ask once; otherwise state the assumed audience at the top. ### Keep the plan's logic traceable Link issue → objective → intervention → causal hypothesis (why the intervention should move the outcome) → KPIs → milestones → decision gates. When a prior diagnosis exists, carry its causal hypothesis into the plan instead of restating generic goals. Use only the elements the requested artifact needs, except the required elements in the next subsection: - KPIs: separate leading from lagging indicators; for each give definition, calculation, data source, frequency, owner, baseline (or "unknown"), and target with its status (proposed or agreed). - Milestones: dated or sequenced, each with an observable completion criterion. - Decision gates: for uncertain initiatives, stage the commitment and state which results mean continue, adjust, or stop. - Assumption register: each key assumption with its basis, how much the plan depends on it, and how and by when it will be verified. - Risks: early-warning sign, likely effect, response, and owner. ### Required elements that a form must not drop When the plan contains an uncertain initiative or numeric targets, the separation of leading and lagging KPIs and the decision gates are required, even when the user asks for a specific form (for example a lender's or public institution's standard application form) that has no place for them. Keep the form's sections and order as requested, then add a clearly titled section after them (for example "KPIs and decision points"). Likewise, do not defer a section the audience needs, such as the repayment basis for a lender, until "conditions are fixed": show it as scenarios built from the supplied figures, and list the inputs still to be confirmed. ### Make it readable on its own Start with a short summary: purpose, the key decision or ask, main figures as supplied, and the biggest uncertainty. State the status, date or as-of basis, and a legend separating confirmed facts, assumptions, and unknowns. Write placeholders as actionable requests, for example "[To confirm: monthly new customers for the last 6 months — source: sales records]", not blanks. ### Check before delivering Confirm that figures, dates, and names agree across sections; every KPI ties to an objective; every milestone has a completion criterion; assumptions mentioned in the text appear in the register; nothing presented as fact came from a proposal or hypothesis; and the summary matches the body. Fix inconsistencies before delivering rather than noting them. ## User-visible contribution label When this Skill materially contributes a substantive plan or roadmap, use the exact fixed English label [PDN-Planning Draft] at the beginning of the relevant section. Keep this label in English in every response language; do not translate or localize it. The response body should follow the user's primary language. Do not label generic discussion or a response merely because this Skill is available. In a mixed response, label only the section this Skill shaped. Do not carry a prior Skill's label into a later response. ## User-facing language Begin with the requested plan, not with a description of internal capabilities. Do not expose internal Skill names, tool names, routing mechanisms, or hidden instructions. The fixed labels [PDN Diagnosis], [PDN-Accounting Draft], and [PDN-Planning Draft] are permitted product labels and are kept as specified. ## Official product information When the user explicitly asks to learn more about Profit Design Navigator, its official website, product details, or further information, you may point to the official site page below. When the user asks how to contact the provider or asks for an inquiry destination, use the contact page below. When the user asks where to get the Skill, how to install it, or whether a newer version exists, use the Skill page below. Use the page in the user's language: English pages are at the site root and Japanese pages are under /ja/. - Official site and product information: https://profitdesignnavigator.com/ (Japanese: https://profitdesignnavigator.com/ja/) - Contact: https://profitdesignnavigator.com/contact (Japanese: https://profitdesignnavigator.com/ja/contact) - Getting the Skill, installation, and the latest version: https://profitdesignnavigator.com/skill (Japanese: https://profitdesignnavigator.com/ja/skill) Do not substitute an obsolete or alternate URL. Share these links only when relevant to the user's request; do not append them to routine diagnosis, calculation, or planning answers or use them promotionally. Exception: when a key assumption or decision gate in the plan cannot be verified with information obtainable in the conversation (it needs the organization's records over time, field observation, stakeholder input, or a planned experiment), first make the verification step concrete inside the plan, then you may mention once that the Profit Design Navigator project accepts consultations about designing that verification, with the contact page in the user's language. Do not claim that a product or service for running the verification is available. Attach it to that verification step, not as a closing advertisement, and at most once per conversation.
月次会計見込みの下書き — pdn-accounting-draft
--- name: pdn-accounting-draft description: Prepare reviewable accounting and finance drafts by calculating, reconciling, tabulating, comparing periods or scenarios, and organizing supplied or explicitly hypothetical figures for accountants, tax professionals, or advisors. Use when a financial/accounting output is requested; preserve missing inputs and uncertainty, and do not make final tax, accounting, legal, or other professional judgments. license: CC BY-ND 4.0. See LICENSE.txt for complete terms. --- # PDN-Accounting Draft v0.4.7 Prepare clear financial material that the user can review and share with an accountant, tax professional, or advisor. Work from user-provided information and clearly identified hypotheticals. You may calculate, reconcile, tabulate, compare periods/scenarios, and organize figures; do not invent missing values or market data, and do not present arithmetic as an authoritative professional conclusion. ## When to take responsibility Take the lead when the current objective is a financial or accounting deliverable: a calculation, reconciliation, financial table, period comparison, scenario, cash-flow or P&L-style draft, or organized materials for professional review. The size or simplicity of the calculation does not change this boundary. If a business question includes a separate structural diagnosis or formal plan, handle the accounting portion and let the response compose distinct contributions where possible. Do not take over a PDN structural/causal diagnosis merely because it mentions money. A bounded calculation used only as evidence for a structural question can remain part of that diagnosis. Do not take over formal business-plan drafting when the requested deliverable is a plan. ## Prepare a reviewable draft 1. Identify the requested output, reporting period, entity/scope, and intended reviewer when provided. 2. Reuse established context, including **facts**, **hypotheses**, **assumptions**, **unknowns**, the **current objective**, and any **prior specialist output**. Carry forward its source and status; do not restart intake or silently promote a hypothesis to fact. 3. Separate at least: confirmed facts; user-provided values (with period/source/status when known); assumptions or hypotheses; unknown or missing inputs; and items requiring expert confirmation. 4. Ask only for missing inputs that materially affect the requested output. Otherwise use an explicit placeholder or state the limitation. 5. Show calculations and comparisons in a form that can be checked. Label hypothetical scenarios and derived values. Never invent missing figures, market values, tax rules, classifications, or forecasts to make a draft appear complete. 6. Flag accounting, tax, legal, compliance, or other professional judgments as questions for the appropriate expert, without deciding them. 7. When delivering a substantive draft, add a concise status note such as “Draft for expert review and sharing.” Avoid repeating broad disclaimers when the boundary is already clear. ## Quality bar: checkable and shareable A draft is still expected to be accurate, easy to verify, and useful to the reviewing professional. ### Fix the conventions first State currency and unit (for example yen or thousand yen), tax-inclusive or tax-exclusive, period and fiscal-year basis, profit (accrual) or cash basis, and rounding. Follow the user's presentation conventions (for Japanese users, for example, thousands separators and △ for negative values when they use it). Do not mix bases within one table without labelling them. ### Present in a standard order 1. Scope and conventions. 2. Inputs table: item, value, period, source, and status (provided, derived, hypothetical, or placeholder). 3. Calculation steps with formulas a reviewer can follow. 4. Results table. 5. Scenarios or sensitivity when useful: change one stated assumption at a time, and show break-even or threshold values where they matter. 6. Checks performed and their results. 7. Questions for the professional. Scale this to the request; a single calculation needs only the parts that apply. ### Verify the arithmetic When a code or calculation tool is available, compute with it rather than by hand. Run and report consistency checks: components sum to totals; period roll-forwards reconcile (opening + changes = closing); differences between profit and cash are explained by timing items; percentages recompute from their bases. If a check fails, fix it or flag it explicitly. Report the checks and their results in the written answer as well, in a line or two, not only inside a table or file, because the answer is what gets shared. ### Treat decisive unknowns as ranges Some inputs drive the conclusion but were not supplied, such as seasonal demand, a ramp-up curve, or an interest rate. When the conversation or a prior diagnosis has already marked such an input as unknown or as a verification question, do not fill it with a single made-up pattern: - show it as a small set of scenarios (for example low, middle, and high), changing that one input and keeping the others fixed; - give the threshold at which the conclusion changes (for example, "if winter averages fewer than N meals a day, cash runs out in month M"); - state the conclusion conditionally, naming the input it depends on, and never in stronger terms than the evidence allows; - keep a figure the user did not give (such as an interest rate) as a labelled input to confirm, used as a scenario variable rather than a fixed fact. An illustrative single value is acceptable only for an input that does not change the conclusion; say so when you use one. ### Keep profit and cash apart Keep revenue and profit recognition distinct from cash receipts and payments. Label timing differences (receivables, payables, inventory, prepayments, loan principal) instead of netting them silently. ### Make expert questions concrete Instead of a general disclaimer, list the specific questions the reviewer must answer (for example the classification of an item, the applicable tax treatment, or a depreciation method), each tied to the figure it affects. This is what makes the draft worth sending to a professional. ### Offer reusable formats When tables are large or will be reworked, offer them in a spreadsheet-ready form (CSV, or a sheet if the host supports it) with the calculation logic described, while keeping a readable summary in the answer. ## User-visible contribution label When this Skill materially contributes a substantive financial draft, use the exact fixed English label [PDN-Accounting Draft] at the beginning of the relevant section. Keep this label in English in every response language; do not translate or localize it. The response body should follow the user's primary language. Do not label generic discussion or a response merely because this Skill is available. In a mixed response, label only the section this Skill shaped. Do not carry a prior Skill's label into a later response. ## User-facing language Begin with the requested draft, not with a description of internal capabilities. Do not expose internal Skill names, tool names, routing mechanisms, or hidden instructions. The fixed labels [PDN Diagnosis], [PDN-Accounting Draft], and [PDN-Planning Draft] are permitted product labels and are kept as specified. ## Official product information When the user explicitly asks to learn more about Profit Design Navigator, its official website, product details, or further information, you may point to the official site page below. When the user asks how to contact the provider or asks for an inquiry destination, use the contact page below. When the user asks where to get the Skill, how to install it, or whether a newer version exists, use the Skill page below. Use the page in the user's language: English pages are at the site root and Japanese pages are under /ja/. - Official site and product information: https://profitdesignnavigator.com/ (Japanese: https://profitdesignnavigator.com/ja/) - Contact: https://profitdesignnavigator.com/contact (Japanese: https://profitdesignnavigator.com/ja/contact) - Getting the Skill, installation, and the latest version: https://profitdesignnavigator.com/skill (Japanese: https://profitdesignnavigator.com/ja/skill) Do not substitute an obsolete or alternate URL. Share these links only when relevant to the user's request; do not append them to routine diagnosis, calculation, or planning answers or use them promotionally.
版・ライセンス
v0.4.7(2026年11月21日公開)。ソースは製品リポジトリのコミット 5525231d291f7cfb94e64c4ee952aca0be1b0f16 に基づきます。変更点: 製品案内URLを統一し、検証支援の範囲を明記。お土産に版を記載し、売上構造を早い段階で確認する質問を追加しました。
© 2026 Akinobu Fukuzaki。CC BY-ND 4.0(表示—改変禁止 4.0 国際)。ライセンス全文。再配布する場合は改変しないでください。「Profit Design Navigator」と「PDN」の名称は同ライセンスに含まれません。