vibepro 0.1.0-alpha.0

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+https://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or Derivative
+Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work, excluding
+those notices that do not pertain to any part of the Derivative
+Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "[]"
+replaced with your own identifying information. (Don't include
+the brackets!) The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/NOTICE

@@ -0,0 +1,9 @@
+VibePro
+Copyright 2026 Unson LLC
+
+VibePro is licensed under the Apache License, Version 2.0.
+
+Optional integrations:
+Graphify is not bundled with VibePro. VibePro can invoke an externally
+installed `graphify` command or import artifacts generated by Graphify.
+Install and use Graphify under its own license.

package/README.ja.md

@@ -0,0 +1,448 @@
+# VibePro
+
+[![Language: English](https://img.shields.io/badge/Language-English-blue)](README.md)
+[![Language: Japanese](https://img.shields.io/badge/Language-%E6%97%A5%E6%9C%AC%E8%AA%9E-green)](README.ja.md)
+[![Node.js >=20](https://img.shields.io/badge/Node.js-%3E%3D20-339933)](package.json)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache--2.0-blue)](LICENSE)
+
+VibePro は、AI 駆動開発の PR を安全に進めるための CLI 制御基盤です。Feature Story から Architecture、Spec、Verification、Agent Review、PR Evidence を生成・整理し、必要な Gate が揃うまで PR 作成を止めます。
+
+VibePro は対象アプリを自動で書き換えるツールではありません。対象リポジトリ内に `.vibepro/` 作業領域を作り、変更・レビュー・マージの前に必要な証跡を保存します。
+
+## なぜ VibePro か
+
+AI コーディングは速い一方で、最後の 20% に手間がかかります。要求の抜け、UI フローの未確認、API 契約破壊、曖昧なレビュー範囲、見た目は完成しているが実際には触れない PR が起きやすいからです。さらに、広いワークフロー変更が通常の Unit/API 変更のように見えてしまうリスクがあります。
+
+VibePro はその最後の詰めを明示します。
+
+- Story: どんなユーザー価値を満たすべきか。
+- Architecture: どの境界・責務・依存方向を守るべきか。
+- Spec: どの振る舞い・不変条件を満たすべきか。
+- Code: 実際に何が変わったか。
+- Gates: Unit、Integration、E2E、Performance、Security、Review の何が未解決か。
+- Risk profile: 軽い変更か、API契約か、画面操作か、複数の導線をまたぐ重い変更か。
+- PR Evidence: 人間と AI エージェントが作業前に読むべき共通文脈。
+
+基本の流れは次の通りです。
+
+```text
+Story -> Architecture -> Spec -> Code -> Risk-Adaptive Gates -> PR Evidence -> VibePro PR Create
+```
+
+Story と Architecture が確定できれば、実装は AI エージェントへ渡しやすくなります。変更が workflow state、runtime contract、verification evidence、review orchestration にまたがる場合、VibePro は通常の軽いGateではなく重い Gate DAG へ自動で切り替えます。
+
+## 主な機能
+
+- Story / Architecture / Spec を踏まえた PR 準備
+- 変更コードに対する Requirement Consistency 検査
+- 完了条件と workflow-heavy release check を示す、リスクに応じた Gate DAG
+- 大きい変更や危険な変更の PR 分割計画
+- Unit / Integration / E2E / Build / Type-check の検証証跡記録
+- Playwright による UI フロー検証とネットワークエラー検知
+- Performance metric 定義、run 記録、before/after 比較
+- UI、Security、Performance、Architecture、PR Readiness、Launch Readiness の診断パッケージ
+- サブエージェントレビュー依頼とリスクに応じたレビュー結果の記録
+- 未解決Gateとwaiver理由を記録する `vibepro pr create` 経路強制
+- 既存情報構造を壊さずUIを改善する `design-modernize` planning と Derived Design System 生成
+- Skills / Codex instructions の導入による AI 駆動開発ワークフロー標準化
+
+## インストール
+
+VibePro は Node.js 20 以上が必要です。
+
+VibePro は現在 alpha OSS 公開候補です。まだ public npm registry に存在しない場合、`npm install -D vibepro` や `pnpm add -D vibepro` を実行しても npm からは解決できません。
+
+利用方法は次のどれかです。
+
+```bash
+# このリポジトリをcloneしてローカルから使う
+cd /path/to/vibepro
+npm install
+node bin/vibepro.js --help
+
+# npm公開前にGitHubからinstallする
+npm install -g git+https://github.com/Unson-LLC/vibepro.git
+vibepro --help
+```
+
+npm公開後は次の形で使えます。
+
+```bash
+npx vibepro --help
+```
+
+VibePro本体を開発する場合:
+
+```bash
+npm install
+node bin/vibepro.js --help
+```
+
+## 任意連携: Graphify
+
+Graphify は任意ですが、影響範囲調査の精度を上げるため推奨です。VibePro は Graphify 本体や Graphify のコードを同梱しません。`--run-graphify` を使う場合は、外部インストール済みの `graphify` コマンドを呼びます。`--from graphify-out` を使う場合は、Graphify が生成済みの成果物を取り込みます。
+
+```bash
+uv tool install graphifyy
+```
+
+Graphify のインストールと利用は Graphify 側のライセンスに従ってください。Graphify がなくても、多くの Story / Diagnosis / Checkpoint / PR Gate ワークフローは利用できます。ただし、変更ファイルの隣接調査は弱くなります。
+
+以下の例では `vibepro` コマンドを使います。global install していない場合は、`vibepro` を `node /path/to/vibepro/bin/vibepro.js` に置き換えてください。
+
+## 初回: 目的別にこれだけ実行
+
+まずリポジトリ全体を診断したいだけなら、既存の Story ID は不要です。
+
+```bash
+vibepro check all /path/to/repo --base <base-branch>
+```
+
+終わったら次を共有してください。
+
+- `.vibepro/checks/all/<run-id>/check.md`
+- 先頭の `Status`
+- `needs_review` / `fail` になっている項目
+
+特定の機能や不具合に紐づけて診断する場合は、まずローカル Story を作ります。
+
+```bash
+vibepro init /path/to/repo \
+  --story-id story-<short-name> \
+  --title "<機能名または不具合名>" \
+  --language ja
+
+vibepro check all /path/to/repo \
+  --story-id story-<short-name> \
+  --base <base-branch>
+```
+
+すでに VibePro Story があるリポジトリでは、先に一覧や map を確認します。
+
+```bash
+vibepro story list /path/to/repo
+vibepro story map /path/to/repo
+```
+
+PR前の確認が目的なら、見るべき入口は check report ではなく PR prepare の成果物です。
+
+```bash
+vibepro pr prepare /path/to/repo \
+  --story-id <story-id> \
+  --base <base-branch>
+```
+
+見る順番:
+
+1. `.vibepro/pr/<story-id>/review-cockpit.html`
+2. `.vibepro/pr/<story-id>/gate-dag.html`
+3. `.vibepro/pr/<story-id>/split-plan.html`
+4. `.vibepro/pr/<story-id>/pr-body.md`
+
+`<base-branch>` はリポジトリごとに異なります。`origin/main`、`main`、`origin/develop`、`develop` など、そのリポジトリの既定 branch を指定してください。
+
+`pr prepare` は Gate DAG を作る前に変更リスクを分類します。狭い docs / UI 変更は軽いGateに留まります。一方、複数surfaceにまたがる workflow 変更は `workflow_heavy` となり、workflow replay、production path coverage、release confidence、より広い Agent Review role が必要になります。必須Gateが未解決の間、VibePro の `next_commands` は PR 作成ではなく review / verification / prepare の再実行を案内します。
+
+## Quick Start
+
+対象リポジトリを初期化します。
+
+```bash
+npx vibepro init /path/to/repo \
+  --story-id story-internal-beta \
+  --title "社内β診断" \
+  --view dev \
+  --period 2026-W18 \
+  --language ja
+```
+
+Story 診断を実行します。
+
+```bash
+npx vibepro story diagnose /path/to/repo --id story-internal-beta --run-graphify
+```
+
+PR 証跡を生成します。
+
+```bash
+npx vibepro pr prepare /path/to/repo \
+  --base <base-branch> \
+  --story-id story-internal-beta
+```
+
+現在の git 状態で実際に走らせた検証証跡を記録します。
+
+```bash
+npx vibepro verify record /path/to/repo \
+  --id story-internal-beta \
+  --kind unit \
+  --status pass \
+  --command "npm test"
+```
+
+実装完了扱いにする前に checkpoint を通します。
+
+```bash
+npx vibepro checkpoint verification /path/to/repo \
+  --base <base-branch> \
+  --story-id story-internal-beta
+```
+
+必要な Agent Review を準備・記録し、Gate DAG が ready になるまで PR preparation を再実行します。
+
+```bash
+npx vibepro review prepare /path/to/repo --id story-internal-beta --stage gate
+npx vibepro review status /path/to/repo --id story-internal-beta
+npx vibepro pr prepare /path/to/repo --base <base-branch> --story-id story-internal-beta
+```
+
+`pr prepare` が ready を返した後、VibePro 経由で PR を作成します。
+
+```bash
+npx vibepro pr create /path/to/repo \
+  --base <base-branch> \
+  --head <feature-branch> \
+  --story-id story-internal-beta
+```
+
+通常の PR 作成経路として直接 `gh pr create` は使わないでください。VibePro の Gate DAG と waiver audit を通らないためです。
+
+`<base-branch>` はリポジトリごとに異なります。`origin/main`、`main`、`origin/develop`、`develop` など、そのリポジトリの既定 branch を指定してください。VibePro は `init` や `pr prepare` の出力で候補 branch も表示します。
+
+## VibePro が作るもの
+
+VibePro は対象リポジトリの `.vibepro/` に作業領域を作ります。
+
+```text
+.vibepro/
+  config.json
+  vibepro-manifest.json
+  diagnostics/
+  graphify/
+  pr/
+  qa/
+  raw/
+  stories/
+```
+
+PR 前に見る主な成果物:
+
+- `pr-body.md`: Story、リスク、Gate、検証文脈を含む PR 本文ドラフト。
+- `review-cockpit.html`: 人間が見るレビュー画面。
+- `gate-dag.html`: 完了条件の依存関係。
+- `split-plan.html`: PR 分割レーンと merge order。
+- `pr-prepare.json`: AI エージェント向けの機械可読な正本。
+
+人間は Markdown / HTML を読みます。AI エージェントには `pr-body.md`、`review-cockpit.html`、`gate-dag.html`、`split-plan.html`、関連 JSON を渡すのが基本です。
+
+## よく使うワークフロー
+
+### リポジトリを診断する
+
+```bash
+npx vibepro check all /path/to/repo --story-id <story-id> --base <base-branch>
+```
+
+診断パッケージを絞る場合:
+
+```bash
+npx vibepro check ui /path/to/repo --story-id <story-id>
+npx vibepro check security /path/to/repo --story-id <story-id>
+npx vibepro check oss-readiness /path/to/repo --story-id <story-id>
+npx vibepro check performance /path/to/repo --story-id <story-id>
+npx vibepro check architecture /path/to/repo --story-id <story-id>
+npx vibepro check pr-readiness /path/to/repo --story-id <story-id> --base <base-branch>
+```
+
+### UI フローを検証する
+
+```bash
+npx vibepro verify flow /path/to/repo \
+  --base-url http://127.0.0.1:3000 \
+  --id <story-id>
+```
+
+VibePro は Playwright 証跡を記録し、API `4xx` / `5xx`、console error、unhandled rejection、既知の画面エラー文言を Gate finding として扱います。
+
+### 検証証跡を記録する
+
+```bash
+npx vibepro verify record /path/to/repo \
+  --id <story-id> \
+  --kind unit \
+  --status pass \
+  --command "npm test"
+```
+
+記録した証跡は `pr prepare` と PR Gate で再利用されます。
+
+workflow-heavy 変更では Unit/API 証跡だけでは不十分です。VibePro は current git に紐づいた Story E2E / Flow evidence、実行可能な assertion、Gate DAG が要求する risk-adaptive review role も確認します。
+
+### Agent Review を準備する
+
+```bash
+npx vibepro review prepare /path/to/repo --id <story-id> --stage implementation
+```
+
+レビュー結果を記録します。
+
+```bash
+npx vibepro review record /path/to/repo \
+  --id <story-id> \
+  --stage implementation \
+  --role regression_risk \
+  --status pass \
+  --summary "変更フローに回帰リスクは見つからなかった。" \
+  --agent-system codex \
+  --execution-mode parallel_subagent \
+  --agent-id <spawned-subagent-id> \
+  --agent-thread-id <thread-id> \
+  --agent-model <model> \
+  --agent-closed
+```
+
+`gate:agent_review` は、required review に Codex/Claude Code の並列サブエージェント
+証跡と close 済み lifecycle 証跡がある場合だけ検証済みレビューとして扱います。
+各レビュー結果を受け取ったら、記録前にレビューに使ったサブエージェントを close/shutdown し、
+`--agent-closed` を渡して記録してください。Claude Code の場合は `--agent-system claude_code`
+と Task/subagent id、session id、または transcript artifact を渡してください。
+人間レビューは監査用の文脈として記録できますが、required subagent review の代替にはなりません。
+
+```bash
+npx vibepro review record /path/to/repo \
+  --id <story-id> \
+  --stage implementation \
+  --role regression_risk \
+  --status pass \
+  --summary "手動レビューで問題は見つからなかった。" \
+  --agent-system human \
+  --execution-mode manual_review \
+  --recorded-by <reviewer>
+```
+
+手動レビュー証跡は監査文脈としては有用ですが、required Agent Review Gate は通しません。
+実行環境がサブエージェントを起動できない場合、coordinator は gate を通した扱いにせず、
+block するか別の waiver decision として記録します。
+
+### VibePro 経由で PR を作成する
+
+```bash
+npx vibepro pr prepare /path/to/repo --story-id <story-id> --base <base-branch>
+npx vibepro pr create /path/to/repo --story-id <story-id> --base <base-branch> --head <feature-branch>
+```
+
+`pr create` は `pr prepare` が生成した PR 本文を使い、branch push と GitHub PR 作成を実行します。critical Gate が未解決の場合、PR作成前に失敗します。非critical Gate だけが未解決の場合は、`--allow-needs-verification` と `--verification-waiver <reason>` の両方が必要です。
+
+### 既存UIをModernizeする
+
+```bash
+npx vibepro design-modernize derive-system /path/to/repo \
+  --id <story-id> \
+  --product <name> \
+  --routes /home,/map,/detail \
+  --brief "日本語ホテル探索アプリ。地図探索とプロダクト固有CTAを重視する"
+
+npx vibepro design-modernize plan /path/to/repo \
+  --id <story-id> \
+  --product <name> \
+  --routes /home,/map,/detail \
+  --base-url http://127.0.0.1:3000
+```
+
+`derive-system` は product brief と現行UI証跡から、VibePro内の Derived Design System を作ります。product semantics、semantic color roles、component responsibilities、composition rules、visual-hypothesis policy、明示的なDS gateを生成し、画面候補を作る前に「そのプロダクトで許されるデザイン判断の空間」を固定します。
+
+`design-modernize` は、既存のルート、情報構造、CTA、状態、データ依存を保ったまま実プロダクト画面を改善するための workflow です。Design System bundle や生成された visual hypothesis は参照材料であり、VibePro が作った派生デザインシステム、現行スクリーンショット、Graphify/Codex evidence、Gate DAG が実装判断の正本です。
+
+主な成果物は `.vibepro/design-modernize/<story-id>/` 配下に出力されます。
+
+- `design-system-derivation.json` / `.md`: product semantics と Derived Design System の要約
+- `derived-design-system.json`: semantic token、component role map、CTA hierarchy、anti-pattern、visual hypothesis policy
+- `design-modernize.json`: 画面別modernization plan と Design Quality DAG
+- `ds-gate.json`: fallbackを禁止した明示的なDS drift / UX regression clause
+
+外部Design Systemや画像生成案は visual hypothesis として扱います。実装前に、spec が現行route、情報構造、CTA優先度、状態、データ依存を保持していることを確認してください。PR作成前には `vibepro pr prepare` で Design / Requirement / Unit / Integration / Agent Review gate が現HEADに対して解消されている必要があります。
+
+### Performance を測る
+
+Story ごとの metric を定義します。
+
+```bash
+npx vibepro performance define /path/to/repo \
+  --id <story-id> \
+  --metric-id session-switch.user-terminal-ready \
+  --user-story "ユーザーがsessionを切り替え、terminalに入力できる" \
+  --start-condition "session row click" \
+  --completion-condition "owner and inputReady=true" \
+  --evidence-source browser_e2e \
+  --readiness-kind user_perceived
+```
+
+before / after の run を記録します。
+
+```bash
+npx vibepro performance record /path/to/repo \
+  --id <story-id> \
+  --metric-id session-switch.user-terminal-ready \
+  --label before \
+  --status completed \
+  --duration-ms 2400
+
+npx vibepro performance compare /path/to/repo --id <story-id>
+```
+
+VibePro は同じ `metricId` と互換性のある completion condition の run だけを比較します。比較できない場合は、その理由を表示します。
+
+## AI Agent Setup
+
+Claude / Claude Code 向けの同梱 Skills を対象リポジトリへ導入します。
+
+```bash
+npx vibepro skills list
+npx vibepro skills install /path/to/repo
+npx vibepro skills verify /path/to/repo
+```
+
+同梱 Skills:
+
+- `vibepro-workflow`: Story / Architecture / Spec / Graphify / Gate の実行順。design-modernize と Agent Review flow も含む。
+- `vibepro-story-refactor`: Story、Architecture、Spec、Task、Code、Gate evidence を揃えながら進める refactor workflow。
+- `vibepro-diagnosis-packages`: UI、security、performance、architecture、PR、launch readiness の目的別check。
+- `vibepro-human-review`: PR readiness artifact、split plan、review cockpit、waiver 判断の読み方。
+
+Codex 向け instructions を導入します。
+
+```bash
+npx vibepro codex install /path/to/repo
+npx vibepro codex verify /path/to/repo
+```
+
+目的は、agent が Story を読み、証跡を作り、レビューを実行し、PR Gate を守る流れを標準化することです。
+
+## 出力言語
+
+VibePro は人間が読む CLI 出力とレポートで日本語・英語を切り替えられます。
+
+```bash
+npx vibepro init /path/to/repo --language ja
+npx vibepro config language /path/to/repo --language en
+npx vibepro pr prepare /path/to/repo --language en --base <base-branch>
+```
+
+機械可読 JSON のキーは安定性のため英語系のまま維持します。
+
+## ドキュメント
+
+- [English README](README.md)
+- [Changelog](CHANGELOG.md)
+- [Contributing guide](CONTRIBUTING.md)
+- [Security policy](SECURITY.md)
+- [OSS readiness architecture](https://github.com/Unson-LLC/vibepro/blob/main/docs/architecture/vibepro-oss-apache2-readiness.md)
+- [OSS readiness spec](https://github.com/Unson-LLC/vibepro/blob/main/docs/specs/vibepro-oss-apache2-readiness.md)
+
+## プロジェクト状態
+
+VibePro は現在 alpha OSS 公開候補です。安定版公開前に API、report schema、diagnosis pack は変わる可能性があります。
+
+## License
+
+VibePro は [Apache License 2.0](LICENSE) で公開されています。