{"id":51223036,"url":"https://github.com/easyinplay/harnessed","last_synced_at":"2026-06-30T00:00:22.366Z","repository":{"id":357188090,"uuid":"1235802542","full_name":"easyinplay/harnessed","owner":"easyinplay","description":"AI coding harness composition orchestrator — manifest-described upstreams, composition skill workflows. Apache-2.0.","archived":false,"fork":false,"pushed_at":"2026-06-24T00:59:15.000Z","size":7408,"stargazers_count":2,"open_issues_count":0,"forks_count":1,"subscribers_count":0,"default_branch":"main","last_synced_at":"2026-06-24T02:24:41.019Z","etag":null,"topics":["ai","claude","claude-code","claude-code-plugin","claude-skills","harness-engineering","workflow"],"latest_commit_sha":null,"homepage":"https://harnessed.cc/","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/easyinplay.png","metadata":{"files":{"readme":"README-cn.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":".github/FUNDING.yml","license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":"NOTICE","maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null},"funding":{"github":"easyinplay"}},"created_at":"2026-05-11T17:07:49.000Z","updated_at":"2026-06-24T00:59:21.000Z","dependencies_parsed_at":null,"dependency_job_id":null,"html_url":"https://github.com/easyinplay/harnessed","commit_stats":null,"previous_names":["easyinplay/harnessed"],"tags_count":124,"template":false,"template_full_name":null,"purl":"pkg:github/easyinplay/harnessed","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/easyinplay%2Fharnessed","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/easyinplay%2Fharnessed/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/easyinplay%2Fharnessed/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/easyinplay%2Fharnessed/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/easyinplay","download_url":"https://codeload.github.com/easyinplay/harnessed/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/easyinplay%2Fharnessed/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":34947088,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-06-29T02:00:05.398Z","response_time":58,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["ai","claude","claude-code","claude-code-plugin","claude-skills","harness-engineering","workflow"],"created_at":"2026-06-28T09:00:31.116Z","updated_at":"2026-06-30T00:00:22.291Z","avatar_url":"https://github.com/easyinplay.png","language":"TypeScript","funding_links":["https://github.com/sponsors/easyinplay"],"categories":["Source Catalog"],"sub_categories":[],"readme":"# harnessed\n\n[English](./README.md) | **简体中文** | [繁體中文](./README-tw.md) | [日本語](./README-ja.md) | [한국어](./README-ko.md) | [Português (Brasil)](./README-pt-BR.md) | [Türkçe](./README-tr.md) | [Русский](./README-ru.md) | [Tiếng Việt](./README-vi.md) | [ไทย](./README-th.md)\n\n\u003e AI coding harness 包管理器 + composition orchestrator\n\u003e 把三层栈协作方法论 (gstack 决策 + GSD 项目经理 + superpowers 资深工程师 + karpathy 心法 + mattpocock 招式) 编排化为可执行 engine\n\n[![npm](https://img.shields.io/npm/v/harnessed?label=npm\u0026color=blue)](https://npmjs.com/package/harnessed)\n[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](./LICENSE)\n[![Sponsor](https://img.shields.io/github/sponsors/easyinplay?logo=github\u0026label=Sponsor)](https://github.com/sponsors/easyinplay)\n\n\u003e Not affiliated with, endorsed by, or sponsored by Harness Inc. (见 [NOTICE](./NOTICE))\n\n---\n\n## ✨ 一句话定位\n\n**把原始的 Claude Code 变成一支纪律严明的资深工程团队。** 一次安装,就把治理 (governance)、规划 (planning)、TDD、审查 (review) 织进一条 Discuss→Ship 工作流 —— 进度和证据落在磁盘上,不消散在对话里。\n\n\u003e _AI coding harness 包管理器 + composition orchestrator_ —— 装配市面上最优秀的开源 Claude Code 生态组件,用强意见 composition skill 织成统一工作流;不 vendor 上游代码,通过 manifest 描述 install/check + composition skill 编排多上游协作。\n\n---\n\n\u003e 等等 — harnessed 真能跟 superpowers / gstack / GSD 这种上游 PK?\n\u003e 当然 —— 我们**站在巨人的肩膀上**,看得更远嘛。(牛顿同款 quote,没收版权费就先用着了 🧐)\n\u003e ……(小声) 不过仔细看更像肩上那只鹦鹉。\n\u003e 算了,鹦鹉学舌,我们至少**会编排**。🦜\n\n---\n\n## 🎯 关键差异化\n\n- **三层栈机器化** — `gstack 决策` + `GSD 项目经理` + `superpowers 资深工程师` + `karpathy 4 心法` + `mattpocock 23 招式`,5 支柱 100% capture\n- **不 vendor 上游** — manifest describe install/check;上游升级用户 re-install 即获最新版\n- **Composition Skill** — 自家 workflow skill 当指挥棒,调度多个上游协同。**1 super-master `/auto` + 4 stage master + 18 sub-workflow + 2 standalone = 25 namespace-layered workflow**,完整 4-stage 机器化 (`/auto` 跨 stage 一键 / `/discuss /plan /task /verify` 单 stage / 三层栈 18 sub / `/research /retro` 2 standalone)\n- **L0 Discipline Substrate** — 全局 cross-stage 行为基准 (karpathy 心法 + output-style + language + operational + priority + protocols),applied universally\n- **包管理器思维** — install dependency graph 自动解析, doctor 健康检查, install-base 一键装齐\n- **统一入口** — 用户面对 `/discuss /plan /task /verify` 等 master slash command,不需学每家上游术语;sub command 显式调用单 stage (例如 `/discuss-strategic` 只跑战略层澄清)\n\n---\n\n## 📦 快速安装\n\n```bash\nnpm install -g harnessed \u0026\u0026 harnessed setup\n```\n\n\u003e Windows PowerShell 5.x 不支持 `\u0026\u0026` 链接,需改 `;` 或分两行 (`npm install -g harnessed; harnessed setup`)。bash / zsh / PowerShell 7+ / cmd.exe 都正常。\n\n**卸载 harnessed：**\n```bash\nharnessed uninstall    # 删除 harnessed 自身文件（上游组件不受影响）\n```\n\n\u003e `harnessed uninstall` 会清理 commands、workflow skills、settings 环境变量和状态目录。上游组件（npm 包、MCP 服务器、CC 插件、git clone 仓库、npx skills）保持完整。运行 `harnessed uninstall \u003cname\u003e` 可单独移除某个上游。加 `--dry-run` 可预览。\n\n🤖 **或让 AI 帮你装** — 把下面这句话发给 Claude Code (或任何 AI 助手):\n\n\u003e 按 `https://github.com/easyinplay/harnessed/blob/main/INSTALL-WITH-AI.md` 的指导帮我装 harnessed\n\nAI 会自动 fetch 文档 + 跑安装,处理 OS / 权限 / PATH / corepack 等 edge case,无需复制大段文字。\n\n\u003e [!TIP]\n\u003e 🚀 **很多人关心的 Agent Teams 和 Subagent 功能,在 harnessed 中会根据任务自动启用!**\n\u003e 无需手动配置 `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS`,`harnessed setup` v3.3.1+ 会自动写入 `~/.claude/settings.json`;Pattern A 全栈三路 / Pattern C 4-specialist 等 multi-agent workflow 即开即用。\n\n---\n\n## 🚀 快捷使用 — 3 种选择\n\n按介入程度由低到高:\n\n### 🎯 整体自动 (推荐新手 / 不想动脑子)\n\n```\n/auto \"需求 X\"\n\n# 大需求可显式分阶段 (一般不需要如下指定 AI 自动判断进入;若自认大需求可强制):\n/auto \"需求 X\" --staged\n```\n\n\u003e 不想动脑子或者刚入门 — 一切交给 harnessed。自动跑完 6 stage (research conditional → discuss → plan → task → verify → retro mandatory),中间不停。AI 1-shot 自动判断需求复杂度,大需求建议切 `--staged` 模式 (每 stage 完停 review);开始前 prompt \"对需求清晰认知吗?\" n → 自动加跑 `/research` 多源调研;末尾 `/retro` 强制总结。失败 fail-fast,`harnessed resume` 续。\n\n### 📂 分类自动 (推荐熟手 / 想 review 中间结果)\n\n```\n/discuss \"需求 X\"          # 战略 + Phase + 子任务 3 层澄清\n/plan \"需求 X\"             # 架构 (conditional) + 计划持久化\n/task \"subtask-1\"          # 4 sub 串行 (clarify → code → test → deliver)\n/verify \"phase-1\"          # 7 sub conditional 验证\n```\n\n\u003e 想自己决定从哪个 stage 开始 / review 中间产出 — 4 个 master 独立调用,每个 master 内部仍自动 fan-out 该 stage 所有 sub。\n\n### 🔬 精确调用 (大神 mode / 知道自己要什么)\n\n```\n/discuss-phase \"...\"        # 单跑 Phase 层澄清\n/plan-architecture \"...\"    # 单跑架构审查\n/verify-paranoid \"...\"      # 单跑 Paranoid Staff Engineer 审查\n# ... 其他 18 个 sub-workflow 任选\n```\n\n\u003e \"我是大神,我自己决定\" — 跳过 master,直接调某 sub-workflow。适合已知精确需要哪个 sub 的高级用户 / 复用某单一环节。\n\n---\n\n## 📐 4-stage 流程图\n\n```mermaid\ngraph TD\n  RS([⓪ /research — 前置多源调研 可选]):::optional\n  subgraph Discuss[① Discuss 战略澄清]\n    DM[/discuss master/]\n    DS[discuss-strategic]\n    DP[discuss-phase]\n    DT[discuss-subtask]\n    DM --\u003e DS \u0026 DP \u0026 DT\n  end\n  subgraph Plan[② Plan 任务规划]\n    PM[/plan master/]\n    PA[plan-architecture]\n    PP[plan-phase]\n    PM --\u003e PA \u0026 PP\n  end\n  subgraph Task[③ Task 执行]\n    TM[/task master/]\n    TC[task-clarify]\n    TCo[task-code]\n    TT[task-test]\n    TD[task-deliver]\n    TM --\u003e TC --\u003e TCo --\u003e TT --\u003e TD\n  end\n  subgraph Verify[④ Verify 验证]\n    VMs[/verify master/]\n    VP[verify-progress]\n    VC[verify-code-review]\n    VPa[verify-paranoid]\n    VQ[verify-qa]\n    VS[verify-security]\n    VD[verify-design]\n    VSi[verify-simplify]\n    VM[verify-multispec]\n    VMs --\u003e VP \u0026 VC \u0026 VPa \u0026 VQ \u0026 VS \u0026 VD \u0026 VSi \u0026 VM\n  end\n  RT([⑤ /retro — 里程碑总结 可选]):::optional\n  RS --\u003e Discuss\n  Discuss --\u003e Plan --\u003e Task --\u003e Verify\n  Verify --\u003e RT\n  classDef optional stroke-dasharray:5 5,fill:#f5f5f5,color:#666\n```\n\n\u003e 虚框 = 可选 standalone (`/research` 战略前调研 / `/retro` 里程碑后总结);实框 = 主流程 4-stage cadence。\n\n### 25 workflow 总览表\n\n| Slash cmd | Stage | Type | Capability / Upstream | Brief |\n|-----------|-------|------|----------------------|-------|\n| `/auto` | All | **Super-master** | masterOrchestrator (跨 6 stage) | 一键自动跑 6 stage (research conditional → discuss → plan → task → verify → retro mandatory); AI 复杂度 1-shot judge + 理解度 check + retro mandatory; `--staged` opt-in stage gate |\n| `/discuss` | ① Discuss | Master | masterOrchestrator | 3 sub 并行 gate-eval (chain-isolation 铁律) |\n| `/discuss-strategic` | ① Discuss | Sub | gstack `/office-hours` + `/plan-ceo-review` + planning-with-files | 战略层 — 新功能 / 新 milestone / 产品方向强制治理 (findings.md 持久化) |\n| `/discuss-phase` | ① Discuss | Sub | GSD `/gsd-discuss-phase` + planning-with-files | Phase 层 — ≥2 open decisions / 灰色地带澄清 (findings.md + knowledge.md 持久化) |\n| `/discuss-subtask` | ① Discuss | Sub | superpowers brainstorming + `/grill-with-docs` | 子任务层 — ≥2 approach / 核心算法 / API contract (ephemeral 短讨论, 不持久化) |\n| `/plan` | ② Plan | Master | masterOrchestrator | 串行 invoke 2 sub (architecture conditional → phase always) |\n| `/plan-architecture` | ② Plan | Sub | gstack `/plan-eng-review` | 架构层 — 复杂架构强制治理关卡 |\n| `/plan-phase` | ② Plan | Sub | GSD `/gsd-plan-phase` + planning-with-files `/plan` | 计划层 — 持久化 `task_plan.md` + `progress.md` |\n| `/task` | ③ Task | Master | masterOrchestrator | 串行 invoke 4 sub per subtask (clarify → code → test → deliver) |\n| `/task-clarify` | ③ Task | Sub | superpowers brainstorming + `/grill-with-docs` conditional | 子任务起步澄清 gate |\n| `/task-code` | ③ Task | Sub | karpathy 4 心法 + `/zoom-out` / `/improve-codebase-architecture` / `/diagnose` conditional | 子任务编码 + 跨 session progress.md 同步 |\n| `/task-test` | ③ Task | Sub | superpowers TDD red-green-refactor + `/diagnose` conditional | 核心逻辑 TDD 强制 (alias mattpocock `/tdd`) |\n| `/task-deliver` | ③ Task | Sub | `ralph-loop` SDK wrapper + Agent Teams conditional | 至 verbatim `COMPLETE` + R20.10 max_iter fallback |\n| `/verify` | ④ Verify | Master | masterOrchestrator | 7 sub 按场景 conditional dispatch |\n| `/verify-progress` | ④ Verify | Sub | GSD `/gsd-verify-work` + `/gsd-progress` | 必跑串行起点 — UAT 验收 + 状态同步 |\n| `/verify-code-review` | ④ Verify | Sub | `code-review` 多 subagent fan-out | 高置信度 finding 并行 |\n| `/verify-paranoid` | ④ Verify | Sub | gstack `/review` (Paranoid Staff Engineer) | 关键模块 PR 前强制 |\n| `/verify-qa` | ④ Verify | Sub | gstack `/qa` + playwright-cli / `@playwright/test` / webapp-testing | 端到端 QA (has_ui_changes conditional) |\n| `/verify-security` | ④ Verify | Sub | gstack `/cso` | OWASP / auth / secrets (has_auth_or_secrets conditional) |\n| `/verify-design` | ④ Verify | Sub | gstack `/design-review` + ui-ux-pro-max + frontend-design | 设计系统一致性 (has_design_changes conditional) |\n| `/verify-simplify` | ④ Verify | Sub | `code-simplifier` | 末尾串行简化 |\n| `/verify-multispec` | ④ Verify | Sub | 4-specialist Agent Team Pattern C | 关键发布 / 大重构 PR 升级 (互相 SendMessage 质询) |\n| `/research` | Standalone | Standalone | Tavily / Exa MCP + ctx7 + GSD `/gsd-discuss-phase` | 多源调研 (Stage ① alternate) |\n| `/retro` | Standalone | Standalone | gstack `/retro` + planning-with-files RETROSPECTIVE.md | 项目 / 里程碑结束总结 |\n\n\u003e Master orchestrator 自动 gate-route 到合适的 sub (chain-isolation 铁律 — 不 fire 的 sub 透明声明跳过)。\n\u003e 直接调用 sub 也可绕过 master 单跑某 stage,例如 `/discuss-strategic \"新功能 X\"`。\n\n---\n\n## ⚡ 使用流程\n\n4-stage 三层栈方法论 — 推荐 4 个 master orchestrator 串行驱动:\n\n```\n/discuss  →  /plan  →  /task  →  /verify\n   ①         ②        ③         ④\n```\n\n| Stage | Master | 主要 sub-workflow | 上游协同 |\n| ---- | ---- | ---- | ---- |\n| ① **Discuss** | `/discuss` | strategic / phase / subtask (3 并行) | gstack `/office-hours` + GSD `/gsd-discuss-phase` + superpowers brainstorming |\n| ② **Plan** | `/plan` | architecture (conditional) → phase | gstack `/plan-eng-review` + GSD `/gsd-plan-phase` + planning-with-files |\n| ③ **Task** | `/task` | clarify → code → test → deliver (4 串行 per subtask) | karpathy 心法 + mattpocock 招式 + superpowers TDD + `ralph-loop` |\n| ④ **Verify** | `/verify` | progress → 5 parallel conditional → simplify (+ multispec critical) | GSD `/gsd-verify-work` + code-review + gstack `/review` / `/qa` / `/cso` / `/design-review` + code-simplifier |\n\n实操示例:\n\n```bash\n# 1. 装 workflow 上游 (一行装齐 gstack + GSD + superpowers + planning-with-files)\nharnessed setup\n\n# 2. 在 Claude Code 内跑 4-stage cadence\n/discuss \"新功能 X\"           # 战略 + Phase + 子任务 3 层澄清\n/plan \"新功能 X\"              # 架构 (conditional) + 计划 (任务图持久化)\n/task \"subtask-1: API contract\"  # 4 sub 串行 per subtask\n/verify \"phase-1\"             # 7 sub conditional\n\n# 3. 中断后恢复 (任何时候)\nharnessed resume\n```\n\n\u003e 也可直接调 sub 绕过 master 单跑某一层,例如 `/verify-paranoid` 只跑 Paranoid Staff Engineer 审查。\n\n📊 详细 mermaid + 各 stage 完整说明:[docs/WORKFLOW.md](./docs/WORKFLOW.md)\n\n---\n\n## 🗂️ 架构 (4-stage namespace-layered)\n\n### 1. 目录结构\n\n```\nharnessed/\n├── manifests/                  # L1: 上游描述层 (NOT vendored)\n├── workflows/                  # L6: composition skill (4-stage 指挥棒)\n│   ├── discuss/                # Stage ① 3 layer (strategic + phase + subtask)\n│   │   ├── auto/               # /discuss master gate-route\n│   │   ├── strategic/          # /discuss-strategic (gstack /office-hours + /plan-ceo-review)\n│   │   ├── phase/              # /discuss-phase (GSD /gsd-discuss-phase)\n│   │   └── subtask/            # /discuss-subtask (superpowers brainstorming)\n│   ├── plan/                   # Stage ② (architecture + phase 任务图)\n│   ├── task/                   # Stage ③ (clarify + code + test + deliver)\n│   ├── verify/                 # Stage ④ (progress + code-review + paranoid + qa + cso + design + simplify + multispec)\n│   ├── research/               # standalone Stage ① alternate\n│   ├── retro/                  # standalone post-④ milestone close\n│   ├── capabilities.yaml       # L5a: ~100 entry, 7 category SoT\n│   ├── defaults.yaml           # ralph_max_iterations per workflow phase\n│   ├── judgments/              # L5a: 三层栈判据 + parallelism + tdd + fallback + rules-routing\n│   │   ├── strategic-gate.yaml\n│   │   ├── phase-gate.yaml\n│   │   ├── subtask-gate.yaml\n│   │   ├── parallelism-gate.yaml         # L5b execution mechanism routing\n│   │   ├── tdd-gate.yaml\n│   │   ├── fallback.yaml                 # 3 铁律: skip_with_transparency + override + chain_isolation\n│   │   ├── web-design-routing.yaml       # UI 设计工具路由\n│   │   ├── web-testing-routing.yaml      # E2E / 浏览器测试工具路由\n│   │   ├── web-search-routing.yaml       # 网页搜索 / 文档抓取路由\n│   │   └── stage-routing.yaml            # master orchestrator sub-stage 路由\n│   └── disciplines/            # L0: 全局 cross-stage 行为基准\n│       ├── karpathy.yaml       # 4 心法 + ≤200L\n│       ├── output-style.yaml   # BLUF + no-emoji + no-em-dash\n│       ├── language.yaml       # zh-Hans default + English preserve\n│       ├── operational.yaml    # biome preempt + A7 + commit safety\n│       ├── priority.yaml       # skill conflict 仲裁\n│       └── protocols.yaml      # cc-handoff design doc 自包含\n├── routing/                    # L4: routing engine SSOT (decision_rules.yaml)\n├── schemas/                    # L3: JSON Schema (IDE / CI consume)\n├── src/                        # L4: TS engine (workflow + routing + cli + installers + checkpoint + audit + state)\n├── tests/                      # vitest unit + integration + dogfood (R8.1 dogfood-first)\n├── scripts/                    # CI gate (check-workflow-schema, transparency-verdict, state-archive)\n├── .planning/                  # project memory (STATE + ROADMAP + REQUIREMENTS + per-phase + milestones)\n└── docs/adr/                   # 架构决策记录\n```\n\n### 2. 逻辑分层 (8 层)\n\n```\n┌────────────────────────────────────────────────────────────┐\n│ L7 User-facing slash cmd + harnessed CLI                    │\n│   /discuss /plan /task /verify (master) + 18 sub + /research /retro + /auto super-master\n│   + direct gstack invoke (30+ optional): /office-hours /review /qa /...\n├────────────────────────────────────────────────────────────┤\n│ L6 Workflow orchestration (workflows/\u003cstage\u003e/\u003csub\u003e/)         │\n├────────────────────────────────────────────────────────────┤\n│ L5b Execution Mechanism (orthogonal): subagent / Agent Teams │\n│   / 主 session + ralph-loop wrapper                         │\n│   parallelism-gate.yaml: 默认 subagent → escalate 5 触发     │\n│   Pattern A 全栈三路 / B 对立假设 / C 多维度审查              │\n├────────────────────────────────────────────────────────────┤\n│ L5a Capability + Judgment + Defaults SoT                    │\n│   capabilities.yaml (7 category) + judgments/ (10 file) +    │\n│   defaults.yaml                                              │\n├────────────────────────────────────────────────────────────┤\n│ L4  Runtime engine (workflow / routing / handlers)           │\n├────────────────────────────────────────────────────────────┤\n│ L3  TypeBox schema + CI gate                                 │\n├────────────────────────────────────────────────────────────┤\n│ L2  Installer + Manifest engine                              │\n├────────────────────────────────────────────────────────────┤\n│ L1  Upstream components (NOT vendored)                       │\n├────────────────────────────────────────────────────────────┤\n│ L0  Discipline Substrate (全局生效)                          │\n│   karpathy 心法 + output-style + language + operational +    │\n│   priority + protocols (applied universally to L1-L7)       │\n└────────────────────────────────────────────────────────────┘\n```\n\n### 3. Cross-cutting Capabilities (capabilities.yaml 7 category, ~100 entry)\n\n```\nbehavioral (6):       karpathy-guidelines + output-style + language + operational + priority + protocols\ntool-slash-cmd (~60): gstack 30+ optional + gsd 10+ + mattpocock 12 高频 + 等\ntool-mcp (3):         chrome-devtools-mcp / tavily-mcp / exa-mcp\ntool-cli (2):         ctx7 / gws\ntool-plugin (2):      planning-with-files / @playwright/test\ntool-bundled (3):     ralph-loop / webapp-testing / playwright-cli\nagent-platform (3):   agent-teams-create / send-message / shutdown\n```\n\n### 4. 数据流示例 (用户调用 `/discuss \"新功能 X\"`)\n\n```\n[L7] User invokes /discuss \"新功能 X\"\n  ↓\n[L6] workflows/discuss/auto/workflow.yaml master orchestrator\n  ↓\n[L5a] judgments.strategic-gate.fires + phase-gate.fires + subtask-gate.fires (3-way 并行 eval)\n  ↓\n[L4] judgmentResolver.ts (4-level ref split) + exprBuilder.ts (expr-eval evaluate)\n  ↓\n[L0] discipline.priority-hierarchy 仲裁工具冲突 / output-style 格式化输出\n  ↓\n[fires=true sub] → invoke sub-workflow (/discuss-strategic / /discuss-phase / /discuss-subtask)\n  ↓ for each sub:\n      ├─ behavioral_layer: karpathy-guidelines (always-on)\n      ├─ tools_available: planning-with-files / ctx7 / mattpocock by-condition\n      ├─ parallelism: judgments.parallelism-gate.\u003croute\u003e.fires (L5b mechanism)\n      └─ phase invocations execute via capability template interpolation\n  ↓\n[fallback.yaml chain-isolation] 三层独立判断, 不串行依赖\n[Skip 透明声明] 不 fire 的 sub → \"⚠️ 跳过 \u003csub\u003e, 因为 \u003creason\u003e\"\n  ↓\nplanning-with-files /plan (cross-cutting tool) → write artifacts to .planning/\u003cphase-id\u003e/\n  ↓\n[L4] state.ts writeCurrentWorkflow (proper-lockfile) + audit.append (12-field JSONL)\n```\n\n### 5. 抉择路由矩阵 (rules-based, codified in judgments + capabilities)\n\n| 场景 | Default → Escalate |\n|------|---------------------|\n| 并行机制 | subagent → Agent Teams Pattern A/B/C (5 触发) |\n| UI 设计主方案 | ui-ux-pro-max → frontend-design (用户明示风格) |\n| E2E 浏览器探查 | playwright-cli (Bash 一行 token 省) |\n| E2E commit-able TS | @playwright/test 默认 |\n| E2E Python 后端联动 | webapp-testing |\n| 性能 / a11y / 内存诊断 | chrome-devtools-mcp |\n| Web 搜索 (关键词) | Tavily MCP 默认 |\n| Web 搜索 (描述式 / 学术) | Exa MCP |\n| 库 API 文档 | ctx7 CLI |\n| GitHub URL | gh CLI |\n| 单 URL 抓取 | WebFetch 内置 |\n| Gmail / Drive / Calendar | gws CLI |\n| 架构审查 (复杂) | gstack /plan-eng-review |\n| TDD 强制 (核心算法) | superpowers TDD OR mattpocock /tdd |\n| 关键模块 PR | gstack /review |\n| 大重构 PR 多维度审查 | 4-specialist Agent Team Pattern C |\n| 跨 session hand-off | discipline.protocols self-contained design doc |\n| `/auto` 复杂度大需求 | AI 1-shot judge → 自动建议 `--staged` (n abort 建议手动 `/discuss`) |\n| `/auto` 需求理解度 | 开始前 prompt → n 自动加 `/research` 多源调研 |\n\n---\n\n## 🛠️ 维护命令 (Operational)\n\n\u003e 这些是 harnessed 自身维护命令(setup / 健康检查 / 备份回滚 / 状态恢复等),日常 feature 开发用上面的 slash command 即可,这块通常不需要。\n\n**v4.0 — 编排大脑。** slash command 在 Claude Code 主 session 内跑澄清（让问题能触达你），再 spawn CC-native subagent（启用 Agent Teams + 澄清 round-trip）。harnessed 负责 gate 评估（`harnessed gates`）和 spawn-ready prompt（`harnessed prompt`），由主 session 完成 spawn。`harnessed run` 保留供 CI/headless 使用。\n\n### CLI 命令\n\n| 命令 | 说明 |\n| ---- | ---- |\n| `harnessed setup` | 一次性 setup,装 workflow skills 到 `~/.claude/skills/` + MCP 到 `~/.claude.json` |\n| `harnessed gates \u003cmaster\u003e` | 评估某 master stage 下哪些 sub-workflow 会 fire（JSON: fire/skip/parallelism）。供 slash command 编排 native spawn |\n| `harnessed prompt \u003csub\u003e` | 输出某 sub-workflow 的 spawn-ready prompt（role + checklist + disciplines + completion/clarification 协议） |\n| `harnessed checkpoint \u003caction\u003e \u003csub\u003e` | 记录 sub-workflow 的 start/complete/fail 到 `~/.claude/harnessed/checkpoints/` |\n| `harnessed run \u003cname\u003e` | 通过 in-process SDK spawn 运行 workflow（CI/headless 模式）。slash command 改用 CC-native spawn |\n| `harnessed resume` | session 中断后恢复至最近 checkpoint |\n| `harnessed status` | 当前 phase + lock holder |\n| `harnessed doctor` | 8-check 健康检查 (Node / MCP / jq / Win bash / 路由 / token budget 等) |\n| `harnessed install \u003cname\u003e` | 装上游 manifest |\n| `harnessed uninstall [name]` | 统一卸载 — 不指定名称：删除 harnessed 自身文件（上游完整保留）；指定名称：移除单个上游组件 |\n| `harnessed backup` | snapshot 备份管理 |\n| `harnessed rollback \u003ctimestamp\u003e` | 一行回滚 (EOL preserve + sha1 verify) |\n| `harnessed gc` | 清理过期 backups |\n| `harnessed audit-log` | 路由透明日志 query (支持 `--filter` jq 表达式) |\n\n### 参数 (Flags)\n\n\u003e 所有命令默认 **apply (immediate write)**,无需加 flag。高级用户可加 `--dry-run` 预览。\n\n| Flag | 说明 |\n| ---- | ---- |\n| `--dry-run` | 预览不写盘 (高级用户 opt-in) |\n| `--non-interactive` | CI / 脚本场景 |\n| `--system` | L4 全局装允许 (否则降级 L1 npx ephemeral) |\n| `--full-diff` | 展开 \u003e 200 行的 diff 折叠 |\n| `--no-color` | 强制 nocolor (即使 TTY) |\n| `--task \u003ctext\u003e` | `run` 子命令 — 任务描述 (传入 workflow `gateContext.task`) |\n| `--task-stdin` | `run` 子命令 — 从 stdin 读任务描述直到 EOF (避免 shell 转义引号/$/`) |\n\n---\n\n## ❓ FAQ\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eQ1. 装了 harnessed 还需要装 superpowers / gstack / GSD 上游吗?\u003c/b\u003e\u003c/summary\u003e\n\n\u003cbr\u003e\n\n需要,但**用户感知 = 一行命令**:\n\n```bash\nharnessed setup  # 自动装齐 gstack + GSD + superpowers + planning-with-files,25 workflow skill 一并落到 ~/.claude/skills/ + Agent Teams env var 自动写 ~/.claude.json\n```\n\n类比 `brew install \u003cformula\u003e` 装全套依赖 — 你不需要单独 `brew install` 每个依赖项。\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eQ2. 为什么不直接 vendor superpowers / gstack 进 harnessed 仓库?\u003c/b\u003e\u003c/summary\u003e\n\n\u003cbr\u003e\n\n4 条理由:\n\n1. **差异化哲学** — harnessed 是「装配主义包管理器」对位「all-in-one 自建派」。vendor = 失去 wedge → 沦为又一个 plugin pack\n2. **License + attribution 噩梦** — vendor 4-5 个主动维护的上游 = 复杂 license 拼盘\n3. **上游升级反向** — 当前 manifest 描述,上游升级用户 re-install 即得新版;vendor 后手动 sync code 永远落后\n4. **Bus factor 1** — 单 maintainer 维护 vendor 4-5 上游 = 加速 burnout\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eQ3. gstack / GSD / superpowers 看起来都是 plan/discuss 类,是不是重叠?\u003c/b\u003e\u003c/summary\u003e\n\n\u003cbr\u003e\n\n**不是**。它们是三层栈的不同阶段:\n\n| 阶段 | 上游 | 职责 |\n| ---- | ---- | ---- |\n| Governance | gstack | 多角色决策关卡 (CEO / EM / Designer / Paranoid Engineer) |\n| Brainstorming | superpowers | 子任务设计澄清、方案对比 |\n| Orchestration | GSD | 高层 phase 任务图 + 依赖分析 |\n| Persistence | planning-with-files | 持久化 `task_plan.md` / `progress.md` / `findings.md` |\n\n`/discuss /plan /task /verify` 4 个 master 把 4 阶段串起来,每个 master 内部再 delegate 到对应 sub。每个阶段做不同事,输出喂给下一阶段。**没有合并**。\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eQ4. workflow phase 之间是自动跑还是等用户?\u003c/b\u003e\u003c/summary\u003e\n\n\u003cbr\u003e\n\n看 `workflows/\u003cname\u003e/SKILL.md` frontmatter 的 `pause` 字段:\n\n- `pause: human_review` → 阻塞等用户 approve (governance gate / final lock,如 `/discuss-strategic` gstack `/office-hours` + `/plan-architecture` `/plan-eng-review` 锁定关卡)\n- 无 `pause` → 自动 chain 到下一 phase\n\n每个 phase 输出写到 `.harnessed/checkpoints/`,session 中断后 `harnessed resume` 从最近 checkpoint 继续。\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eQ5. harnessed 自己是 CC plugin 吗?\u003c/b\u003e\u003c/summary\u003e\n\n\u003cbr\u003e\n\n混合体:\n\n- `npx harnessed@latest setup` 跑的是 **Node.js CLI** (`bin/harnessed`)\n- setup 装的 **workflow skills** (markdown) 进 `~/.claude/skills/`,由 Claude Code 运行时加载\n- `/discuss` / `/plan` / `/task` / `/verify` 等是 CC 内的 slash command,触发 skill 执行\n- CLI 和 CC skill 共享 `.harnessed/checkpoints/` 状态目录\n\n\u003c/details\u003e\n\n---\n\n\n## License\n\n[Apache-2.0](./LICENSE) — 见 [NOTICE](./NOTICE) (含 Harness Inc. 商标 disclaimer)\n\n支持开发: [![Sponsor](https://img.shields.io/github/sponsors/easyinplay?logo=github\u0026label=Sponsor)](https://github.com/sponsors/easyinplay)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Feasyinplay%2Fharnessed","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Feasyinplay%2Fharnessed","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Feasyinplay%2Fharnessed/lists"}