[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4TQPF4R1QXJNXCZS53CVM":3,"skill-same:01M6C4TQPF4R1QXJNXCZS53CVM":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":26,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":70,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":88},"01M6C4TQPF4R1QXJNXCZS53CVM","harness-plan-brief",null,"Generate a Plan Brief HTML for non-engineer vibecoders before implementation starts. Searches harness-mem (project-only) for relevant past decisions, patterns, and Plans archive entries, then renders a single-file HTML artifact summarizing understanding, options, risks, acceptance criteria, and confidence. Use when the user requests a planning preview, a non-engineer-friendly summary before approval, or says: plan brief, planning preview, 計画概要, 計画レビュー. Do NOT load for: actual implementation, code review, release work.","Chachamaru127\u002Fclaude-code-harness","Chachamaru127","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96473544?v=4","01M6C4N084DDDEK9SJPGFG9H9M","Chachamaru","01M6C4N0CCNFST9P8C7EJNVH42",3209,"MIT","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fharness-plan-brief\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"harness","brief","plan","harness plan","harness plan brief","decisions","when","html artifact","relevant","render","project","preview","engineer","only","schema","single-file","use","code review","decision","生成","archive","Bash","open","file","acceptance","planning","code","review","2026-11-10 10:12:30",false,"---\nname: harness-plan-brief\ndescription: \"Generate a Plan Brief HTML for non-engineer vibecoders before implementation starts. Searches harness-mem (project-only) for relevant past decisions, patterns, and Plans archive entries, then renders a single-file HTML artifact summarizing understanding, options, risks, acceptance criteria, and confidence. Use when the user requests a planning preview, a non-engineer-friendly summary before approval, or says: plan brief, planning preview, 計画概要, 計画レビュー. Do NOT load for: actual implementation, code review, release work.\"\ndescription-en: \"Generate a Plan Brief HTML for non-engineer vibecoders before implementation starts. Searches harness-mem (project-only) for relevant past decisions, patterns, and Plans archive entries, then renders a single-file HTML artifact summarizing understanding, options, risks, acceptance criteria, and confidence. Use when the user requests a planning preview, a non-engineer-friendly summary before approval, or says: plan brief, planning preview, 計画概要, 計画レビュー. Do NOT load for: actual implementation, code review, release work.\"\ndescription-ja: \"実装着手前に Plan Brief HTML を生成する。現プロジェクトのみで harness-mem を検索し (`strict_project: true`)、過去 decision \u002F pattern \u002F Plans archive から類似案件を抽出して `plan-brief-context.v1` schema に整形、`render-html.sh` で単独 HTML を生成しブラウザ自動 open する。Use when: 計画概要, 非エンジニア向け事前共有, 提案前 review。Do NOT load for: 実装作業, code review, release。\"\nallowed-tools: [\"Read\", \"Write\", \"Edit\", \"Bash\"]\nargument-hint: \"[task-description]\"\nuser-invocable: true\n---\n\n# harness-plan-brief\n\n非エンジニアの発注者・プロデューサー職向けに、Claude が着手しようとしている計画を **HTML 1 枚** で提示するスキル。\n発注者の認知負荷ピーク (1) 計画理解の段階で使う。\n\n## Quick Reference\n\n- 「**Plan Brief を作って**」 → このスキル\n- 「**実装前にざっくり整理**」 → このスキル\n- 「**非エンジニア向けに計画を見せて**」 → このスキル\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 承認後の memory write は `plan-brief-record-decision.sh` の責務) |\n| plan_readiness 算出 | `scripts\u002Fplan-brief-compile.sh` に委譲。互換フィールド名 `confidence` は残すが、意味は DoD 明確度 + 依存解決率に限定 |\n\n## 入力\n\n引数 `[task-description]` にユーザーの request を渡す。\n引数なしの場合は、会話の原依頼と選択済み計画から回収する。複数の候補が残って判断を変える場合だけ確認する。\n計画の目的、担当範囲、未決事項と合格条件を示し、計画概要の作成依頼から実装を始めない。\n\n## 出力\n\n| 出力 | パス | 形式 |\n|------|------|------|\n| Plan Brief HTML | `.claude\u002Fstate\u002Fviews\u002Fplan-brief-\u003Ctimestamp>.html` | 単独で開ける HTML (no server, no JS framework) |\n| Plan Brief context JSON | `.claude\u002Fstate\u002Fviews\u002Fplan-brief-\u003Ctimestamp>.context.json` | `plan-brief-context.v1` schema |\n\n## Schema: `plan-brief-context.v1`\n\n```json\n{\n  \"schema\": \"plan-brief-context.v1\",\n  \"user_request\": \"string (ユーザーの request 原文)\",\n  \"my_understanding\": \"string (Claude の理解を 1-3 段落で)\",\n  \"options\": [\n    { \"name\": \"string\", \"summary\": \"string\", \"pros\": [\"string\"], \"cons\": [\"string\"] }\n  ],\n  \"risks\": [\n    { \"kind\": \"string\", \"severity\": \"info|warn|critical\", \"description\": \"string\", \"mitigation\": \"string\" }\n  ],\n  \"acceptance_criteria\": [\n    { \"id\": \"string\", \"description\": \"string\", \"verifiable_by\": \"string\" }\n  ],\n  \"tdd_required\": \"yes|no|skip:\u003Creason>\",\n  \"confidence\": 0,\n  \"confidence_evidence\": [\"string (plan_readiness evidence: DoD clarity + dependency resolution only)\"],\n  \"related_decisions\": [\n    { \"id\": \"string\", \"title\": \"string\", \"relevance\": \"string\" }\n  ],\n  \"similar_past_plans\": [\n    { \"archive_path\": \"string\", \"phase\": \"string\", \"outcome\": \"cc:完了|cc:WIP|cc:TODO|skipped\", \"relevance\": \"string\" }\n  ],\n  \"project\": \"string\",\n  \"generated_at\": \"ISO8601\"\n}\n```\n\n完全 schema は [`schemas\u002Fplan-brief-context.v1.schema.json`](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Fplan-brief-context.v1.schema.json) を参照。\n\n## Execution Flow\n\nスキル起動時、Claude は以下の手順で動作する。\n\n### Step 1: project name を解決\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\")\"\n```\n\n`PROJECT_NAME` が空 (git 外) の場合は `current` をデフォルトに使う。\n\n### Step 2: harness-mem を **project-only** で検索する (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\nquery: \u003Cuser request>\nexpand_links: true\nlimit: 5\n```\n\n> **重要**: `project` パラメータは**必須**。空文字列や `null` を渡してはならない。\n> `strict_project: true` を指定し、cross-project な検索は**絶対に行わない**。\n> 必要なら `tags` filter で `decision` \u002F `pattern` を絞ってもよいが、`project` は固定。\n\n過去 decision (D1-D41) \u002F pattern (P1-P33) \u002F Plans archive 28 件から類似案件を最大 5 件取得する。\n\n### Step 2 (alt): cross-project search (Phase 65.3.5 opt-in)\n\n引数に `--cross-project-group \u003Cname>` flag が**ある**場合のみ:\n\nD43 Option α (MCP N-call) に従い、以下の手順で cross-project 検索を行う。\n\n```bash\n# (a) group → member projects に解決 (yaml SSOT)\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# MEMBERS_JSON は [\"proj1\",\"proj2\",...] 形式の JSON 配列\n```\n\n`MEMBERS_JSON` が `[]` (空配列) の場合は warning を出して 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    query: \u003Cuser request>,\n    expand_links: true,\n    limit: 5\n  )\n```\n\n各 search 結果を **client 側でマージ・dedupe (id 単位)・relevance_score 降順 sort** し、最大 5 件に絞る。\n合計呼び出し数が多くなる (group が 5 project なら 5 回) ため、レイテンシは増える点に注意。\n\n> **D43 判断 1 の根拠**: MCP tool schema には `projects: [array]` も `strict_project: false` も\n> exposed されていないため、横断検索は client 側 N-call が唯一の選択肢。\n> 詳細は `.claude\u002Frules\u002Fcross-repo-handoff.md` の「Phase 65.3 実装決定事項 (D43)」参照。\n\ncross-project 結果には Layer 2\u002F3 (Phase 65.3.2-65.3.4) の redaction を必ず通すこと:\n- HTML レンダリング時に `bash scripts\u002Frender-html.sh ... --with-redaction` を使用\n- これにより辞書 + NER + final scan の 3 段で固有名詞が漏れない\n\n### Step 3: context JSON を組み立てる\n\n`scripts\u002Fplan-brief-compile.sh` を使って、mem search 結果から\n`plan-brief-context.v1` schema 準拠の JSON を構築する。\n\nPhase 105.3 以降、Plan Brief の `confidence` は後方互換のフィールド名であり、\n表示上の意味は `plan_readiness` として扱う。算出軸は次の 2 つだけに固定する。\n\n- DoD 明確度: request \u002F DoD に機械検証できる数値・条件がどれだけ含まれるか\n- 依存解決率: 類似 Plans のうち依存が完了済みとして扱えるものの割合\n\n過去類似案件の成功率や関連 Decision \u002F Pattern 件数は context-only の根拠として表示し、\nreadiness 点数へ別軸加算しない。これは「AI の理解度」「成功確率」と誤読されるのを避けるため。\n\n`options` \u002F `risks` \u002F `acceptance_criteria` は常に 1 件以上生成する。\nmem search が空でも、以下を最低限埋める。\n\n- `options`: 推奨案を 1 件以上。必要なら代替案を追加し、pros \u002F cons を付ける\n- `risks`: readiness 誤読、scope creep、未観測データなど今回の計画固有リスクを 1 件以上\n- `acceptance_criteria`: 実行後に機械検証または目視確認できる条件を 1 件以上\n\n例:\n\n```bash\njq -n \\\n  --arg req \"$USER_REQUEST\" \\\n  --arg proj \"$PROJECT_NAME\" \\\n  --arg ts \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\" \\\n  '{\n    schema: \"plan-brief-context.v1\",\n    user_request: $req,\n    my_understanding: \"(まだ未着手)\",\n    options: [{name:\"Option A: 最小検証で進める\", summary:\"DoD と依存を先に確認してから実装\", pros:[\"影響が小さい\"], cons:[\"大きな再設計は別タスク化が必要\"]}],\n    risks: [{kind:\"readiness-misread\", severity:\"warn\", description:\"plan_readiness を AI の理解度として誤読するリスク\", mitigation:\"DoD 明確度 + 依存解決率だけの指標として evidence に明記\"}],\n    acceptance_criteria: [{id:\"AC-1\", description:\"Plan Brief context が非空の options \u002F risks \u002F acceptance_criteria を含む\", verifiable_by:\"tests\u002Ftest-plan-brief-compile.sh\"}],\n    confidence: 0,\n    confidence_evidence: [\"plan_readiness DoD 明確度: 0\u002F60\", \"plan_readiness 依存解決率: 0\u002F40\"],\n    tdd_required: \"no\",\n    related_decisions: [],\n    similar_past_plans: [],\n    project: $proj,\n    generated_at: $ts\n  }' > \"$CONTEXT_JSON\"\n```\n\n### Step 4: HTML を生成する\n\n`scripts\u002Frender-html.sh` (Phase 65.1.1) を `templates\u002Fhtml\u002Fplan-brief.html.template` で呼ぶ:\n\nHTML には TDD 判定を 1 行で表示する。\n形式は `tdd_required: yes`、`tdd_required: no`、または `tdd_required: skip:\u003Creason>` のいずれかにする。\n\n```bash\nbash scripts\u002Frender-html.sh \\\n  --template plan-brief \\\n  --data \"$CONTEXT_JSON\" \\\n  --out \"$HTML_OUT\"\n```\n\n`diagram-design` skill がインストールされていれば図の描画に使う。無ければ静的レイアウトのまま。\n\n### Step 5: ブラウザで自動 open する\n\n`scripts\u002Fplan-brief-open.sh` で OS 別 dispatch:\n\n```bash\nbash scripts\u002Fplan-brief-open.sh \"$HTML_OUT\"\n```\n\n`BROWSER=true` の env が設定されている場合 (CI 環境)、open は **skip** され `printf` で path だけ出力する。\n\n### Step 6: ユーザー承認待ち\n\n「この理解で実装に進んでよいか」を確認する。\n承認後の memory write は別スキル (Phase 65.1.4 の `plan-brief-record-decision.sh`) の責務。\n\n## 失敗時の挙動\n\n| 失敗 | 挙動 |\n|------|------|\n| `mcp__harness__harness_mem_search` 不達 | 警告を表示し、`related_decisions` \u002F `similar_past_plans` を空配列で続行 |\n| `git rev-parse --show-toplevel` 失敗 | `PROJECT_NAME=current` で続行 |\n| `render-html.sh` 失敗 | エラーを stderr に出力し exit 1 |\n| `plan-brief-open.sh` 失敗 | HTML path を stdout に出力するだけで exit 0 (browser open は best-effort) |\n\n## Related\n\n- `scripts\u002Frender-html.sh` (Phase 65.1.1) — HTML テンプレートエンジン\n- `scripts\u002Fplan-brief-compile.sh` (Phase 65.1.3) — context compilation\n- `scripts\u002Fplan-brief-record-decision.sh` (Phase 65.1.4) — 承認 memory write\n- `harness-accept` skill (Phase 65.2.1) — 受け入れ判断スキル (対構造)\n- `harness-progress` skill (Phase 65.4.1) — 進行管理スキル (対構造)\n","# harness-plan-brief\n\n非エンジニアの発注者・プロデューサー職向けに、Claude が着手しようとしている計画を **HTML 1 枚** で提示するスキル。\n発注者の認知負荷ピーク (1) 計画理解の段階で使う。\n\n## Quick Reference\n\n- 「**Plan Brief を作って**」 → このスキル\n- 「**実装前にざっくり整理**」 → このスキル\n- 「**非エンジニア向けに計画を見せて**」 → このスキル\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 承認後の memory write は `plan-brief-record-decision.sh` の責務) |\n| plan_readiness 算出 | `scripts\u002Fplan-brief-compile.sh` に委譲。互換フィールド名 `confidence` は残すが、意味は DoD 明確度 + 依存解決率に限定 |\n\n## 入力\n\n引数 `[task-description]` にユーザーの request を渡す。\n引数なしの場合は、会話の原依頼と選択済み計画から回収する。複数の候補が残って判断を変える場合だけ確認する。\n計画の目的、担当範囲、未決事項と合格条件を示し、計画概要の作成依頼から実装を始めない。\n\n## 出力\n\n| 出力 | パス | 形式 |\n|------|------|------|\n| Plan Brief HTML | `.claude\u002Fstate\u002Fviews\u002Fplan-brief-\u003Ctimestamp>.html` | 単独で開ける HTML (no server, no JS framework) |\n| Plan Brief context JSON | `.claude\u002Fstate\u002Fviews\u002Fplan-brief-\u003Ctimestamp>.context.json` | `plan-brief-context.v1` schema |\n\n## Schema: `plan-brief-context.v1`\n\n```json\n{\n  \"schema\": \"plan-brief-context.v1\",\n  \"user_request\": \"string (ユーザーの request 原文)\",\n  \"my_understanding\": \"string (Claude の理解を 1-3 段落で)\",\n  \"options\": [\n    { \"name\": \"string\", \"summary\": \"string\", \"pros\": [\"string\"], \"cons\": [\"string\"] }\n  ],\n  \"risks\": [\n    { \"kind\": \"string\", \"severity\": \"info|warn|critical\", \"description\": \"string\", \"mitigation\": \"string\" }\n  ],\n  \"acceptance_criteria\": [\n    { \"id\": \"string\", \"description\": \"string\", \"verifiable_by\": \"string\" }\n  ],\n  \"tdd_required\": \"yes|no|skip:\u003Creason>\",\n  \"confidence\": 0,\n  \"confidence_evidence\": [\"string (plan_readiness evidence: DoD clarity + dependency resolution only)\"],\n  \"related_decisions\": [\n    { \"id\": \"string\", \"title\": \"string\", \"relevance\": \"string\" }\n  ],\n  \"similar_past_plans\": [\n    { \"archive_path\": \"string\", \"phase\": \"string\", \"outcome\": \"cc:完了|cc:WIP|cc:TODO|skipped\", \"relevance\": \"string\" }\n  ],\n  \"project\": \"string\",\n  \"generated_at\": \"ISO8601\"\n}\n```\n\n完全 schema は [`schemas\u002Fplan-brief-context.v1.schema.json`](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Fplan-brief-context.v1.schema.json) を参照。\n\n## Execution Flow\n\nスキル起動時、Claude は以下の手順で動作する。\n\n### Step 1: project name を解決\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\")\"\n```\n\n`PROJECT_NAME` が空 (git 外) の場合は `current` をデフォルトに使う。\n\n### Step 2: harness-mem を **project-only** で検索する (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\nquery: \u003Cuser request>\nexpand_links: true\nlimit: 5\n```\n\n> **重要**: `project` パラメータは**必須**。空文字列や `null` を渡してはならない。\n> `strict_project: true` を指定し、cross-project な検索は**絶対に行わない**。\n> 必要なら `tags` filter で `decision` \u002F `pattern` を絞ってもよいが、`project` は固定。\n\n過去 decision (D1-D41) \u002F pattern (P1-P33) \u002F Plans archive 28 件から類似案件を最大 5 件取得する。\n\n### Step 2 (alt): cross-project search (Phase 65.3.5 opt-in)\n\n引数に `--cross-project-group \u003Cname>` flag が**ある**場合のみ:\n\nD43 Option α (MCP N-call) に従い、以下の手順で cross-project 検索を行う。\n\n```bash\n# (a) group → member projects に解決 (yaml SSOT)\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# MEMBERS_JSON は [\"proj1\",\"proj2\",...] 形式の JSON 配列\n```\n\n`MEMBERS_JSON` が `[]` (空配列) の場合は warning を出して 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    query: \u003Cuser request>,\n    expand_links: true,\n    limit: 5\n  )\n```\n\n各 search 結果を **client 側でマージ・dedupe (id 単位)・relevance_score 降順 sort** し、最大 5 件に絞る。\n合計呼び出し数が多くなる (group が 5 project なら 5 回) ため、レイテンシは増える点に注意。\n\n> **D43 判断 1 の根拠**: MCP tool schema には `projects: [array]` も `strict_project: false` も\n> exposed されていないため、横断検索は client 側 N-call が唯一の選択肢。\n> 詳細は `.claude\u002Frules\u002Fcross-repo-handoff.md` の「Phase 65.3 実装決定事項 (D43)」参照。\n\ncross-project 結果には Layer 2\u002F3 (Phase 65.3.2-65.3.4) の redaction を必ず通すこと:\n- HTML レンダリング時に `bash scripts\u002Frender-html.sh ... --with-redaction` を使用\n- これにより辞書 + NER + final scan の 3 段で固有名詞が漏れない\n\n### Step 3: context JSON を組み立てる\n\n`scripts\u002Fplan-brief-compile.sh` を使って、mem search 結果から\n`plan-brief-context.v1` schema 準拠の JSON を構築する。\n\nPhase 105.3 以降、Plan Brief の `confidence` は後方互換のフィールド名であり、\n表示上の意味は `plan_readiness` として扱う。算出軸は次の 2 つだけに固定する。\n\n- DoD 明確度: request \u002F DoD に機械検証できる数値・条件がどれだけ含まれるか\n- 依存解決率: 類似 Plans のうち依存が完了済みとして扱えるものの割合\n\n過去類似案件の成功率や関連 Decision \u002F Pattern 件数は context-only の根拠として表示し、\nreadiness 点数へ別軸加算しない。これは「AI の理解度」「成功確率」と誤読されるのを避けるため。\n\n`options` \u002F `risks` \u002F `acceptance_criteria` は常に 1 件以上生成する。\nmem search が空でも、以下を最低限埋める。\n\n- `options`: 推奨案を 1 件以上。必要なら代替案を追加し、pros \u002F cons を付ける\n- `risks`: readiness 誤読、scope creep、未観測データなど今回の計画固有リスクを 1 件以上\n- `acceptance_criteria`: 実行後に機械検証または目視確認できる条件を 1 件以上\n\n例:\n\n```bash\njq -n \\\n  --arg req \"$USER_REQUEST\" \\\n  --arg proj \"$PROJECT_NAME\" \\\n  --arg ts \"$(date -u +%Y-%m-%dT%H:%M:%SZ)\" \\\n  '{\n    schema: \"plan-brief-context.v1\",\n    user_request: $req,\n    my_understanding: \"(まだ未着手)\",\n    options: [{name:\"Option A: 最小検証で進める\", summary:\"DoD と依存を先に確認してから実装\", pros:[\"影響が小さい\"], cons:[\"大きな再設計は別タスク化が必要\"]}],\n    risks: [{kind:\"readiness-misread\", severity:\"warn\", description:\"plan_readiness を AI の理解度として誤読するリスク\", mitigation:\"DoD 明確度 + 依存解決率だけの指標として evidence に明記\"}],\n    acceptance_criteria: [{id:\"AC-1\", description:\"Plan Brief context が非空の options \u002F risks \u002F acceptance_criteria を含む\", verifiable_by:\"tests\u002Ftest-plan-brief-compile.sh\"}],\n    confidence: 0,\n    confidence_evidence: [\"plan_readiness DoD 明確度: 0\u002F60\", \"plan_readiness 依存解決率: 0\u002F40\"],\n    tdd_required: \"no\",\n    related_decisions: [],\n    similar_past_plans: [],\n    project: $proj,\n    generated_at: $ts\n  }' > \"$CONTEXT_JSON\"\n```\n\n### Step 4: HTML を生成する\n\n`scripts\u002Frender-html.sh` (Phase 65.1.1) を `templates\u002Fhtml\u002Fplan-brief.html.template` で呼ぶ:\n\nHTML には TDD 判定を 1 行で表示する。\n形式は `tdd_required: yes`、`tdd_required: no`、または `tdd_required: skip:\u003Creason>` のいずれかにする。\n\n```bash\nbash scripts\u002Frender-html.sh \\\n  --template plan-brief \\\n  --data \"$CONTEXT_JSON\" \\\n  --out \"$HTML_OUT\"\n```\n\n`diagram-design` skill がインストールされていれば図の描画に使う。無ければ静的レイアウトのまま。\n\n### Step 5: ブラウザで自動 open する\n\n`scripts\u002Fplan-brief-open.sh` で OS 別 dispatch:\n\n```bash\nbash scripts\u002Fplan-brief-open.sh \"$HTML_OUT\"\n```\n\n`BROWSER=true` の env が設定されている場合 (CI 環境)、open は **skip** され `printf` で path だけ出力する。\n\n### Step 6: ユーザー承認待ち\n\n「この理解で実装に進んでよいか」を確認する。\n承認後の memory write は別スキル (Phase 65.1.4 の `plan-brief-record-decision.sh`) の責務。\n\n## 失敗時の挙動\n\n| 失敗 | 挙動 |\n|------|------|\n| `mcp__harness__harness_mem_search` 不達 | 警告を表示し、`related_decisions` \u002F `similar_past_plans` を空配列で続行 |\n| `git rev-parse --show-toplevel` 失敗 | `PROJECT_NAME=current` で続行 |\n| `render-html.sh` 失敗 | エラーを stderr に出力し exit 1 |\n| `plan-brief-open.sh` 失敗 | HTML path を stdout に出力するだけで exit 0 (browser open は best-effort) |\n\n## Related\n\n- `scripts\u002Frender-html.sh` (Phase 65.1.1) — HTML テンプレートエンジン\n- `scripts\u002Fplan-brief-compile.sh` (Phase 65.1.3) — context compilation\n- `scripts\u002Fplan-brief-record-decision.sh` (Phase 65.1.4) — 承認 memory write\n- `harness-accept` skill (Phase 65.2.1) — 受け入れ判断スキル (対構造)\n- `harness-progress` skill (Phase 65.4.1) — 進行管理スキル (対構造)\n",{"name":5,"description":7,"allowed-tools":60,"argument-hint":64,"description-en":7,"description-ja":65,"user-invocable":66},[61,62,63,48],"Read","Write","Edit","[task-description]","実装着手前に Plan Brief HTML を生成する。現プロジェクトのみで harness-mem を検索し (`strict_project: true`)、過去 decision \u002F pattern \u002F Plans archive から類似案件を抽出して `plan-brief-context.v1` schema に整形、`render-html.sh` で単独 HTML を生成しブラウザ自動 open する。Use when: 計画概要, 非エンジニア向け事前共有, 提案前 review。Do NOT load for: 実装作業, code review, release。",true,"main","c2304c325d4432f51d632e0586d886767b0f41ea","skills\u002Fharness-plan-brief",306,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness","https:\u002F\u002Fgithub.com\u002FChachamaru127","https:\u002F\u002Fcanai.jp\u002F","Going all-in on the AI business from April 2025\r\nOSS release: 3k Stars\r\nAI adoption starting with \"I want\"\r\nAX Support | Tokenomics | AISDR |","2026-11-11 17:18:34",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":66},[78,81,84],{"tool":79,"command":80},"npx","npx skills add Chachamaru127\u002Fclaude-code-harness --skill harness-plan-brief",{"tool":82,"command":83},"bunx","bunx skills add Chachamaru127\u002Fclaude-code-harness --skill harness-plan-brief",{"tool":85,"command":86},"pnpm","pnpm dlx skills add Chachamaru127\u002Fclaude-code-harness --skill harness-plan-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fharness-plan-brief\u002FSKILL.md",[89,95],{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"reference\u002Fplaybook.md","REFERENCE","参考文档",12363,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-pytest-skill\u002Freference\u002Fplaybook.md",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"schemas\u002Fplan-brief-context.v1.schema.json",4443,"https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fharness-plan-brief\u002Fschemas\u002Fplan-brief-context.v1.schema.json",[100,116,124,141,169,193],{"skillNo":101,"name":102,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":108,"publishedAt":55},"01M6C4VZCJB9EN3KZXGNARAF6P","escape-skill","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-escape\u002FSKILL.md",[105],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[109,110,111,112,113,114,115],"escape skill","escape","Tools","false","true","path","quoted",{"skillNo":117,"name":118,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":55},"01M6C4VYAJW332S5R2MM3RNE0G","zz-review-empty","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fskills\u002Fzz-review-empty\u002FSKILL.md",[],[54,122,123,112,113],"zz review empty","empty",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":55},"01M6C4VWW4GNAZ2680GY04S3EW","session-send","This skill should be used when the user asks to notify other session, requests a session handoff, says tell other agent, or needs a cross-session message.","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fsession-send\u002FSKILL.md",[130],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[132,133,134,135,136,48,137,138,139,140,33],"session","session send","send","handoff","session handoff","user","message","notify","requests",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":148,"publishedAt":55},"01M6C4VSMYH6XQGR087HQ9Y7HT","memory","Manage SSOT, memory, and cross-tool memory search. Guardian of decisions.md and patterns.md. Use when user mentions memory, SSOT, decisions.md, patterns.md, merging, migration, SSOT promotion, sync memory, save learnings, memory search, harness-mem, past decisions, or record this. Do NOT load for: implementation work, reviews, ad-hoc notes, or in-session logging.","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fmemory\u002FSKILL.md",[147],{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},[143,149,150,151,27,152,153,154,48,155,156,157,32,158,159,160,137,132,43,161,162,163,164,165,166,113,167,168,33],"MCP","sync","notes","search","memory search","guardian","migrate","tool","work","read","write","edit","migration","manage","do","learnings","promotion","reviews","load","for",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":55},"01M6C4VQ3507BV9XRX4BDSES6J","maintenance","File cleanup and archiving. Tidies up bloated Plans.md, session-log.md, old logs, and state files. Trigger: \u002Fmaintenance, cleanup, archive, organize, split session-log. Do NOT load for: implementation, review, release, new feature development.","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fmaintenance\u002FSKILL.md",[],[171,54,176,177,178,179,180,50,181,48,47,182,158,159,160,183,132,184,185,186,163,187,188,189,190,191,113,167,168,192],"development","cleanup","run","release","state","logs","grep","new feature","up","log","files","feature","plans","trigger","整理","split","new",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":209,"publishedAt":55},"01M6C4VK473YJ872RNMBYK7P4R","japanese-writing-drafter","Detect when the operator corrects the agent's Japanese phrasing mid-conversation (rewrites a sentence, calls out a style problem, says 'this wording is bad, say it like X instead') and draft a pending writing-rule proposal into ~\u002F.claude\u002Fwriting-lint\u002Fproposals.jsonl for later human review. This skill is the ONLY writer of proposals.jsonl — it never edits rules.jsonl and never sets status to anything but pending. Promotion to rules.jsonl only happens via the human-run scripts\u002Fwriting-rule-approve.sh. Use when user mentions writing-rule proposal, 表現を直して, 文体を直して, その言い方はNG, writing lint 提案, 指摘をルール化して. Do NOT load for: approving or rejecting proposals (use scripts\u002Fwriting-rule-approve.sh), listing pending proposals (use scripts\u002Fwriting-rule-list.sh), or scanning text against the existing dictionary (the writinglint engine \u002F PostToolUse hook does that).","https:\u002F\u002Fgithub.com\u002FChachamaru127\u002Fclaude-code-harness\u002Fblob\u002Fmain\u002Fskills\u002Fjapanese-writing-drafter\u002FSKILL.md",[199,200,203,204],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":201,"categoryName":202,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":106,"categoryName":107,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":205,"categoryName":206,"taxonomyType":207,"taxonomyTypeDesc":208},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[210,211,212,54,213,178,214,215,48,216,217,218,219,158,220,221,43,222,40,223,224,225,226,227,228,229,230,231,232,233,33,234],"writing","japanese writing drafter","japanese","status","lint","operator","提案","text","engine","Rules","list","proposals","never","scanning","say","human review","later","conversation","writer","human","scripts","problem","proposal","jsonl","listing"]