[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79BPP7VFN2XXMS15GEK9FGS":3,"skill-same:01M79BPP7VFN2XXMS15GEK9FGS":49},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M79BPP7VFN2XXMS15GEK9FGS","harness-progress",null,"Generate a Progress Tracker HTML for non-engineer vibecoders to glance at session progress (cc:WIP \u002F cc:TODO \u002F cc:完了 counts, percentage, elapsed\u002Festimated minutes, cost so far\u002Festimate, drift alerts). Uses Plans.md as source of truth, renders a single-file HTML with auto-regeneration support. Use when user asks for progress overview, session status snapshot, dashboard, or says: progress tracker, 進捗確認, 進捗ボード, dashboard. Do NOT load for: actual 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-progress\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: harness-progress\ndescription: \"Generate a Progress Tracker HTML for non-engineer vibecoders to glance at session progress (cc:WIP \u002F cc:TODO \u002F cc:完了 counts, percentage, elapsed\u002Festimated minutes, cost so far\u002Festimate, drift alerts). Uses Plans.md as source of truth, renders a single-file HTML with auto-regeneration support. Use when user asks for progress overview, session status snapshot, dashboard, or says: progress tracker, 進捗確認, 進捗ボード, dashboard. Do NOT load for: actual implementation, code review, release work.\"\ndescription-en: \"Generate a Progress Tracker HTML for non-engineer vibecoders to glance at session progress (cc:WIP \u002F cc:TODO \u002F cc:完了 counts, percentage, elapsed\u002Festimated minutes, cost so far\u002Festimate, drift alerts). Uses Plans.md as source of truth, renders a single-file HTML with auto-regeneration support. Use when user asks for progress overview, session status snapshot, dashboard, or says: progress tracker, 進捗確認, 進捗ボード, dashboard. Do NOT load for: actual implementation, code review, release work.\"\ndescription-ja: \"進捗 Tracker HTML を生成する。Plans.md を SoT として cc:WIP \u002F cc:TODO \u002F cc:完了 件数・%、経過分数・コスト・drift alert を 1 枚 HTML で表示。PostToolUse hook で 60 秒に 1 回自動再生成。Use when: 進捗確認, 進捗ボード, dashboard。Do NOT load for: 実装作業, code review, release。\"\nallowed-tools: [\"Read\", \"Write\", \"Bash\"]\nargument-hint: \"[--out \u003Cpath>] [--no-open]\"\n---\n\n# Harness Progress Tracker\n\nPhase 65.4 (Progress Tracker) — 3rd surface of the cognitive-load HTML triplet.\nPlan Brief \u002F Acceptance Demo に続く 3 つ目の HTML surface で、**進行中セッションの全体像を 1 枚の紙で把握** できるようにする。\n\n## Quick Reference\n\n| 入力                             | 動作                                               |\n| -------------------------------- | -------------------------------------------------- |\n| `\u002Fharness-progress`              | 現プロジェクトの進捗 snapshot HTML を生成し開く    |\n| `\u002Fharness-progress --no-open`    | 生成のみ (browser 開かない、PostToolUse hook 用)   |\n| `\u002Fharness-progress --out \u003Cpath>` | 出力先指定 (default: `out\u002Fprogress-snapshot.html`) |\n\n## Mission\n\n> \"今のセッションは何件のタスクをどこまで終わらせて、いつ終わる見込みで、いくら使ったか\" を、\n> エンジニアじゃない vibecoder が **3 秒でブラウザで把握** できる HTML 1 枚を生成する。\n\n**やる**:\n\n- Plans.md の cc:TODO \u002F cc:WIP \u002F cc:完了 件数を集計\n- progress_pct (完了率) を計算 (cc:完了 ÷ 総タスク × 100)\n- 経過分数 \u002F 推定総分数 \u002F コスト so-far \u002F コスト estimate を表示\n- drift alert を表示 (Phase 65.4.3 以降で populate)\n\n**やらない** (本 cycle):\n\n- WebSocket \u002F SSE による live update (静的 HTML、再生成で更新)\n- 過去 session の history 比較 (Phase 65.4.4 で別軸)\n- 他 project の cross-project view (Phase 65.3 と独立)\n\n## Schema: progress-snapshot.v1\n\n詳細仕様: [schemas\u002Fprogress-snapshot.v1.schema.json](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Fprogress-snapshot.v1.schema.json)\n\n```yaml\nschema:        progress-snapshot.v1\nproject:       \u003Cbasename of git repo>\ncurrent_task:  \u003Ccc:WIP の最初の項目 1 行サマリ、なければ空文字>\nprogress_pct:  \u003C0-100 の整数、cc:完了 ÷ 総タスク × 100 の四捨五入>\ntodo_tasks:    [{number, title}]    ← cc:TODO のみ\nwip_tasks:     [{number, title}]    ← cc:WIP のみ\ndone_tasks:    [{number, title, commit}]   ← cc:完了 [hash] のみ、hash は 7 chars\nelapsed_minutes:          \u003Cint, state file から>\nestimated_total_minutes:  \u003Cint, state file から>\ncost_so_far_usd:          \u003Cfloat, state file から>\ncost_estimate_usd:        \u003Cfloat, state file から>\nalerts:                    []   ← Phase 65.4.3 以降で populate\ngenerated_at:             \u003CISO8601 UTC>\n```\n\n## Execution Flow\n\n### Step 0: PROJECT_NAME を取得\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\" 2>\u002Fdev\u002Fnull || echo \"current\")\"\n```\n\n### Step 1: snapshot を組み立て\n\n```bash\nSNAPSHOT_JSON=\"$(mktemp \u002Ftmp\u002Fprogress-snapshot-XXXX.json)\"\nbash scripts\u002Fprogress-snapshot.sh \\\n  --plans Plans.md \\\n  --project \"$PROJECT_NAME\" \\\n  > \"$SNAPSHOT_JSON\"\n```\n\n`scripts\u002Fprogress-snapshot.sh` (Phase 65.4.1 で実装) は Plans.md を parse し\n`progress-snapshot.v1` schema 準拠の JSON を出力する。\n\n### Step 2: HTML をレンダリング\n\n```bash\nOUT_PATH=\"${OUT_PATH:-out\u002Fprogress-snapshot.html}\"\nmkdir -p \"$(dirname \"$OUT_PATH\")\"\n\nbash scripts\u002Frender-html.sh \\\n  --template progress \\\n  --data \"$SNAPSHOT_JSON\" \\\n  --out \"$OUT_PATH\"\n```\n\n### Step 3: ブラウザで開く\n\n`--no-open` flag が**ない**場合のみ実行 (PostToolUse hook からの背景再生成では skip):\n\n```bash\nbash scripts\u002Fplan-brief-open.sh --path \"$OUT_PATH\"\n```\n\n## Cross-project search (default OFF)\n\nPhase 65.4.4 で `--cross-project-group \u003Cname>` flag が追加される。本 cycle (65.4.1) では default OFF、現プロジェクトのみ集計する。\n\n## Failure modes\n\n| 状態                           | 動作                                                                   |\n| ------------------------------ | ---------------------------------------------------------------------- |\n| Plans.md が無い                | `progress-snapshot.sh` が exit 1 (clear error message)                 |\n| Plans.md にタスクが 1 件もない | `progress_pct: 0`, 空配列 で snapshot 生成 (HTML は「タスクなし」表示) |\n| state file (経過分数等) が無い | `elapsed_minutes: 0`, `cost_so_far_usd: 0` で fallback (warning なし)  |\n| `git` 不在 \u002F git repo 外       | `project: \"current\"` で fallback                                       |\n\n## Related\n\n- `harness-plan-brief` (Phase 65.1.x) — 1st surface (実装前の説明会)\n- `harness-accept` (Phase 65.2.x) — 2nd surface (検収判断)\n- `harness-progress` (本 skill, Phase 65.4.x) — 3rd surface (進捗ダッシュボード)\n- 65.4.2 (PostToolUse auto-regen)、65.4.3 (drift alert 5 種)、65.4.4 (過去判断 lookup) で機能拡張\n","# Harness Progress Tracker\n\nPhase 65.4 (Progress Tracker) — 3rd surface of the cognitive-load HTML triplet.\nPlan Brief \u002F Acceptance Demo に続く 3 つ目の HTML surface で、**進行中セッションの全体像を 1 枚の紙で把握** できるようにする。\n\n## Quick Reference\n\n| 入力                             | 動作                                               |\n| -------------------------------- | -------------------------------------------------- |\n| `\u002Fharness-progress`              | 現プロジェクトの進捗 snapshot HTML を生成し開く    |\n| `\u002Fharness-progress --no-open`    | 生成のみ (browser 開かない、PostToolUse hook 用)   |\n| `\u002Fharness-progress --out \u003Cpath>` | 出力先指定 (default: `out\u002Fprogress-snapshot.html`) |\n\n## Mission\n\n> \"今のセッションは何件のタスクをどこまで終わらせて、いつ終わる見込みで、いくら使ったか\" を、\n> エンジニアじゃない vibecoder が **3 秒でブラウザで把握** できる HTML 1 枚を生成する。\n\n**やる**:\n\n- Plans.md の cc:TODO \u002F cc:WIP \u002F cc:完了 件数を集計\n- progress_pct (完了率) を計算 (cc:完了 ÷ 総タスク × 100)\n- 経過分数 \u002F 推定総分数 \u002F コスト so-far \u002F コスト estimate を表示\n- drift alert を表示 (Phase 65.4.3 以降で populate)\n\n**やらない** (本 cycle):\n\n- WebSocket \u002F SSE による live update (静的 HTML、再生成で更新)\n- 過去 session の history 比較 (Phase 65.4.4 で別軸)\n- 他 project の cross-project view (Phase 65.3 と独立)\n\n## Schema: progress-snapshot.v1\n\n詳細仕様: [schemas\u002Fprogress-snapshot.v1.schema.json](${CLAUDE_SKILL_DIR}\u002Fschemas\u002Fprogress-snapshot.v1.schema.json)\n\n```yaml\nschema:        progress-snapshot.v1\nproject:       \u003Cbasename of git repo>\ncurrent_task:  \u003Ccc:WIP の最初の項目 1 行サマリ、なければ空文字>\nprogress_pct:  \u003C0-100 の整数、cc:完了 ÷ 総タスク × 100 の四捨五入>\ntodo_tasks:    [{number, title}]    ← cc:TODO のみ\nwip_tasks:     [{number, title}]    ← cc:WIP のみ\ndone_tasks:    [{number, title, commit}]   ← cc:完了 [hash] のみ、hash は 7 chars\nelapsed_minutes:          \u003Cint, state file から>\nestimated_total_minutes:  \u003Cint, state file から>\ncost_so_far_usd:          \u003Cfloat, state file から>\ncost_estimate_usd:        \u003Cfloat, state file から>\nalerts:                    []   ← Phase 65.4.3 以降で populate\ngenerated_at:             \u003CISO8601 UTC>\n```\n\n## Execution Flow\n\n### Step 0: PROJECT_NAME を取得\n\n```bash\nPROJECT_NAME=\"$(basename \"$(git rev-parse --show-toplevel)\" 2>\u002Fdev\u002Fnull || echo \"current\")\"\n```\n\n### Step 1: snapshot を組み立て\n\n```bash\nSNAPSHOT_JSON=\"$(mktemp \u002Ftmp\u002Fprogress-snapshot-XXXX.json)\"\nbash scripts\u002Fprogress-snapshot.sh \\\n  --plans Plans.md \\\n  --project \"$PROJECT_NAME\" \\\n  > \"$SNAPSHOT_JSON\"\n```\n\n`scripts\u002Fprogress-snapshot.sh` (Phase 65.4.1 で実装) は Plans.md を parse し\n`progress-snapshot.v1` schema 準拠の JSON を出力する。\n\n### Step 2: HTML をレンダリング\n\n```bash\nOUT_PATH=\"${OUT_PATH:-out\u002Fprogress-snapshot.html}\"\nmkdir -p \"$(dirname \"$OUT_PATH\")\"\n\nbash scripts\u002Frender-html.sh \\\n  --template progress \\\n  --data \"$SNAPSHOT_JSON\" \\\n  --out \"$OUT_PATH\"\n```\n\n### Step 3: ブラウザで開く\n\n`--no-open` flag が**ない**場合のみ実行 (PostToolUse hook からの背景再生成では skip):\n\n```bash\nbash scripts\u002Fplan-brief-open.sh --path \"$OUT_PATH\"\n```\n\n## Cross-project search (default OFF)\n\nPhase 65.4.4 で `--cross-project-group \u003Cname>` flag が追加される。本 cycle (65.4.1) では default OFF、現プロジェクトのみ集計する。\n\n## Failure modes\n\n| 状態                           | 動作                                                                   |\n| ------------------------------ | ---------------------------------------------------------------------- |\n| Plans.md が無い                | `progress-snapshot.sh` が exit 1 (clear error message)                 |\n| Plans.md にタスクが 1 件もない | `progress_pct: 0`, 空配列 で snapshot 生成 (HTML は「タスクなし」表示) |\n| state file (経過分数等) が無い | `elapsed_minutes: 0`, `cost_so_far_usd: 0` で fallback (warning なし)  |\n| `git` 不在 \u002F git repo 外       | `project: \"current\"` で fallback                                       |\n\n## Related\n\n- `harness-plan-brief` (Phase 65.1.x) — 1st surface (実装前の説明会)\n- `harness-accept` (Phase 65.2.x) — 2nd surface (検収判断)\n- `harness-progress` (本 skill, Phase 65.4.x) — 3rd surface (進捗ダッシュボード)\n- 65.4.2 (PostToolUse auto-regen)、65.4.3 (drift alert 5 種)、65.4.4 (過去判断 lookup) で機能拡張\n",{"name":5,"description":7,"allowed-tools":23,"argument-hint":27,"description-en":7,"description-ja":28},[24,25,26],"Read","Write","Bash","[--out \u003Cpath>] [--no-open]","進捗 Tracker HTML を生成する。Plans.md を SoT として cc:WIP \u002F cc:TODO \u002F cc:完了 件数・%、経過分数・コスト・drift alert を 1 枚 HTML で表示。PostToolUse hook で 60 秒に 1 回自動再生成。Use when: 進捗確認, 進捗ボード, dashboard。Do NOT load for: 実装作業, code review, release。","main","44656ee607735b31d88e298752f574936b85af75","agent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fharness-progress","https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal","https:\u002F\u002Fgithub.com\u002FTimothy191","2026-07-24 02:57:18",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Timothy191\u002Farch-systems-portal --skill harness-progress",{"tool":41,"command":42},"bunx","bunx skills add Timothy191\u002Farch-systems-portal --skill harness-progress",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Timothy191\u002Farch-systems-portal --skill harness-progress","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTimothy191\u002Farch-systems-portal\u002Fblob\u002Fmain\u002Fagent-harnesses\u002Fclaude-code-harness\u002Fskills\u002Fharness-progress\u002FSKILL.md",true,[],[50,56,62,69,76,83],{"skillNo":51,"name":52,"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":53,"categories":54,"keywords":55,"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":57,"name":58,"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":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"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":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"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":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"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",[],[]]