harnessed 2.0.1 → 3.0.1

package/workflows/discuss/strategic/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: discuss-strategic
+description: |
+  Stage ①.a 战略层 discuss sub-workflow — gstack /office-hours + /plan-ceo-review 新功能 / 新
+  milestone / 新产品方向启动前强制治理关卡 (sister ~/.claude/CLAUDE.md "🔒 新功能启动前强制")。
+  schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  (gstack-office-hours + gstack-plan-ceo-review + planning-with-files) + 3 phases (gate
+  judgments.strategic-gate.* fires + planning-with-files /plan findings.md 持久化)。
+  Triggered by harnessed CLI `harnessed discuss-strategic --topic <text>` or slash command
+  `/discuss-strategic` after `harnessed setup`.
+trigger_phrases:
+  - "discuss strategic"
+  - "战略层澄清"
+  - "office hours"
+  - "新功能启动"
+  - "跑 discuss-strategic"
+---
+
+# discuss-strategic workflow (v3)
+
+## Overview
+
+3-phase sub-workflow mapping CLAUDE.md "Stage ①.a 战略层 — 新功能启动前强制 🔒"
+onto harnessed runtime (Phase v3.0-3.4 W0.1 — D-04 Stage ① Discuss 三层 + D-12 gstack
+治理关卡 + Pattern A sub-workflow ship)。
+
+| phase | id | upstream | model | capability / invokes | gate / artifacts |
+| ----- | -- | -------- | ----- | -------------------- | ---------------- |
+| 1 | `01-office-hours` | gstack | opus | `{{ capabilities.gstack-office-hours.cmd }}` | `gate: judgments.strategic-gate.office-hours.fires` |
+| 2 | `02-plan-ceo-review` | gstack | opus | `{{ capabilities.gstack-plan-ceo-review.cmd }}` | `gate: judgments.strategic-gate.plan-ceo-review.fires` |
+| 3 | `03-persist` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` + `invokes: /plan` | `artifacts_expected: [findings.md]` |
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` entries:
+- `gstack-office-hours` — Bucket 3 治理关卡 (impl: gstack, cmd: /office-hours)
+- `gstack-plan-ceo-review` — Bucket 3 治理关卡 (impl: gstack, cmd: /plan-ceo-review)
+- `planning-with-files` — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
+
+## Gate refs
+
+Sister `workflows/judgments/strategic-gate.yaml`:
+- `office-hours.fires` — `phase.type in ['new_project', 'new_milestone', 'new_feature']`
+- `plan-ceo-review.fires` — `phase.type == 'new_project' or phase.is_major_release == true`
+
+## Invocation
+
+- CLI: `harnessed discuss-strategic --topic "<text>"`
+- Slash command: `/discuss-strategic <text>` (after `harnessed setup`)
+
+## Routing rules
+
+跳过条件 (sister CLAUDE.md "战略层 ❌ 跳过"):
+- bug 修复 / 技术债 / 实现细节
+- scope 已在历史 `.planning/` 或 design doc 定义
+- continuing 已有 phase 的执行
+- 用户已给明确 ticket / spec
+
+## References
+
+- D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
+- D-12 gstack 治理关卡强制
+- ~/.claude/CLAUDE.md "gstack 治理关卡 🔒 新功能启动前强制"
+- workflows/capabilities.yaml — gstack-office-hours / gstack-plan-ceo-review / planning-with-files
+- workflows/judgments/strategic-gate.yaml — office-hours / plan-ceo-review triggers
+- workflows/defaults.yaml — ralph_max_iterations.discuss-strategic.* values (W2.2 backfill)

package/workflows/discuss/strategic/workflow.yaml

@@ -0,0 +1,47 @@
+# workflows/discuss/strategic/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.1
+#
+# Stage ①.a 战略层 sub-workflow — gstack 治理关卡 /office-hours + /plan-ceo-review
+# 新功能 / 新 milestone / 新产品方向启动前强制 (sister ~/.claude/CLAUDE.md
+# "gstack 治理关卡 🔒 新功能启动前强制" verbatim)。
+#
+# Sister refs:
+#   - ~/.claude/CLAUDE.md "澄清/审查触发判据 — 战略层" 章节
+#   - workflows/judgments/strategic-gate.yaml — office-hours / plan-ceo-review triggers
+#   - workflows/capabilities.yaml — gstack-office-hours / gstack-plan-ceo-review / planning-with-files
+#   - src/workflow/schema/workflow.ts WorkflowSchemaV3 (Phase 3.3 W0.5 SHIPPED)
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 sub-stage example verbatim
+
+schema_version: harnessed.workflow.v3
+workflow: discuss-strategic
+description: |
+  Stage ①.a 战略层 — gstack /office-hours + /plan-ceo-review 新功能 / 新 milestone 启动前强制
+  (sister CLAUDE.md "🔒 新功能启动前强制")。Gate: judgments.strategic-gate.office-hours.fires
+  + judgments.strategic-gate.plan-ceo-review.fires (各 phase 独立 gate)。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [gstack-office-hours, gstack-plan-ceo-review, planning-with-files]
+
+phases:
+  - id: 01-office-hours
+    name: gstack-office-hours (YC-style pressure test + reframe + Design Doc)
+    upstream: gstack
+    capability: '{{ capabilities.gstack-office-hours.cmd }}'
+    model: opus
+    gate: judgments.strategic-gate.office-hours.fires
+    max_iterations: '{{ defaults.ralph_max_iterations.discuss-strategic.01-office-hours }}'
+
+  - id: 02-plan-ceo-review
+    name: gstack-plan-ceo-review (CEO 视角 商业价值 + 10-star 潜力 + scope)
+    upstream: gstack
+    capability: '{{ capabilities.gstack-plan-ceo-review.cmd }}'
+    model: opus
+    gate: judgments.strategic-gate.plan-ceo-review.fires
+    max_iterations: '{{ defaults.ralph_max_iterations.discuss-strategic.02-plan-ceo-review }}'
+
+  - id: 03-persist
+    name: planning-with-files findings.md (战略层决策 + 理由持久化)
+    upstream: planning-with-files
+    capability: '{{ capabilities.planning-with-files.cmd }}'
+    invokes: '/plan'
+    model: haiku
+    artifacts_expected: [findings.md]

package/workflows/discuss/subtask/SKILL.md

@@ -0,0 +1,67 @@
+---
+name: discuss-subtask
+description: |
+  Stage ①.c 子任务层 discuss sub-workflow — superpowers brainstorming (≥2 approach / 核心算法 /
+  API contract / 错误成本高)。schema_version: harnessed.workflow.v3 with disciplines_applied (6
+  default) + tools_available (superpowers-brainstorming + grill-with-docs + grill-me) + 1 phase
+  (01-brainstorm with conditional invokes_tools for spec_ambiguous + no_docs)。Triggered by
+  harnessed CLI `harnessed discuss-subtask --task <text>` or slash command `/discuss-subtask`
+  after `harnessed setup`.
+trigger_phrases:
+  - "discuss subtask"
+  - "子任务澄清"
+  - "brainstorm"
+  - "多 approach 探索"
+  - "跑 discuss-subtask"
+---
+
+# discuss-subtask workflow (v3)
+
+## Overview
+
+1-phase sub-workflow mapping CLAUDE.md "Stage ①.c 子任务层 — superpowers brainstorming"
+onto harnessed runtime (Phase v3.0-3.4 W0.3 — D-04 Stage ① Discuss 三层 + D-05
+phase.invokes_tools conditional fire + Pattern A sub-workflow ship)。
+
+| phase | id | upstream | model | capability / invokes_tools | gate |
+| ----- | -- | -------- | ----- | -------------------------- | ---- |
+| 1 | `01-brainstorm` | superpowers | opus | `{{ capabilities.superpowers-brainstorming.cmd }}` + conditional `invokes_tools[grill-with-docs, grill-me]` | `gate: judgments.subtask-gate.brainstorming.fires` |
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` entries:
+- `superpowers-brainstorming` — Bucket 4 (impl: superpowers, cmd: superpowers:brainstorming)
+- `grill-with-docs` — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-with-docs)
+- `grill-me` — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-me)
+
+## Gate ref
+
+Sister `workflows/judgments/subtask-gate.yaml`:
+- `brainstorming.fires` — `subtask.approaches >= 2 or subtask.core_algorithm == true or subtask.has_api_contract == true or subtask.error_cost == 'high'`
+
+## Conditional tool invocation (D-05 invokes_tools)
+
+- `phase.spec_ambiguous == true` → fire `grill-with-docs`
+- `phase.spec_ambiguous == true AND phase.no_docs == true` → fire `grill-me`
+
+## Invocation
+
+- CLI: `harnessed discuss-subtask --task "<text>"`
+- Slash command: `/discuss-subtask <text>` (after `harnessed setup`)
+
+## Routing rules
+
+跳过条件 (sister CLAUDE.md "子任务层 ❌ 跳过"):
+- 常规 CRUD / 跟现有模式一致
+- 单一明显实现 (< 20 行 / 一个文件)
+- 标准库直接调用
+- bug 修复且已知根因
+
+## References
+
+- D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
+- D-05 phase.invokes_tools conditional fire (NEW v3)
+- ~/.claude/CLAUDE.md "子任务层: superpowers:brainstorming"
+- workflows/capabilities.yaml — superpowers-brainstorming / grill-with-docs / grill-me
+- workflows/judgments/subtask-gate.yaml — brainstorming trigger
+- workflows/defaults.yaml — ralph_max_iterations.discuss-subtask.* values (W2.2 backfill)

package/workflows/discuss/subtask/workflow.yaml

@@ -0,0 +1,33 @@
+# workflows/discuss/subtask/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.3
+#
+# Stage ①.c 子任务层 sub-workflow — superpowers brainstorming (≥2 approach / 核心算法 /
+# API contract / 错误成本高)。Sister ~/.claude/CLAUDE.md "澄清/审查触发判据 — 子任务层"。
+#
+# Sister refs:
+#   - workflows/judgments/subtask-gate.yaml — brainstorming trigger
+#   - workflows/capabilities.yaml — superpowers-brainstorming / grill-with-docs / grill-me
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 sub-stage example verbatim
+
+schema_version: harnessed.workflow.v3
+workflow: discuss-subtask
+description: |
+  Stage ①.c 子任务层 — superpowers brainstorming (≥2 approach / 核心算法 / API contract / 错误成本高)。
+  Gate: judgments.subtask-gate.brainstorming.fires。conditional invokes_tools for
+  /grill-with-docs (spec_ambiguous) + /grill-me (spec_ambiguous AND no_docs)。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [superpowers-brainstorming, grill-with-docs, grill-me]
+
+phases:
+  - id: 01-brainstorm
+    name: superpowers-brainstorming (multi-approach explore + 选定 winning approach)
+    upstream: superpowers
+    capability: '{{ capabilities.superpowers-brainstorming.cmd }}'
+    model: opus
+    gate: judgments.subtask-gate.brainstorming.fires
+    invokes_tools:
+      - if: 'phase.spec_ambiguous == true'
+        tool: grill-with-docs
+      - if: 'phase.spec_ambiguous == true and phase.no_docs == true'
+        tool: grill-me
+    max_iterations: '{{ defaults.ralph_max_iterations.discuss-subtask.01-brainstorm }}'

package/workflows/judgments/stage-routing.yaml

@@ -0,0 +1,93 @@
+# workflows/judgments/stage-routing.yaml
+# Master orchestrator sub-stage delegation per D-01
+# 4 master (/discuss /plan /task /verify) auto gate-eval 触发 sub conditional
+# Sister: 3 strategic/phase/subtask gate 已 SHIPPED 独立判断, 本 file orchestrator-level routing
+#
+# Phase v3.0-3.2 Wave A RESEARCH → 3.3 W0.3 ship per D-11 + D-01
+#
+# expr-eval 2.0.2 case-sensitive: keyword `and` / `or` 全小写
+
+schema_version: harnessed.judgment.v1
+
+triggers:
+  # /discuss master → 3 sub conditional fire
+  discuss-strategic-delegate:
+    description: |
+      /discuss master → /discuss-strategic 委派 fire 当 strategic-gate.fires
+      (任一 office-hours OR plan-ceo-review)。
+    fires_when: "phase.type in ['new_project', 'new_milestone', 'new_feature'] or phase.is_major_release == true"
+    invokes:
+      - capability: gstack-office-hours
+      - capability: gstack-plan-ceo-review
+
+  discuss-phase-delegate:
+    description: /discuss master → /discuss-phase 委派 fire per phase-gate.fires。
+    fires_when: "phase.open_decisions >= 2 or phase.has_cross_phase_data_flow == true or phase.scope_days > 1"
+    invokes:
+      - capability: gsd-discuss-phase
+
+  discuss-subtask-delegate:
+    description: /discuss master → /discuss-subtask 委派 fire per subtask-gate.fires。
+    fires_when: "subtask.approaches >= 2 or subtask.core_algorithm == true or subtask.has_api_contract == true or subtask.error_cost == 'high'"
+    invokes:
+      - capability: superpowers-brainstorming
+
+  # /plan master → 2 sub serial
+  plan-architecture-delegate:
+    description: /plan master → /plan-architecture 委派 fire 当复杂架构 (gstack /plan-eng-review)。
+    fires_when: "phase.is_complex_architecture == true"
+    invokes:
+      - capability: plan-eng-review
+
+  plan-phase-delegate:
+    description: /plan master → /plan-phase 委派总是 fire (GSD plan-phase + planning-with-files)。
+    fires_when: "phase.stage == 'plan'"
+    invokes:
+      - capability: gsd-plan-phase
+      - capability: planning-with-files
+
+  # /verify master → 5-7 sub conditional
+  verify-progress-always:
+    description: /verify master → /verify-progress 总 fire (GSD verify + progress)。
+    fires_when: "phase.stage == 'verify'"
+    invokes:
+      - capability: gsd-verify-work
+      - capability: gsd-progress
+
+  verify-paranoid-critical:
+    description: /verify master → /verify-paranoid fire 当 critical_module。
+    fires_when: "phase.stage == 'verify' and phase.is_critical_module == true"
+    invokes:
+      - capability: gstack-review
+
+  verify-qa-ui:
+    description: /verify master → /verify-qa fire 当 has_ui_changes。
+    fires_when: "phase.stage == 'verify' and phase.has_ui_changes == true"
+    invokes:
+      - capability: gstack-qa
+
+  verify-security-secrets:
+    description: /verify master → /verify-security fire 当 has_auth_or_secrets。
+    fires_when: "phase.stage == 'verify' and phase.has_auth_or_secrets == true"
+    invokes:
+      - capability: gstack-cso
+
+  verify-design-changes:
+    description: /verify master → /verify-design fire 当 has_design_changes。
+    fires_when: "phase.stage == 'verify' and phase.has_design_changes == true"
+    invokes:
+      - capability: gstack-design-review
+
+  verify-multispec-critical-release:
+    description: |
+      /verify master → /verify-multispec 4-specialist Agent Team Pattern C fire
+      当 critical release。
+    fires_when: "phase.stage == 'verify' and is_critical_release == true"
+    invokes:
+      - capability: agent-teams-create
+
+  verify-simplify-tail:
+    description: /verify master → /verify-simplify 末尾 (code-simplifier)。
+    fires_when: "phase.stage == 'verify' and phase.is_final_step == true"
+    invokes:
+      - capability: code-simplifier

package/workflows/judgments/web-design-routing.yaml

@@ -0,0 +1,37 @@
+# workflows/judgments/web-design-routing.yaml
+# Sister: ~/.claude/rules/web-design.md ui-ux-pro-max 默认 + frontend-design 补充 + 仲裁
+# Phase v3.0-3.2 Wave A RESEARCH → 3.3 W0.3 ship per D-11
+#
+# 默认 ui-ux-pro-max 优先 (数据驱动 / 标准化 / 可解释);
+# 例外: 用户明示「做出风格」/「要独特」/「不要 AI 感」/「要有创意」时 frontend-design 主导;
+# 用户没明确表达就按默认走 (不脑补"用户应该想要独特")。
+#
+# expr-eval 2.0.2 case-sensitive: keyword `and` / `or` 全小写
+
+schema_version: harnessed.judgment.v1
+
+triggers:
+  ui-ux-pro-max-default:
+    description: |
+      默认主方案 — 数据驱动 / 标准化 / 可解释。
+      50+ styles, 161 color palettes, 57 font pairings, 161 product types,
+      99 UX guidelines, 10 stacks, 25 chart types。
+    fires_when: "phase.has_ui_changes == true and phase.requires_creative_polish == false"
+    invokes:
+      - capability: ui-ux-pro-max
+
+  frontend-design-creative:
+    description: |
+      创意补充 — 用户明示"做出风格 / 要独特 / 不要 AI 感 / 要有创意",
+      OR ui-ux-pro-max 决定主方案后 layout/动效/装饰性细节补充。
+    fires_when: "phase.has_ui_changes == true and phase.requires_creative_polish == true"
+    invokes:
+      - capability: frontend-design
+
+  design-review-post:
+    description: |
+      设计完成后可选 gstack /design-review — 设计系统一致性 + AI 审美问题识别。
+      常规 PR 跳过, 不强制。
+    fires_when: "phase.stage == 'verify' and phase.has_design_changes == true"
+    invokes:
+      - capability: gstack-design-review

package/workflows/judgments/web-search-routing.yaml

@@ -0,0 +1,52 @@
+# workflows/judgments/web-search-routing.yaml
+# Sister: ~/.claude/rules/web-search.md 条件式 fallback + Tavily/Exa MCP routing
+# Phase v3.0-3.2 Wave A RESEARCH → 3.3 W0.3 ship per D-11
+#
+# 路由优先级 (per rules/web-search.md):
+#   Step 1: 探测 Tavily / Exa MCP 是否安装
+#   Step 2A (MCP 不可用): 内置 WebFetch / WebSearch + gh CLI + ctx7 CLI fallback
+#   Step 2B (MCP 可用):  默认 Tavily, 描述式/学术/批量 Exa 覆盖, 整站 crawl Tavily 必用
+#
+# expr-eval 2.0.2 case-sensitive: keyword `and` / `or` 全小写
+
+schema_version: harnessed.judgment.v1
+
+triggers:
+  tavily-mcp-default:
+    description: |
+      Tavily MCP 默认 — 关键词查询 / 库 API 文档 / 新闻时效 / 生产 RAG。
+      支持 time_range / country / include_domains / exclude_domains / search_depth。
+    fires_when: "subtask.needs_web_search == true and subtask.search_type == 'keyword'"
+    invokes:
+      - capability: tavily-mcp
+
+  exa-mcp-descriptive-academic:
+    description: |
+      Exa MCP 覆盖默认 — 描述式查询 / 学术论文 / 批量抓多 URL /
+      用户明说"研究/深度调研" / Token 敏感 (Exa highlights 密度约 2× Tavily)。
+    fires_when: "subtask.needs_web_search == true and subtask.search_type in ['descriptive', 'academic']"
+    invokes:
+      - capability: exa-mcp
+
+  tavily-crawl-map-site:
+    description: |
+      Tavily 必用 — 抓整站 / 站点结构 (crawl / map), Exa 无对等工具。
+    fires_when: "subtask.needs_web_search == true and subtask.search_type == 'site-crawl'"
+    invokes:
+      - capability: tavily-mcp
+
+  ctx7-lib-docs:
+    description: |
+      ctx7 CLI — 库 / API / 框架 / SDK / CLI 工具文档抓取。
+      使用 user 完整问题作为 query, 不超过 3 命令/问。
+      Prefer over web search for library docs (per rules/context7.md)。
+    fires_when: "subtask.needs_lib_docs == true"
+    invokes:
+      - capability: ctx7
+
+  webfetch-single-url:
+    description: |
+      永远规则 — 单次轻量查询 (一个明确 URL) 直接 WebFetch, 不走 MCP / CLI。
+      WebFetch 是 Claude Code 平台内置, NOT capabilities.yaml registry entry。
+    fires_when: "subtask.search_type == 'single-url'"
+    # No capability invoke — WebFetch 是 Claude Code 平台内置

package/workflows/judgments/web-testing-routing.yaml

@@ -0,0 +1,50 @@
+# workflows/judgments/web-testing-routing.yaml
+# Sister: ~/.claude/rules/web-testing.md 三层职责矩阵 + 决策树机器化
+# Phase v3.0-3.2 Wave A RESEARCH → 3.3 W0.3 ship per D-11
+#
+# 三层职责矩阵 verbatim:
+#   脑 (写测试 / 跑 CI)         — @playwright/test (frontend/e2e/*.spec.ts)
+#   手 (AI 实时操作)            — playwright-cli (一行 Bash, token 最省)
+#   筋骨 (Python 后端联动)      — webapp-testing skill (tests/e2e/*.py)
+#   非功能性诊断 (性能/a11y/内存) — chrome-devtools-mcp (必用)
+#
+# expr-eval 2.0.2 case-sensitive: keyword `and` / `or` 全小写 (sister Phase 2.3 W0.2 bug)
+
+schema_version: harnessed.judgment.v1
+
+triggers:
+  playwright-test-default:
+    description: |
+      @playwright/test — 默认 CI 提交进 repo 的正式 E2E test framework,
+      前端 TypeScript / React / Vue, 只需浏览器操作 + HTTP API setup。
+      Path frontend/e2e/*.spec.ts; cmd npx playwright test。
+    fires_when: "subtask.test_type == 'ci-commit'"
+    skips_when: "subtask.test_type in ['probe', 'python-backend', 'perf-diagnostic']"
+    invokes:
+      - capability: playwright-test
+
+  playwright-cli-probe:
+    description: |
+      playwright-cli — AI 实时操作浏览器 一行 Bash, token 最省;
+      用于探查 / 调试 / 一次性确认 (非提交 repo)。
+      探查产出的 selectors 再沉淀到正式 test。
+    fires_when: "subtask.test_type == 'probe'"
+    invokes:
+      - capability: playwright-cli
+
+  webapp-testing-python-backend:
+    description: |
+      webapp-testing skill — Python 后端联动特例
+      (要 import Tortoise ORM / pandas / backend utils OR 前端是 Python 模板 Django Jinja)。
+      Path tests/e2e/*.py; with_server.py 双进程。
+    fires_when: "subtask.test_type == 'python-backend'"
+    invokes:
+      - capability: webapp-testing
+
+  chrome-devtools-mcp-diagnostic:
+    description: |
+      chrome-devtools-mcp — 非功能性诊断必须用 (NOT playwright/test/cli/webapp-testing)。
+      LCP / Core Web Vitals / ARIA / 堆快照。
+    fires_when: "subtask.test_type == 'perf-diagnostic'"
+    invokes:
+      - capability: chrome-devtools-mcp

package/workflows/plan/architecture/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: plan-architecture
+description: |
+  Stage ②.a 架构层 plan sub-workflow — gstack /plan-eng-review (复杂架构强制治理关卡,
+  sister ~/.claude/CLAUDE.md "⚠️ 复杂架构前 plan-eng-review")。schema_version:
+  harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
+  [plan-eng-review] + 1 phase (01-plan-eng-review) + gate literal expr
+  `phase.is_complex_architecture == true`。Triggered by harnessed CLI `harnessed
+  plan-architecture --module <name>` or slash command `/plan-architecture` after
+  `harnessed setup`.
+trigger_phrases:
+  - "plan architecture"
+  - "架构审查"
+  - "plan eng review"
+  - "复杂架构"
+  - "跑 plan-architecture"
+---
+
+# plan-architecture workflow (v3)
+
+## Overview
+
+1-phase sub-workflow mapping CLAUDE.md "⚠️ 复杂架构前 — plan-eng-review" onto harnessed
+runtime (Phase v3.0-3.4 W0.4 — D-04 Stage ② Plan 二层 + D-12 gstack 治理关卡 + Pattern A
+sub-workflow ship)。
+
+| phase | id | upstream | model | capability | gate |
+| ----- | -- | -------- | ----- | ---------- | ---- |
+| 1 | `01-plan-eng-review` | gstack | opus | `{{ capabilities.plan-eng-review.cmd }}` | `gate: phase.is_complex_architecture == true` (literal expr) |
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml` entries:
+- `plan-eng-review` — Bucket 7 gstack 33 optional (impl: gstack, cmd: /plan-eng-review)
+  - Pattern A E.2 LOCK: no `gstack-` prefix per CLAUDE.md gstack skill routing convention
+
+## Gate ref
+
+Inline literal expr `phase.is_complex_architecture == true` — sister capability
+`fires_when` clause verbatim。W2.2 backfill 可加 `judgments/phase-gate.yaml`
+trigger `is-complex-architecture` 重构 ref。
+
+## Invocation
+
+- CLI: `harnessed plan-architecture --module "<name>"`
+- Slash command: `/plan-architecture <name>` (after `harnessed setup`)
+
+## Routing rules
+
+触发条件 (sister CLAUDE.md "⚠️ 复杂架构前"):
+- 涉及多模块跨界设计 (≥3 模块协同)
+- 新引入核心抽象 (新 framework / 新数据模型 / 新协议)
+- 性能 / scaling 关键路径
+- 引入显著技术债 / migration 风险
+
+## References
+
+- D-04 Stage ② Plan 二层 (架构 / 计划)
+- D-12 gstack 治理关卡 (复杂架构强制)
+- ~/.claude/CLAUDE.md "⚠️ 复杂架构前: /plan-eng-review"
+- workflows/capabilities.yaml — plan-eng-review (Bucket 7)
+- workflows/defaults.yaml — ralph_max_iterations.plan-architecture.* values (W2.2 backfill)

package/workflows/plan/architecture/workflow.yaml

@@ -0,0 +1,33 @@
+# workflows/plan/architecture/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.4
+#
+# Stage ②.a 架构层 sub-workflow — gstack /plan-eng-review (复杂架构强制,
+# sister ~/.claude/CLAUDE.md "⚠️ 复杂架构前 plan-eng-review")。
+#
+# Sister refs:
+#   - workflows/capabilities.yaml — plan-eng-review (Bucket 7 gstack 33 optional registry)
+#   - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 sub-stage example verbatim
+#
+# Note: capabilities.yaml v3 entry name = `plan-eng-review` (NO `gstack-` prefix per
+# Pattern A E.2 — Bucket 7 gstack 33 optional 命名 strip prefix per 用户 CLAUDE.md
+# gstack skill routing 直接 invoke cmd 名)。判 gate 用 literal expr (judgments
+# phase-gate.yaml 暂无 is-complex-architecture trigger; v3 schema gate is Type.String
+# 接受任意 expr; W2.2 backfill 可加 judgment trigger)。
+
+schema_version: harnessed.workflow.v3
+workflow: plan-architecture
+description: |
+  Stage ②.a 架构层 — gstack /plan-eng-review (复杂架构强制, sister CLAUDE.md "⚠️ 复杂架构前")。
+  Gate: phase.is_complex_architecture == true literal expr (W2.2 backfill 可加 phase-gate
+  judgment trigger 重构 ref)。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available: [plan-eng-review]
+
+phases:
+  - id: 01-plan-eng-review
+    name: plan-eng-review (复杂架构审查 — engineering manager 视角, 锁定架构再 plan-phase)
+    upstream: gstack
+    capability: '{{ capabilities.plan-eng-review.cmd }}'
+    model: opus
+    gate: 'phase.is_complex_architecture == true'
+    max_iterations: '{{ defaults.ralph_max_iterations.plan-architecture.01-plan-eng-review }}'

package/workflows/plan/auto/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: plan
+description: |
+  Stage ② Plan master orchestrator — 串行 invoke 2 sub (architecture conditional → phase always)。
+  复杂架构 gstack /plan-eng-review 锁定架构后再 GSD /gsd-plan-phase + planning-with-files 持久化
+  task_plan.md。schema_version: harnessed.workflow.v3 with delegates_to (2 sub: architecture
+  serial order 1 + phase serial order 2) + disciplines_applied (6 default) + tools_available
+  (planning-with-files + plan-eng-review + gsd-plan-phase)。
+  Triggered by harnessed CLI `harnessed plan --topic <text>` or slash command `/plan`
+  (bare per ADR 0030 namespace policy D-02 LOCK) after `harnessed setup`.
+trigger_phrases:
+  - "plan"
+  - "计划阶段"
+  - "stage 2 plan"
+  - "持久化计划"
+  - "task_plan"
+---
+
+# plan master orchestrator (v3)
+
+## Overview
+
+4-stage cadence Stage ② master orchestrator delegating to 2 sequential sub-workflows
+(per ~/.claude/CLAUDE.md "Plan 阶段" 节 + D-06 planning-with-files cross-cutting tool):
+
+| order | sub | gate ref | mode | when fires |
+| ----- | --- | -------- | ---- | ---------- |
+| 1 | `architecture` | `judgments.stage-routing.plan-architecture-delegate.fires` | serial | phase.is_complex_architecture == true |
+| 2 | `phase` | (unconditional — plan-phase always fires when stage=='plan') | serial | always |
+
+Engine runtime spawns 2 sub-workflow phases sequentially via `runMasterOrchestrator`
+per T3.5.W0.1 — order 1 (architecture conditional) MUST complete before order 2
+(phase unconditional, GSD plan-phase + planning-with-files /plan task_plan.md
+持久化)。K9 invariant enforced: every serial mode delegate carries explicit `order`。
+
+## Capability refs
+
+Sister `workflows/capabilities.yaml`:
+- `planning-with-files` — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
+- `plan-eng-review` — Bucket 7 gstack 33 optional (impl: gstack, cmd: /plan-eng-review)
+- `gsd-plan-phase` — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-plan-phase)
+- sub `architecture` upstream → `plan-eng-review`
+- sub `phase` upstream → `gsd-plan-phase` + `planning-with-files`
+
+## Routing rules (sister CLAUDE.md "Plan 阶段")
+
+- **复杂架构必须先跑** `/plan-eng-review` 锁定架构后再进入 plan-phase (sister CLAUDE.md "⚠️")
+- 普通 phase skip architecture sub (gate `phase.is_complex_architecture == false`)
+- **禁止在规划阶段直接使用** `superpowers:writing-plans` 输出大文档 (除非用户明确要求)
+
+## Invocation
+
+- CLI: `harnessed plan --topic "<text>"`
+- Slash command: `/plan <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-06 planning-with-files cross-cutting tool (NOT 独立 sub-workflow)
+- ~/.claude/CLAUDE.md "Plan 阶段" 节 verbatim
+- workflows/judgments/stage-routing.yaml — plan-{architecture,phase}-delegate triggers
+- workflows/plan/{architecture,phase}/workflow.yaml — 2 sub-workflow Phase 3.4 SHIPPED

package/workflows/plan/auto/workflow.yaml

@@ -0,0 +1,41 @@
+# workflows/plan/auto/workflow.yaml — Phase v3.0-3.5 W1 T3.5.W1.2
+#
+# Stage ② Plan master orchestrator — 串行 invoke 2 sub (architecture conditional → phase always)
+# per ~/.claude/CLAUDE.md "Plan 阶段" 节 + RESEARCH-workflows § Area 2。
+# planning-with-files /plan 是 D-06 cross-cutting tool (NOT 独立 sub-workflow per user clarification 2)。
+#
+# Sister refs:
+#   - ~/.claude/CLAUDE.md "Plan 阶段 (GSD + planning-with-files, 可选 gstack 架构审查)" 节
+#   - workflows/judgments/stage-routing.yaml — plan-{architecture,phase}-delegate triggers
+#   - workflows/plan/{architecture,phase}/workflow.yaml — 2 sub-workflow Phase 3.4 SHIPPED
+#   - workflows/capabilities.yaml — planning-with-files + plan-eng-review + gsd-plan-phase
+#   - .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-workflow-schema.mjs K9):
+#   - phases 缺省 (master only has delegates_to[])
+#   - 2 delegates_to mode serial — 必带 explicit order (K9 invariant T3.3.W0.10)
+#   - architecture conditional (gate phase.is_complex_architecture) + phase unconditional
+
+schema_version: harnessed.workflow.v3
+workflow: plan
+description: |
+  Stage ② Plan master orchestrator — 串行 invoke 2 sub (architecture conditional → phase always);
+  planning-with-files /plan 自动 sink task_plan.md + progress.md (D-06 cross-cutting tool, NOT
+  独立 sub-workflow per user clarification 2)。复杂架构 gstack /plan-eng-review 强制 (sister
+  CLAUDE.md "⚠️ 复杂架构前 plan-eng-review"), 普通 phase skip architecture sub。
+
+disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
+tools_available:
+  - planning-with-files
+  - plan-eng-review
+  - gsd-plan-phase
+
+delegates_to:
+  - sub: architecture
+    gate: judgments.stage-routing.plan-architecture-delegate.fires
+    mode: serial
+    order: 1
+  - sub: phase
+    mode: serial
+    order: 2