[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BNAM8F0ZECZ7XQ0EGSZZW":3,"skill-same:01M79BNAM8F0ZECZ7XQ0EGSZZW":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":13,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":49},"01M79BNAM8F0ZECZ7XQ0EGSZZW","harness-accept",null,"Generate an Acceptance Demo HTML for non-engineer vibecoders right before ship\u002Fwait\u002Freject decision. Reads back the acceptance_criteria that were stored as personal-preference.v1 by harness-plan-brief (joined by user_request_hash), then renders a single-file HTML showing each criterion as verified or unverified along with a ship\u002Fwait\u002Freject recommendation. Use when the user asks for an acceptance review, wants to decide whether to ship a delivered task, or says: acceptance demo, accept demo, 受け入れ判断, 受入レビュー, ship\u002Fwait\u002Freject 判定, 検収レビュー. Do NOT load for: implementation, code review, release work.","Timothy191\u002Farch-systems-portal","Timothy191","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F219252205?v=4","01M79B3963G748F05KS7AH3NJR","01M79B396N88AYYNHK5G2DNP2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fharness-accept\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: harness-accept\ndescription: \"Generate an Acceptance Demo HTML for non-engineer vibecoders right before ship\u002Fwait\u002Freject decision. Reads back the acceptance_criteria that were stored as personal-preference.v1 by harness-plan-brief (joined by user_request_hash), then renders a single-file HTML showing each criterion as verified or unverified along with a ship\u002Fwait\u002Freject recommendation. Use when the user asks for an acceptance review, wants to decide whether to ship a delivered task, or says: acceptance demo, accept demo, 受け入れ判断, 受入レビュー, ship\u002Fwait\u002Freject 判定, 検収レビュー. Do NOT load for: implementation, code review, release work.\"\ndescription-en: \"Generate an Acceptance Demo HTML for non-engineer vibecoders right before ship\u002Fwait\u002Freject decision. Reads back the acceptance_criteria that were stored as personal-preference.v1 by harness-plan-brief (joined by user_request_hash), then renders a single-file HTML showing each criterion as verified or unverified along with a ship\u002Fwait\u002Freject recommendation. Use when the user asks for an acceptance review, wants to decide whether to ship a delivered task, or says: acceptance demo, accept demo, 受け入れ判断, 受入レビュー, ship\u002Fwait\u002Freject 判定, 検収レビュー. Do NOT load for: implementation, code review, release work.\"\ndescription-ja: \"実装完了直後の受け入れ判断 (ship \u002F wait \u002F reject) 前に Acceptance Demo HTML を生成する。harness-plan-brief が `personal-preference.v1` で書き込んだ acceptance_criteria を `user_request_hash` 経由で取得し、各基準ごとに verified \u002F unverified を表示。`recommendation` を ship \u002F wait \u002F reject の 3 値で算出し、根拠を HTML 上で可視化する。Use when: 受け入れ判断, 受入レビュー, ship\u002Fwait\u002Freject 判定, 検収レビュー。Do NOT load for: 実装作業, code review, release。\"\nallowed-tools: [\"Read\", \"Write\", \"Edit\", \"Bash\"]\nargument-hint: \"[task-description]\"\nuser-invocable: true\n---\n\n# harness-accept\n\n非エンジニアの発注者・プロデューサー職向けに、実装完了タスクの受け入れ判断 (ship \u002F wait \u002F reject) を **HTML 1 枚** で提示するスキル。\n発注者の認知負荷ピーク (3) 受け入れ判断の段階で使う。\n\nPhase 65.1.x (`harness-plan-brief`) の対構造として動作し、Plan Brief で承認した `acceptance_criteria` を read 側で取り戻して評価する。\n\n## Quick Reference\n\n- 「**Acceptance Demo を作って**」 → このスキル\n- 「**受け入れ判断したい**」 → このスキル\n- 「**ship\u002Fwait\u002Freject 判定**」 → このスキル\n\n## 責任境界\n\n| 範囲                | このスキルの責務                                                                                   |\n| ------------------- | -------------------------------------------------------------------------------------------------- |\n| 検索                | **現プロジェクトのみ** (`project: \u003Ccurrent>`, `strict_project: true` を必ず指定)                   |\n| クロスプロジェクト  | **やらない** (Phase 65.3 以降で `--cross-project-group \u003Cname>` flag で opt-in 解放)                |\n| Plan Brief 連携     | `user_request_hash` を join key として `personal-preference.v1` (Phase 65.1.4) を read             |\n| 書き込み            | やらない (Acceptance 承認後の memory write は `accept-record-decision.sh` の責務)                  |\n| recommendation 算出 | verified \u002F 全 criteria の比率で 0.8 \u002F 0.5 閾値判定。ロジックは `scripts\u002Frender-html.sh` 直前で計算 |\n\n## 入力\n\n引数 `[task-description]` にユーザーの request を渡す (Plan Brief 時と同じ文を使う)。\n引数なしの場合は対話形式で受け取る。\n\n## 出力\n\n| 出力                    | パス                                                  | 形式                                           |\n| ----------------------- | ----------------------------------------------------- | ---------------------------------------------- |\n| Acceptance Demo HTML    | `.claude\u002Fstate\u002Fviews\u002Faccept-\u003Ctimestamp>.html`         | 単独で開ける HTML (no server, no JS framework) |\n| Acceptance context JSON | `.claude\u002Fstate\u002Fviews\u002Faccept-\u003Ctimestamp>.context.json` | `acceptance-context.v1` schema                 |\n\n## Schema: `acceptance-context.v1`\n\n```json\n{\n  \"schema\": \"acceptance-context.v1\",\n  \"user_request\": \"string\",\n  \"user_request_hash\": \"sha256 hex (Plan Brief 側の personal-preference.v1 と join)\",\n  \"demo_artifacts\": [{ \"kind\": \"video|screenshot|text\", \"path\": \"string\" }],\n  \"verified_criteria\": [{ \"name\": \"string\", \"passed\": true, \"evidence\": \"string\" }],\n  \"tdd_verified\": \"yes|no|not-required|skip:\u003Creason>\",\n  \"unverified_caveats\": [\"string\"],\n  \"past_issue_patterns\": [\n    { \"pattern_id\": \"P5\", \"title\": \"string\", \"verified_in_current_task\": true }\n  ],\n  \"recommendation\": \"ship|wait|reject\",\n  \"recommendation_evidence\": [\"string\"],\n  \"project\": \"string\",\n  \"generated_at\": \"ISO8601\"\n}\n```\n\n完全 schema は [`schemas\u002Facceptance-context.v1.schema.json`](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Facceptance-context.v1.schema.json) を参照。\n\n## Recommendation 算出ロジック\n\n```\nverified_count    = count of verified_criteria where passed=true\ntotal_criteria    = count of verified_criteria\nratio             = verified_count \u002F total_criteria  (total=0 のときは 0)\n\n  ratio >= 0.8 → \"ship\"\n  ratio >= 0.5 → \"wait\"\n  ratio \u003C  0.5 → \"reject\"\n  total = 0    → \"reject\" (criteria 0 件は判定不能、安全側 reject)\n```\n\n評価根拠は `recommendation_evidence` に literal な数値で残す。\n例: `\"verified 4 件 \u002F 全 5 件 (80%) → ship 閾値以上\"`\n\n## Execution Flow\n\nスキル起動時、Claude は以下の手順で動作する。\n\n### Step 1: project name と user_request_hash を解決\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\")\"\nUSER_REQUEST_HASH=\"$(printf '%s' \"$USER_REQUEST\" | sha256sum | awk '{print $1}')\"\n```\n\n`PROJECT_NAME` が空 (git 外) の場合は `current` をデフォルトに使う。\n\n### Step 2: harness-mem を **project-only** で検索し、Plan Brief 側 record を取得 (default)\n\n引数に `--cross-project-group \u003Cname>` flag が**ない**場合 (default behavior):\n\n`mcp__harness__harness_mem_search` を以下のパラメータで呼び出す:\n\n```\nproject: \u003CPROJECT_NAME>\nstrict_project: true\ntags: [\"personal-preference\", \"plan-brief-approval\"]\nlimit: 10\n```\n\n> **重要**: `project` パラメータは**必須**。`strict_project: true` を指定し、cross-project な検索は**絶対に行わない**。\n\n取得した record を `data.user_request_hash == \u003CUSER_REQUEST_HASH>` でフィルタし、最も新しい 1 件を選ぶ。\nこれが Plan Brief 時の承認内容 (chosen_option \u002F acceptance_criteria 等) を保持している。\n\n### Step 2 (alt): cross-project search (Phase 65.3.5 opt-in)\n\n引数に `--cross-project-group \u003Cname>` flag が**ある**場合のみ、横断 group 内の他プロジェクトでの\n類似 plan-brief-approval \u002F acceptance-decision 履歴を取得する (D43 Option α):\n\n```bash\nMEMBERS_JSON=\"$(bash scripts\u002Fload-cross-project-groups.sh --group \"\u003Cname>\" 2>\u002Fdev\u002Fnull)\" || {\n  echo \"ERROR: cross-project group not found: \u003Cname>\" >&2\n  exit 1\n}\n```\n\n`MEMBERS_JSON` が `[]` の場合は default の単一 project search に fallback。\n\n`MEMBERS_JSON` が非空の場合、各 member project ごとに MCP search を 1 回発行:\n\n```\nfor each project in MEMBERS_JSON:\n  mcp__harness__harness_mem_search(\n    project: \u003Cmember>,\n    strict_project: true,\n    tags: [\"personal-preference\", \"plan-brief-approval\"],\n    limit: 10\n  )\n```\n\n結果を client 側でマージし、`data.user_request_hash == \u003CUSER_REQUEST_HASH>` でフィルタ。\nhash 一致は基本的に同一 user request 由来のため複数 project での重複は稀だが、念のため id 単位で dedupe。\n\ncross-project 由来の record を採用すると過去他案件の chosen_option \u002F acceptance_criteria が混入する\n可能性があるため、HTML 出力時は **`--with-redaction` flag を必ず使用** すること:\n\n```bash\nbash scripts\u002Frender-html.sh --template accept ... --with-redaction\n```\n\n詳細は `.claude\u002Frules\u002Fcross-repo-handoff.md` の「Phase 65.3 実装決定事項 (D43)」を参照。\n\n### Step 3: 過去の問題パターンを取得 (Phase 65.2.2 委譲)\n\n```bash\nbash scripts\u002Faccept-past-issues.sh --project \"$PROJECT_NAME\" --task \"$USER_REQUEST\" > \"$PAST_ISSUES_JSON\"\n```\n\nこのスクリプトは patterns.md (P1-P33) と過去の `acceptance-context.v1` record を semantic search し、\n最大 3 件の `past-issue.v1` を返す。各々 `verified_in_current_task: bool` 付き。\n\n### Step 4: verified_criteria を組み立てる\n\nPlan Brief 時の acceptance_criteria 各項目について、現タスクの状態を評価する。\nユーザー (もしくは Claude) が「verify した evidence」を提示し、`evidence` 文字列を埋める。\n\n`evidence` が空文字列の場合、HTML 上で警告表示される (DoD c)。\n\nTDD が必要な task では、Acceptance Demo に `TDD verified: yes|no` の 1 行を必ず出す。\nTDD 不要または skip の場合は `TDD verified: not-required` または `TDD verified: skip:\u003Creason>` と表示する。\n`yes` にできるのは `.claude\u002Fstate\u002Ftdd-red-log\u002F\u003Ctask-id>.jsonl` の Red 証跡、または literal failing test output が確認できる時だけ。\n\n### Step 5: recommendation を算出する\n\n上記「Recommendation 算出ロジック」に従って ship \u002F wait \u002F reject を決定する。\n\n### Step 6: HTML を生成する\n\n`scripts\u002Frender-html.sh` (Phase 65.1.1) を `templates\u002Fhtml\u002Faccept.html.template` で呼ぶ:\n\n```bash\nbash scripts\u002Frender-html.sh \\\n  --template accept \\\n  --data \"$CONTEXT_JSON\" \\\n  --out \"$HTML_OUT\"\n```\n\n### Step 7: ブラウザで自動 open する\n\n`scripts\u002Fplan-brief-open.sh` (Phase 65.1.2 で導入された **汎用 OS dispatcher**) を再利用:\n\n```bash\nbash scripts\u002Fplan-brief-open.sh \"$HTML_OUT\"\n```\n\n> **注**: スクリプト名に「plan-brief」が入っているが、実体は OS 別 browser open dispatcher で kind 中立。\n> Phase 65.1.2 で先に導入されたため historical name。Layer 3 (HTML 直前最終 scan) 等の他用途でも再利用される。\n> `BROWSER=true` の env が設定されている場合 (CI 環境)、open は **skip** され `printf` で path だけ出力する。\n\n### Step 8: ユーザー判断待ち\n\n「ship \u002F wait \u002F reject の recommendation を採用するか、override するか」を確認する。\n判断後の memory write は別スキル (`accept-record-decision.sh`、Phase 65.2.3) の責務。\n\n## 失敗時の挙動\n\n| 失敗                                    | 挙動                                                                       |\n| --------------------------------------- | -------------------------------------------------------------------------- |\n| `mcp__harness__harness_mem_search` 不達 | 警告を表示し、`verified_criteria` を空配列で続行 (recommendation = reject) |\n| Plan Brief 側 record が見つからない     | warning を出し、`verified_criteria` を空配列で続行                         |\n| `git rev-parse --show-toplevel` 失敗    | `PROJECT_NAME=current` で続行                                              |\n| `accept-past-issues.sh` 失敗            | `past_issue_patterns: []` で続行 (best-effort)                             |\n| `render-html.sh` 失敗                   | エラーを stderr に出力し exit 1                                            |\n\n## Related\n\n- `harness-plan-brief` (Phase 65.1.2) — 計画段階の対構造スキル。本スキルは Plan Brief 時の `personal-preference.v1` を `user_request_hash` で join して read\n- `scripts\u002Faccept-past-issues.sh` (Phase 65.2.2) — 過去の問題パターン取得 (read side)\n- `scripts\u002Faccept-record-decision.sh` (Phase 65.2.3) — 承認 memory write (`acceptance-decision.v1`)\n- `scripts\u002Frender-html.sh` (Phase 65.1.1) — HTML テンプレートエンジン\n- `scripts\u002Fplan-brief-open.sh` (Phase 65.1.2) — 汎用 OS browser dispatcher\n- `harness-progress` skill (Phase 65.4.1) — 進行管理スキル (3 surface のうち真ん中)\n","# harness-accept\n\n非エンジニアの発注者・プロデューサー職向けに、実装完了タスクの受け入れ判断 (ship \u002F wait \u002F reject) を **HTML 1 枚** で提示するスキル。\n発注者の認知負荷ピーク (3) 受け入れ判断の段階で使う。\n\nPhase 65.1.x (`harness-plan-brief`) の対構造として動作し、Plan Brief で承認した `acceptance_criteria` を read 側で取り戻して評価する。\n\n## Quick Reference\n\n- 「**Acceptance Demo を作って**」 → このスキル\n- 「**受け入れ判断したい**」 → このスキル\n- 「**ship\u002Fwait\u002Freject 判定**」 → このスキル\n\n## 責任境界\n\n| 範囲                | このスキルの責務                                                                                   |\n| ------------------- | -------------------------------------------------------------------------------------------------- |\n| 検索                | **現プロジェクトのみ** (`project: \u003Ccurrent>`, `strict_project: true` を必ず指定)                   |\n| クロスプロジェクト  | **やらない** (Phase 65.3 以降で `--cross-project-group \u003Cname>` flag で opt-in 解放)                |\n| Plan Brief 連携     | `user_request_hash` を join key として `personal-preference.v1` (Phase 65.1.4) を read             |\n| 書き込み            | やらない (Acceptance 承認後の memory write は `accept-record-decision.sh` の責務)                  |\n| recommendation 算出 | verified \u002F 全 criteria の比率で 0.8 \u002F 0.5 閾値判定。ロジックは `scripts\u002Frender-html.sh` 直前で計算 |\n\n## 入力\n\n引数 `[task-description]` にユーザーの request を渡す (Plan Brief 時と同じ文を使う)。\n引数なしの場合は対話形式で受け取る。\n\n## 出力\n\n| 出力                    | パス                                                  | 形式                                           |\n| ----------------------- | ----------------------------------------------------- | ---------------------------------------------- |\n| Acceptance Demo HTML    | `.claude\u002Fstate\u002Fviews\u002Faccept-\u003Ctimestamp>.html`         | 単独で開ける HTML (no server, no JS framework) |\n| Acceptance context JSON | `.claude\u002Fstate\u002Fviews\u002Faccept-\u003Ctimestamp>.context.json` | `acceptance-context.v1` schema                 |\n\n## Schema: `acceptance-context.v1`\n\n```json\n{\n  \"schema\": \"acceptance-context.v1\",\n  \"user_request\": \"string\",\n  \"user_request_hash\": \"sha256 hex (Plan Brief 側の personal-preference.v1 と join)\",\n  \"demo_artifacts\": [{ \"kind\": \"video|screenshot|text\", \"path\": \"string\" }],\n  \"verified_criteria\": [{ \"name\": \"string\", \"passed\": true, \"evidence\": \"string\" }],\n  \"tdd_verified\": \"yes|no|not-required|skip:\u003Creason>\",\n  \"unverified_caveats\": [\"string\"],\n  \"past_issue_patterns\": [\n    { \"pattern_id\": \"P5\", \"title\": \"string\", \"verified_in_current_task\": true }\n  ],\n  \"recommendation\": \"ship|wait|reject\",\n  \"recommendation_evidence\": [\"string\"],\n  \"project\": \"string\",\n  \"generated_at\": \"ISO8601\"\n}\n```\n\n完全 schema は [`schemas\u002Facceptance-context.v1.schema.json`](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Facceptance-context.v1.schema.json) を参照。\n\n## Recommendation 算出ロジック\n\n```\nverified_count    = count of verified_criteria where passed=true\ntotal_criteria    = count of verified_criteria\nratio             = verified_count \u002F total_criteria  (total=0 のときは 0)\n\n  ratio >= 0.8 → \"ship\"\n  ratio >= 0.5 → \"wait\"\n  ratio \u003C  0.5 → \"reject\"\n  total = 0    → \"reject\" (criteria 0 件は判定不能、安全側 reject)\n```\n\n評価根拠は `recommendation_evidence` に literal な数値で残す。\n例: `\"verified 4 件 \u002F 全 5 件 (80%) → ship 閾値以上\"`\n\n## Execution Flow\n\nスキル起動時、Claude は以下の手順で動作する。\n\n### Step 1: project name と user_request_hash を解決\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\")\"\nUSER_REQUEST_HASH=\"$(printf '%s' \"$USER_REQUEST\" | sha256sum | awk '{print $1}')\"\n```\n\n`PROJECT_NAME` が空 (git 外) の場合は `current` をデフォルトに使う。\n\n### Step 2: harness-mem を **project-only** で検索し、Plan Brief 側 record を取得 (default)\n\n引数に `--cross-project-group \u003Cname>` flag が**ない**場合 (default behavior):\n\n`mcp__harness__harness_mem_search` を以下のパラメータで呼び出す:\n\n```\nproject: \u003CPROJECT_NAME>\nstrict_project: true\ntags: [\"personal-preference\", \"plan-brief-approval\"]\nlimit: 10\n```\n\n> **重要**: `project` パラメータは**必須**。`strict_project: true` を指定し、cross-project な検索は**絶対に行わない**。\n\n取得した record を `data.user_request_hash == \u003CUSER_REQUEST_HASH>` でフィルタし、最も新しい 1 件を選ぶ。\nこれが Plan Brief 時の承認内容 (chosen_option \u002F acceptance_criteria 等) を保持している。\n\n### Step 2 (alt): cross-project search (Phase 65.3.5 opt-in)\n\n引数に `--cross-project-group \u003Cname>` flag が**ある**場合のみ、横断 group 内の他プロジェクトでの\n類似 plan-brief-approval \u002F acceptance-decision 履歴を取得する (D43 Option α):\n\n```bash\nMEMBERS_JSON=\"$(bash scripts\u002Fload-cross-project-groups.sh --group \"\u003Cname>\" 2>\u002Fdev\u002Fnull)\" || {\n  echo \"ERROR: cross-project group not found: \u003Cname>\" >&2\n  exit 1\n}\n```\n\n`MEMBERS_JSON` が `[]` の場合は default の単一 project search に fallback。\n\n`MEMBERS_JSON` が非空の場合、各 member project ごとに MCP search を 1 回発行:\n\n```\nfor each project in MEMBERS_JSON:\n  mcp__harness__harness_mem_search(\n    project: \u003Cmember>,\n    strict_project: true,\n    tags: [\"personal-preference\", \"plan-brief-approval\"],\n    limit: 10\n  )\n```\n\n結果を client 側でマージし、`data.user_request_hash == \u003CUSER_REQUEST_HASH>` でフィルタ。\nhash 一致は基本的に同一 user request 由来のため複数 project での重複は稀だが、念のため id 単位で dedupe。\n\ncross-project 由来の record を採用すると過去他案件の chosen_option \u002F acceptance_criteria が混入する\n可能性があるため、HTML 出力時は **`--with-redaction` flag を必ず使用** すること:\n\n```bash\nbash scripts\u002Frender-html.sh --template accept ... --with-redaction\n```\n\n詳細は `.claude\u002Frules\u002Fcross-repo-handoff.md` の「Phase 65.3 実装決定事項 (D43)」を参照。\n\n### Step 3: 過去の問題パターンを取得 (Phase 65.2.2 委譲)\n\n```bash\nbash scripts\u002Faccept-past-issues.sh --project \"$PROJECT_NAME\" --task \"$USER_REQUEST\" > \"$PAST_ISSUES_JSON\"\n```\n\nこのスクリプトは patterns.md (P1-P33) と過去の `acceptance-context.v1` record を semantic search し、\n最大 3 件の `past-issue.v1` を返す。各々 `verified_in_current_task: bool` 付き。\n\n### Step 4: verified_criteria を組み立てる\n\nPlan Brief 時の acceptance_criteria 各項目について、現タスクの状態を評価する。\nユーザー (もしくは Claude) が「verify した evidence」を提示し、`evidence` 文字列を埋める。\n\n`evidence` が空文字列の場合、HTML 上で警告表示される (DoD c)。\n\nTDD が必要な task では、Acceptance Demo に `TDD verified: yes|no` の 1 行を必ず出す。\nTDD 不要または skip の場合は `TDD verified: not-required` または `TDD verified: skip:\u003Creason>` と表示する。\n`yes` にできるのは `.claude\u002Fstate\u002Ftdd-red-log\u002F\u003Ctask-id>.jsonl` の Red 証跡、または literal failing test output が確認できる時だけ。\n\n### Step 5: recommendation を算出する\n\n上記「Recommendation 算出ロジック」に従って ship \u002F wait \u002F reject を決定する。\n\n### Step 6: HTML を生成する\n\n`scripts\u002Frender-html.sh` (Phase 65.1.1) を `templates\u002Fhtml\u002Faccept.html.template` で呼ぶ:\n\n```bash\nbash scripts\u002Frender-html.sh \\\n  --template accept \\\n  --data \"$CONTEXT_JSON\" \\\n  --out \"$HTML_OUT\"\n```\n\n### Step 7: ブラウザで自動 open する\n\n`scripts\u002Fplan-brief-open.sh` (Phase 65.1.2 で導入された **汎用 OS dispatcher**) を再利用:\n\n```bash\nbash scripts\u002Fplan-brief-open.sh \"$HTML_OUT\"\n```\n\n> **注**: スクリプト名に「plan-brief」が入っているが、実体は OS 別 browser open dispatcher で kind 中立。\n> Phase 65.1.2 で先に導入されたため historical name。Layer 3 (HTML 直前最終 scan) 等の他用途でも再利用される。\n> `BROWSER=true` の env が設定されている場合 (CI 環境)、open は **skip** され `printf` で path だけ出力する。\n\n### Step 8: ユーザー判断待ち\n\n「ship \u002F wait \u002F reject の recommendation を採用するか、override するか」を確認する。\n判断後の memory write は別スキル (`accept-record-decision.sh`、Phase 65.2.3) の責務。\n\n## 失敗時の挙動\n\n| 失敗                                    | 挙動                                                                       |\n| --------------------------------------- | -------------------------------------------------------------------------- |\n| `mcp__harness__harness_mem_search` 不達 | 警告を表示し、`verified_criteria` を空配列で続行 (recommendation = reject) |\n| Plan Brief 側 record が見つからない     | warning を出し、`verified_criteria` を空配列で続行                         |\n| `git rev-parse --show-toplevel` 失敗    | `PROJECT_NAME=current` で続行                                              |\n| `accept-past-issues.sh` 失敗            | `past_issue_patterns: []` で続行 (best-effort)                             |\n| `render-html.sh` 失敗                   | エラーを stderr に出力し exit 1                                            |\n\n## Related\n\n- `harness-plan-brief` (Phase 65.1.2) — 計画段階の対構造スキル。本スキルは Plan Brief 時の `personal-preference.v1` を `user_request_hash` で join して read\n- `scripts\u002Faccept-past-issues.sh` (Phase 65.2.2) — 過去の問題パターン取得 (read side)\n- `scripts\u002Faccept-record-decision.sh` (Phase 65.2.3) — 承認 memory write (`acceptance-decision.v1`)\n- `scripts\u002Frender-html.sh` (Phase 65.1.1) — HTML テンプレートエンジン\n- `scripts\u002Fplan-brief-open.sh` (Phase 65.1.2) — 汎用 OS browser dispatcher\n- `harness-progress` skill (Phase 65.4.1) — 進行管理スキル (3 surface のうち真ん中)\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":28,"description-en":7,"description-ja":29,"user-invocable":30},[24,25,26,27],"Read","Write","Edit","Bash","[task-description]","実装完了直後の受け入れ判断 (ship \u002F wait \u002F reject) 前に Acceptance Demo HTML を生成する。harness-plan-brief が `personal-preference.v1` で書き込んだ acceptance_criteria を `user_request_hash` 経由で取得し、各基準ごとに verified \u002F unverified を表示。`recommendation` を ship \u002F wait \u002F reject の 3 値で算出し、根拠を HTML 上で可視化する。Use when: 受け入れ判断, 受入レビュー, ship\u002Fwait\u002Freject 判定, 検収レビュー。Do NOT load for: 実装作業, code review, release。",true,"main","44656ee607735b31d88e298752f574936b85af75","agent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fharness-accept","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal","https:\u002F\u002Fgithub.com\u002FTimothy191","2026-07-24 02:57:18",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":30},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Timothy191\u002Farch-systems-portal --skill harness-accept",{"tool":43,"command":44},"bunx","bunx skills add Timothy191\u002Farch-systems-portal --skill harness-accept",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Timothy191\u002Farch-systems-portal --skill harness-accept","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fharness-accept\u002FSKILL.md",[],[51,57,63,70,77,84],{"skillNo":52,"name":53,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M79BVF4ZP6Z3GH36Y7BAAZHE","escape-skill","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-escape\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M79BVE0FF9QC71P53B18GCQ8","zz-review-empty","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-empty\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M79BVAB0TARBFRF4MCQ1T8AG","workflow-guide","Explicit helper for Cursor PM ↔ Claude Code two-agent workflow guidance. Do NOT load for: solo implementation, workflow setup, handoff execution, or general process coaching.","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fworkflow-guide\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M79BV634WBDSVR8DXAHMHA19","vibecoder-guide","Explicit helper for non-technical VibeCoder coaching: what to ask next, how to describe work, and how to stay safe. Do NOT load for: direct implementation, technical review, or Cursor\u002FPM workflow.","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fvibecoder-guide\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M79BV2G6901RYQGBT3QWDK64","ui","Explicit helper for UI components, hero sections, forms, feedback, and contact surfaces. Do NOT load for: authentication, backend implementation, database work, or business logic.","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fui\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M79BTW2QT48HNNS9NCKE8PAH","session","Unified session management window. Handles initialization, memory, state all-in-one. Explicit \u002Fsession invocation only — sub-skills handle auto-delegation. Use when managing Claude Code sessions, \u002Fsession command. Do NOT load for: app user sessions, login state, authentication features.","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fsession\u002FSKILL.md",[],[]]