harnessed 2.0.1 → 3.0.1

package/workflows/defaults.yaml

@@ -1,5 +1,6 @@
 # harnessed v2.0 workflow defaults
 # Phase v2.0-2.3 W1.2 ship — ralph_max_iterations table per R20.10 + D-10 fallback abort path
+# Phase v3.0-3.4 W2.2 extend — 18 v3 sub-workflow + retro standalone × phase entries
 # Sister Phase 2.2 STRIDE T-2.2-05 DoS mitigation: hard_upper_limit = 100 caps any user override
 # Phase 2.4 workflow.yaml v2 interpolation: {{ defaults.ralph_max_iterations.<workflow>.<phase> }}
 
@@ -8,6 +9,7 @@ schema_version: harnessed.defaults.v1
 # Per-workflow per-phase ralph-loop iteration ceiling
 # Values balance: completion guarantee vs DoS prevention; sister ADR 0011 v0.2.0 ralph-loop SDK pattern
 ralph_max_iterations:
+  # v2 legacy (Phase 2.3 W1.2 SHIPPED, deprecated v3.0 per D-04 release-notes-only migration)
   execute-task:
     01-clarify: 5
     02-code: 20
@@ -21,16 +23,81 @@ ralph_max_iterations:
     04-gsd-plan: 3
     05-persist: 5
 
-  research:
-    01-fan-out: 3
-    02-synth: 3
-
   verify-work:
     01-gsd-verify-work: 3
     02-code-review: 5
     03-gstack-review: 3
     04-code-simplifier: 5
 
+  # v3 standalone (research v3 schema bump + retro NEW per Phase 3.4 W1.1+W1.2)
+  research:
+    01-fan-out: 3
+    02-synth: 3
+
+  retro:
+    01-retro: 3
+    02-persist: 3
+
+  # v3 sub-workflow — discuss stage (3 sub per Phase 3.4 W0.1-W0.3)
+  discuss-strategic:
+    01-office-hours: 5
+    02-plan-ceo-review: 3
+
+  discuss-phase:
+    01-gsd-discuss-phase: 5
+
+  discuss-subtask:
+    01-brainstorm: 5
+
+  # v3 sub-workflow — plan stage (2 sub per Phase 3.4 W0.4-W0.5)
+  plan-architecture:
+    01-plan-eng-review: 3
+
+  plan-phase:
+    01-gsd-plan-phase: 5
+    02-persist: 5
+
+  # v3 sub-workflow — task stage (4 sub per Phase 3.4 W0.6-W0.9)
+  task-clarify:
+    01-clarify: 5
+
+  task-code:
+    01-code: 20
+
+  task-test:
+    01-test: 15
+
+  task-deliver:
+    01-deliver: 20
+
+  # v3 sub-workflow — verify stage (8 sub per Phase 3.4 W0.10-W0.13a-e)
+  verify-progress:
+    01-gsd-verify-work: 3
+    02-gsd-progress: 3
+    03-persist: 3
+
+  verify-code-review:
+    01-code-review: 5
+
+  verify-paranoid:
+    01-gstack-review: 3
+
+  verify-qa:
+    01-qa: 3
+
+  verify-security:
+    01-cso: 3
+
+  verify-design:
+    01-design-review: 3
+
+  verify-simplify:
+    01-code-simplifier: 5
+
+  verify-multispec:
+    01-team-create: 1
+    02-team-cleanup: 1
+
 # Hard upper limit — workflow engine rejects any user override > this value
 # Sister Phase 2.2 STRIDE T-2.2-05 DoS mitigation
 hard_upper_limit: 100

package/workflows/disciplines/karpathy.yaml

@@ -0,0 +1,47 @@
+# workflows/disciplines/karpathy.yaml
+# karpathy 心法 + 编码硬限 — 机器化 ~/.claude/CLAUDE.md 「andrej-karpathy-skills」 节
+# Phase v3.0-3.3 W0.4 ship per D-09 (L0 Discipline Substrate)
+# Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
+
+schema_version: harnessed.discipline.v1
+discipline: karpathy
+enforcement_layer: code-writing
+auto_enforce: true
+
+rules:
+  - id: think-before-coding
+    description: 先思考后写代码,不直接 dump 代码;每个子任务前 brainstorm 设计意图
+    enforcement: warn
+    trigger: subtask.type == 'code-write'
+    check_method: heuristic
+    # check_method='heuristic' — runtime engine 检查 subagent 输出 first 200 char 是否含设计意图 marker
+    # (e.g., 'Plan:' / 'Approach:' / '设计:' / '思路:'),若全是 code block → warn
+
+  - id: simplicity-first
+    description: 追求最小有效代码,避免不必要复杂度;YAGNI / 不为假设场景写代码
+    enforcement: warn
+    trigger: always-on
+    check_method: llm-judge
+    # check_method='llm-judge' — verify phase 调用 code-simplifier review
+
+  - id: surgical-changes
+    description: 小步原子修改,每个 commit 单一职责;不大段重写
+    enforcement: warn
+    trigger: phase.type == 'execute'
+    check_method: external-cmd
+    auto_fix_cmd: 'git diff --stat HEAD~1 | awk ''{lines+=$3} END {if (lines>300) exit 1}'''
+    # 单 commit > 300 line diff → warn (rough heuristic, override allowed via task spec)
+
+  - id: goal-driven-execution
+    description: 目标驱动,不发散 / 不无关重构;只解决当前任务 + 不夹带 cleanup
+    enforcement: warn
+    trigger: phase.type == 'execute'
+    check_method: heuristic
+
+  - id: file-length-200-hard-limit
+    description: 单文件 ≤200L 硬限 (per project CLAUDE.md karpathy 心法 reminder);超过 → split helper
+    enforcement: halt
+    trigger: phase.type == 'execute' AND file.lines > 200
+    check_method: external-cmd
+    auto_fix_cmd: 'wc -l <file> | awk ''{if ($1>200) exit 1}'''
+    # 实装 split helper pattern (sister fallbackHandlers.ts / sdkReconcile.ts ≤80L)

package/workflows/disciplines/language.yaml

@@ -0,0 +1,38 @@
+# workflows/disciplines/language.yaml
+# 语言与输出规范 — 机器化 ~/.claude/CLAUDE.md 「语言与输出规范」 节
+# Phase v3.0-3.3 W0.4 ship per D-09
+# Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
+
+schema_version: harnessed.discipline.v1
+discipline: language
+enforcement_layer: output
+auto_enforce: true
+
+rules:
+  - id: default-language-zh-hans
+    description: 默认输出语言简体中文 (zh-Hans);所有解释/分析/计划/总结/提问/状态更新一律中文
+    enforcement: warn
+    trigger: user.lang_request == null
+    check_method: heuristic
+    # heuristic — response 中文 char 占比 > 60% (排除 code block);占比 < 30% → warn
+
+  - id: preserve-english-categories
+    description: 8 类强制保留英文原文,不翻译不音译
+    enforcement: warn
+    trigger: always-on
+    check_method: heuristic
+    # 8 类 (verbatim CLAUDE.md):
+    #   1. 代码/命令/shell/配置/正则/SQL
+    #   2. 文件/目录/路径名 (src/components/Button.tsx 等)
+    #   3. 工具/框架/库/产品/公司名 (Claude Code / GSD / React 等)
+    #   4. API/函数/类/变量/字段/环境变量/配置键
+    #   5. 错误信息/stack trace/log 输出
+    #   6. URL / commit hash / issue / PR 编号 / 版本号 / git ref
+    #   7. 业内固定缩写与通用术语 (TDD / CRUD / API / MCP / token 等)
+    #   8. 引用原文 verbatim
+
+  - id: lang-request-override
+    description: 用户明确"用英文回答"/"reply in English"/"翻译成 X" → 整段切换目标语言
+    enforcement: info
+    trigger: user.lang_request != null
+    check_method: regex

package/workflows/disciplines/operational.yaml

@@ -0,0 +1,61 @@
+# workflows/disciplines/operational.yaml
+# 操作纪律 — 机器化 project CLAUDE.md (biome preempt + commit safety) +
+# ~/.claude/CLAUDE.md (A7 ADR / no-skip-hooks / authorization-not-transitive)
+# Phase v3.0-3.3 W0.4 ship per D-09
+# Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
+
+schema_version: harnessed.discipline.v1
+discipline: operational
+enforcement_layer: commit
+auto_enforce: true
+
+rules:
+  - id: biome-preempt
+    description: |
+      TS/JS commit 前必跑 `pnpm exec biome check --write` (3 CI-red recurrences Phase 2.1.1/2.2/2.3 project memory)
+    enforcement: auto-fix
+    trigger: |
+      phase.type == 'commit' AND
+      changed_files matches '\\.(ts|tsx|js|mjs)$'
+    check_method: external-cmd
+    auto_fix_cmd: 'corepack pnpm exec biome check --write'
+    # NEW src/discipline/enforcement/before-commit.ts hook; exit 0 才允许 commit
+
+  - id: a7-adr-conservation
+    description: |
+      新 ADR 不动旧 ADR main body,baseline tag iterate,CI A7 step 守恒
+      (sister Phase 1.3-2.6 ADR errata 路径)
+    enforcement: warn
+    trigger: phase.type == 'commit' AND changed_files contains 'docs/adr/'
+    check_method: external-cmd
+    auto_fix_cmd: 'scripts/check-adr-conservation.sh'
+
+  - id: no-push-without-approval
+    description: |
+      NEVER push to remote without user explicit approval (project CLAUDE.md commit safety)
+    enforcement: halt
+    trigger: cmd.type == 'git-push'
+    check_method: external-cmd
+    # ralph-loop / subagent 自动调 git push → halt;user explicit `git push` 在主 session 允许
+
+  - id: no-skip-hooks
+    description: |
+      不允许 --no-verify / --no-gpg-sign 等 skip hook flag,除非用户明确要求
+    enforcement: halt
+    trigger: cmd.type == 'git-commit' AND args contains '--no-verify'
+    check_method: regex
+
+  - id: destructive-ops-explicit
+    description: |
+      Destructive ops (git reset --hard / push --force / rm -rf / drop table) 必须用户 explicit 确认
+    enforcement: halt
+    trigger: cmd.is_destructive == true
+    check_method: heuristic
+    # heuristic — 命令含 'rm -rf' / 'reset --hard' / '--force' / 'DROP TABLE' / 'delete from'
+
+  - id: authorization-not-transitive
+    description: |
+      用户 approve 一次 push ≠ 全程 approve;每个 destructive / shared-state 操作单独确认
+    enforcement: warn
+    trigger: cmd.requires_approval == true AND session.has_prior_approval == true
+    check_method: heuristic

package/workflows/disciplines/output-style.yaml

@@ -0,0 +1,62 @@
+# workflows/disciplines/output-style.yaml
+# 对话回答风格 — 机器化 ~/.claude/CLAUDE.md 「对话回答风格」 节
+# Phase v3.0-3.3 W0.4 ship per D-09
+# Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
+
+schema_version: harnessed.discipline.v1
+discipline: output-style
+enforcement_layer: output
+auto_enforce: true
+
+rules:
+  - id: bluf-conclusion-first
+    description: 结论先行 (BLUF),每段先一句给答案/判断/推荐,再展开理由
+    enforcement: warn
+    trigger: always-on
+    check_method: heuristic
+    # heuristic — 第一句长度 ≤ 100 char + 含答案动词 ('是' / '不是' / '推荐' / '应该' / 'use X')
+    # 失败 → warn 'BLUF missing: first sentence is not a conclusion'
+
+  - id: no-sycophantic-open-close
+    description: 删除"好问题/太棒了/完美/希望对你有帮助/还需要别的吗"等开场闭合套话
+    enforcement: auto-fix
+    trigger: always-on
+    check_method: regex
+    auto_fix_cmd: 'strip-sycophantic'
+    # NEW src/discipline/enforcement/strip-sycophantic.ts — regex strip 13 known phrase
+
+  - id: no-emoji-unless-requested
+    description: 禁用 emoji,除非用户明确要求 (项目 markdown 文件如 README/PR/CHANGELOG 不约束)
+    enforcement: warn
+    trigger: response.target == 'chat' AND user.requested_emoji == false
+    check_method: regex
+    # regex /\p{Emoji_Presentation}/u; 命中 + trigger fires → warn
+
+  - id: no-em-dash
+    description: 禁用 em-dash (—— / —);替代:补充用括号/冒号,并列用顿号,转折单独成句
+    enforcement: auto-fix
+    trigger: response.target == 'chat'
+    check_method: regex
+    auto_fix_cmd: 'replace-em-dash'
+    # auto-replace '——' → ',  ' (单段内逗号);'—' → ':' OR ','
+
+  - id: precise-quantifier
+    description: 量词精确,能给具体数字/文件名/行号/commit hash 就不用"一些/几个/多个"
+    enforcement: info
+    trigger: always-on
+    check_method: llm-judge
+
+  - id: no-end-recap
+    description: 不做结尾总结,除非用户明确要求"汇总/recap"
+    enforcement: warn
+    trigger: response.target == 'chat'
+    check_method: heuristic
+    # heuristic — 末尾 200 char 含 '## 总结' / '## Summary' / 'In summary' / '综上所述'
+    # → warn 'redundant end recap'
+
+  - id: no-empty-continuation-question
+    description: 禁空洞续作询问 (要不要我帮你 X?/还需要别的吗?);保留工作流必要下一步指引
+    enforcement: warn
+    trigger: response.target == 'chat'
+    check_method: regex
+    # regex /要不要|还需要别的|希望对你有帮助/  + trigger fires → warn

package/workflows/disciplines/priority.yaml

@@ -0,0 +1,28 @@
+# workflows/disciplines/priority.yaml
+# 优先级仲裁 — 机器化 ~/.claude/CLAUDE.md 「响应规范与优先级」 节
+# Phase v3.0-3.3 W0.4 ship per D-09
+# Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
+
+schema_version: harnessed.discipline.v1
+discipline: priority
+enforcement_layer: workflow
+auto_enforce: true
+
+priority_hierarchy:
+  - gstack                       # 决策层 最高优先
+  - gsd                          # 整体 orchestration
+  - superpowers                  # 子任务执行质量
+  - planning-with-files          # 计划持久化
+  - karpathy                     # 编码行为
+  - mattpocock                   # 招式 by-demand
+  - parallel                     # subagent / Agent Teams / ralph-loop 执行机制
+
+rules:
+  - id: multi-capability-arbitration
+    description: |
+      多 capability fires_when 同时 true → 按 priority_hierarchy order 选最高
+      e.g., gstack /office-hours + GSD /gsd-discuss-phase 同 fire → gstack 先跑
+    enforcement: warn
+    trigger: capabilities.fired_count > 1
+    check_method: heuristic
+    # NEW src/discipline/enforcement/before-spawn.ts hook — sort fired capabilities by tier rank

package/workflows/disciplines/protocols.yaml

@@ -0,0 +1,70 @@
+# workflows/disciplines/protocols.yaml
+# 跨 CC instance 协议 — 机器化 ~/.claude/rules/cc-handoff.md (Ideation→Onboarding +
+# Plan→Execute) + 写入边界表
+# Phase v3.0-3.3 W0.4 ship per D-09
+# Snapshot of CLAUDE.md as of v3.0 ship date (K7 mitigation, verbatim)
+
+schema_version: harnessed.discipline.v1
+discipline: protocols
+enforcement_layer: workflow
+auto_enforce: false   # 默认 NOT auto-enforce — 协议是 cross-session, harnessed 主要 validate
+
+rules: []
+
+protocols:
+  cc-handoff-ideation-to-onboarding:
+    description: |
+      场景 A — Ideation-CC 写自包含产品设计文档;Onboarding-CC 新项目目录读取并启动 GSD
+    required_fields:
+      - 业务目的
+      - 范围/边界
+      - 关键决策+决策理由
+      - 技术栈+理由
+      - 已识别风险
+      - 推荐 milestone 划分
+      - "Open questions (OPEN: <问题>, decision required by user)"
+    forbidden_phrases:
+      - "TODO"
+      - "待补充"
+      - "暂定"
+
+  plan-execute-cc-ready-metadata:
+    description: |
+      场景 B — Plan-CC 离场 PLAN.md 必须 ready-to-execute (metadata 标记)
+    required_fields:
+      - "status: ready-to-execute"
+      - "每个 task: 精确文件路径"
+      - "每个 task: acceptance criteria"
+      - "每个 task: 依赖前置 task 编号"
+      - "## Open Questions 节为空"
+    forbidden_phrases:
+      - "TODO"
+      - "待补充"
+      - "暂定"
+
+  file-ownership-strict:
+    description: |
+      跨 CC 写入边界 — 下游 CC 不修改上游 artifact;歧义写到 PROGRESS.md ## Blocked
+    file_ownership:
+      ideation-cc:
+        - 产品设计文档
+      onboarding-cc:
+        - ".planning/* (初始化)"
+        - 项目代码
+      plan-cc:
+        - SPEC.md
+        - DISCUSS.md
+        - PLAN.md
+        - RESEARCH.md
+      execute-cc:
+        - PROGRESS.md
+        - VERIFICATION.md
+        - 代码
+        - commit
+    rules:
+      - id: no-modify-upstream-artifact
+        description: |
+          下游 CC 发现上游 artifact 模糊 → 写 PROGRESS.md ## Blocked,不修改上游
+        enforcement: halt
+        trigger: cc.role == 'execute' AND file.target matches 'PLAN.md|SPEC.md|DISCUSS.md|RESEARCH.md'
+        check_method: file-content-match

package/workflows/discuss/auto/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: discuss
+description: |
+  Stage ① Discuss master orchestrator — 3 sub-workflow parallel gate-eval (chain-isolation 铁律)。
+  战略层 / Phase 层 / 子任务层独立判断 gate, 可能 3 个全跑 / 1-2 个 / 全跳 + 透明声明。
+  schema_version: harnessed.workflow.v3 with delegates_to (3 sub: strategic + phase + subtask, mode parallel)
+  + disciplines_applied (6 default) + tools_available (planning-with-files)。
+  Triggered by harnessed CLI `harnessed discuss --topic <text>` or slash command `/discuss`
+  (bare per ADR 0030 namespace policy D-02 LOCK) after `harnessed setup`.
+trigger_phrases:
+  - "discuss"
+  - "讨论澄清"
+  - "新功能澄清"
+  - "stage 1 discuss"
+  - "三层澄清"
+---
+
+# discuss master orchestrator (v3)
+
+## Overview
+
+4-stage cadence Stage ① master orchestrator delegating to 3 independent sub-workflows
+(per ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 三层独立判断):
+
+| sub | gate ref | mode | when fires |
+| --- | -------- | ---- | ---------- |
+| `strategic` | `judgments.stage-routing.discuss-strategic-delegate.fires` | parallel | new_project / new_milestone / new_feature / is_major_release |
+| `phase` | `judgments.stage-routing.discuss-phase-delegate.fires` | parallel | open_decisions ≥ 2 / cross_phase_data_flow / scope_days > 1 |
+| `subtask` | `judgments.stage-routing.discuss-subtask-delegate.fires` | parallel | approaches ≥ 2 / core_algorithm / has_api_contract / error_cost=high |
+
+Engine runtime spawns 3 sub-workflow phases via `runMasterOrchestrator` per
+T3.5.W0.1 (sister sub-workflow `runWorkflow` SDK pattern, parallel fan-out via
+subagent default — Path A `query()` parallel OR Path B sub-shell fallback per
+T3.5.W2.1 dogfood cycle decision LOCK)。
+
+## Chain-isolation 铁律 (sister CLAUDE.md "Fallback 三条铁律")
+
+- 拿不准 → 倾向跳过, 但在响应里**透明声明**: "这次跳过了 X, 因为 Y。如果你认为需要请明说"
+- 用户明示 → 覆盖判据 (用户说 "先 brainstorm" / "跑 office-hours" / "讨论一下" 时无条件激活)
+- **链式互不前置**: 跳过战略层 ≠ 必须跳过 phase 层; 每层独立判断 (防止 "上层没跑下层不敢跑" 的死板)
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml`:
+- `planning-with-files` — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan, discuss sink findings.md)
+- sub `strategic` upstream → `gstack-office-hours` + `gstack-plan-ceo-review`
+- sub `phase` upstream → `gsd-discuss-phase`
+- sub `subtask` upstream → `superpowers-brainstorming` + `grill-with-docs` + `grill-me`
+
+## Invocation
+
+- CLI: `harnessed discuss --topic "<text>"`
+- Slash command: `/discuss <text>` (bare per ADR 0030 namespace policy D-02 LOCK after `harnessed setup`)
+
+## References
+
+- D-01 master orchestrator delegation pattern
+- D-02 bare slash cmd convention (ADR 0030 namespace policy LOCK)
+- D-04 Stage ① Discuss 三层独立判
+- ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 verbatim
+- workflows/judgments/stage-routing.yaml — discuss-{strategic,phase,subtask}-delegate triggers
+- workflows/discuss/{strategic,phase,subtask}/workflow.yaml — 3 sub-workflow Phase 3.4 SHIPPED
+- workflows/judgments/fallback.yaml — 链式互不前置 chain-isolation 铁律

package/workflows/discuss/auto/workflow.yaml

@@ -0,0 +1,40 @@
+# workflows/discuss/auto/workflow.yaml — Phase v3.0-3.5 W1 T3.5.W1.1
+#
+# Stage ① Discuss master orchestrator — 3 sub-workflow parallel gate-eval (chain-isolation 铁律
+# per ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 + fallback.yaml "链式互不前置")。
+# 3 sub 独立判 gate, 可能全跑 / 1-2 个 / 全跳 + 透明声明。
+#
+# Sister refs:
+#   - ~/.claude/CLAUDE.md "澄清/审查触发判据" 节 (战略 / Phase / 子任务三层独立判)
+#   - workflows/judgments/stage-routing.yaml — discuss-{strategic,phase,subtask}-delegate triggers
+#   - workflows/discuss/{strategic,phase,subtask}/workflow.yaml — 3 sub-workflow Phase 3.4 SHIPPED
+#   - workflows/capabilities.yaml — planning-with-files (discuss sink findings.md)
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 Master Orchestrator yaml Examples
+#   - src/workflow/schema/workflow.ts WorkflowSchemaV3 + DelegationClause (Phase 3.3 W0.5 SHIPPED)
+#
+# Master invariant (per WorkflowSchemaV3 runtime check + check-workflow-schema.mjs K9):
+#   - phases 缺省 (master only has delegates_to[])
+#   - 3 delegates_to mode parallel — 3 sub 独立 gate-eval, parallel fan-out
+#   - 无 serial mode → 无 order field 需求
+
+schema_version: harnessed.workflow.v3
+workflow: discuss
+description: |
+  Stage ① Discuss master orchestrator — 3 sub-workflow parallel gate-eval (chain-isolation 铁律):
+  战略层 (gstack /office-hours + /plan-ceo-review) + Phase 层 (GSD /gsd-discuss-phase) + 子任务层
+  (superpowers brainstorming) 独立判 gate, 可能全跑 / 1-2 个 / 全跳 + 透明声明 ("这次跳过了 X 因为 Y")。
+  Sister CLAUDE.md "澄清/审查触发判据" 节 + fallback.yaml "链式互不前置" 铁律。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [planning-with-files]
+
+delegates_to:
+  - sub: strategic
+    gate: judgments.stage-routing.discuss-strategic-delegate.fires
+    mode: parallel
+  - sub: phase
+    gate: judgments.stage-routing.discuss-phase-delegate.fires
+    mode: parallel
+  - sub: subtask
+    gate: judgments.stage-routing.discuss-subtask-delegate.fires
+    mode: parallel

package/workflows/discuss/phase/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: discuss-phase
+description: |
+  Stage ①.b Phase 层 discuss sub-workflow — GSD /gsd-discuss-phase 灰色澄清 (≥2 open
+  implementation decisions / 跨 phase API contract 不清 / phase scope > 1 day / 灰色地带)。
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (gsd-discuss-phase + planning-with-files) + 2 phases (01-gsd-discuss + 02-persist findings.md
+  + knowledge.md)。Triggered by harnessed CLI `harnessed discuss-phase --phase <num>` or slash
+  command `/discuss-phase` after `harnessed setup`.
+trigger_phrases:
+  - "discuss phase"
+  - "phase 层澄清"
+  - "gsd discuss phase"
+  - "灰色地带澄清"
+  - "跑 discuss-phase"
+---
+
+# discuss-phase workflow (v3)
+
+## Overview
+
+2-phase sub-workflow mapping CLAUDE.md "Stage ①.b Phase 层 — GSD /gsd-discuss-phase 灰色澄清"
+onto harnessed runtime (Phase v3.0-3.4 W0.2 — D-04 Stage ① Discuss 三层 + Pattern A
+sub-workflow ship)。
+
+| phase | id | upstream | model | capability / invokes | gate / artifacts |
+| ----- | -- | -------- | ----- | -------------------- | ---------------- |
+| 1 | `01-gsd-discuss` | gsd | sonnet | `{{ capabilities.gsd-discuss-phase.cmd }}` | `gate: judgments.phase-gate.gsd-discuss-phase.fires` |
+| 2 | `02-persist` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` + `invokes: /plan` | `artifacts_expected: [findings.md, knowledge.md]` |
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` entries:
+- `gsd-discuss-phase` — Bucket 2 (impl: gsd, cmd: /gsd-discuss-phase)
+- `planning-with-files` — Bucket 4 (impl: claude-code-plugin, cmd: /plan)
+
+## Gate refs
+
+Sister `workflows/judgments/phase-gate.yaml`:
+- `gsd-discuss-phase.fires` — `phase.open_decisions >= 2 or phase.has_cross_phase_data_flow == true or phase.scope_days > 1`
+
+## Invocation
+
+- CLI: `harnessed discuss-phase --phase <num>`
+- Slash command: `/discuss-phase <num>` (after `harnessed setup`)
+
+## Routing rules
+
+跳过条件 (sister CLAUDE.md "Phase 层 ❌ 跳过"):
+- 单一明确子任务
+- 跟前 phase 同 module 同 pattern
+- < 1 天工作量
+- bug 修复且已有最小复现
+
+## References
+
+- D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
+- ~/.claude/CLAUDE.md "Phase 层: GSD /gsd-discuss-phase"
+- workflows/capabilities.yaml — gsd-discuss-phase / planning-with-files
+- workflows/judgments/phase-gate.yaml — gsd-discuss-phase trigger
+- workflows/defaults.yaml — ralph_max_iterations.discuss-phase.* values (W2.2 backfill)

package/workflows/discuss/phase/workflow.yaml

@@ -0,0 +1,35 @@
+# workflows/discuss/phase/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.2
+#
+# Stage ①.b Phase 层 sub-workflow — GSD /gsd-discuss-phase 灰色澄清
+# (sister ~/.claude/CLAUDE.md "澄清/审查触发判据 — Phase 层")。
+#
+# Sister refs:
+#   - workflows/judgments/phase-gate.yaml — gsd-discuss-phase trigger
+#   - workflows/capabilities.yaml — gsd-discuss-phase / planning-with-files
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 sub-stage example verbatim
+
+schema_version: harnessed.workflow.v3
+workflow: discuss-phase
+description: |
+  Stage ①.b Phase 层 — GSD /gsd-discuss-phase 灰色澄清 (≥2 open decisions / phase scope > 1 day /
+  跨 phase API contract 不清)。Gate: judgments.phase-gate.gsd-discuss-phase.fires。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [gsd-discuss-phase, planning-with-files]
+
+phases:
+  - id: 01-gsd-discuss
+    name: gsd-discuss-phase (Phase 层灰色澄清 + open decisions resolve)
+    upstream: gsd
+    capability: '{{ capabilities.gsd-discuss-phase.cmd }}'
+    model: sonnet
+    gate: judgments.phase-gate.gsd-discuss-phase.fires
+    max_iterations: '{{ defaults.ralph_max_iterations.discuss-phase.01-gsd-discuss }}'
+
+  - id: 02-persist
+    name: planning-with-files findings.md + knowledge.md (phase decision 持久化)
+    upstream: planning-with-files
+    capability: '{{ capabilities.planning-with-files.cmd }}'
+    invokes: '/plan'
+    model: haiku
+    artifacts_expected: [findings.md, knowledge.md]