harnessed 2.0.1 → 3.0.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (68) hide show
  1. package/README.md +246 -47
  2. package/dist/cli.mjs +416 -98
  3. package/dist/cli.mjs.map +1 -1
  4. package/dist/index.mjs +1 -1
  5. package/dist/index.mjs.map +1 -1
  6. package/package.json +1 -1
  7. package/workflows/capabilities.yaml +468 -0
  8. package/workflows/defaults.yaml +71 -4
  9. package/workflows/disciplines/karpathy.yaml +47 -0
  10. package/workflows/disciplines/language.yaml +38 -0
  11. package/workflows/disciplines/operational.yaml +61 -0
  12. package/workflows/disciplines/output-style.yaml +62 -0
  13. package/workflows/disciplines/priority.yaml +28 -0
  14. package/workflows/disciplines/protocols.yaml +70 -0
  15. package/workflows/discuss/auto/.gitkeep +0 -0
  16. package/workflows/discuss/auto/SKILL.md +63 -0
  17. package/workflows/discuss/auto/workflow.yaml +40 -0
  18. package/workflows/discuss/phase/SKILL.md +61 -0
  19. package/workflows/discuss/phase/workflow.yaml +35 -0
  20. package/workflows/discuss/strategic/SKILL.md +66 -0
  21. package/workflows/discuss/strategic/workflow.yaml +47 -0
  22. package/workflows/discuss/subtask/SKILL.md +67 -0
  23. package/workflows/discuss/subtask/workflow.yaml +33 -0
  24. package/workflows/judgments/stage-routing.yaml +93 -0
  25. package/workflows/judgments/web-design-routing.yaml +37 -0
  26. package/workflows/judgments/web-search-routing.yaml +52 -0
  27. package/workflows/judgments/web-testing-routing.yaml +50 -0
  28. package/workflows/plan/architecture/SKILL.md +62 -0
  29. package/workflows/plan/architecture/workflow.yaml +33 -0
  30. package/workflows/plan/auto/.gitkeep +0 -0
  31. package/workflows/plan/auto/SKILL.md +63 -0
  32. package/workflows/plan/auto/workflow.yaml +41 -0
  33. package/workflows/plan/phase/SKILL.md +64 -0
  34. package/workflows/plan/phase/workflow.yaml +37 -0
  35. package/workflows/research/SKILL.md +6 -2
  36. package/workflows/research/workflow.yaml +34 -3
  37. package/workflows/retro/SKILL.md +68 -0
  38. package/workflows/retro/workflow.yaml +40 -0
  39. package/workflows/task/auto/.gitkeep +0 -0
  40. package/workflows/task/auto/SKILL.md +68 -0
  41. package/workflows/task/auto/workflow.yaml +57 -0
  42. package/workflows/task/clarify/SKILL.md +83 -0
  43. package/workflows/task/clarify/workflow.yaml +39 -0
  44. package/workflows/task/code/SKILL.md +89 -0
  45. package/workflows/task/code/workflow.yaml +55 -0
  46. package/workflows/task/deliver/SKILL.md +118 -0
  47. package/workflows/task/deliver/workflow.yaml +77 -0
  48. package/workflows/task/test/SKILL.md +93 -0
  49. package/workflows/task/test/workflow.yaml +44 -0
  50. package/workflows/verify/auto/.gitkeep +0 -0
  51. package/workflows/verify/auto/SKILL.md +77 -0
  52. package/workflows/verify/auto/workflow.yaml +74 -0
  53. package/workflows/verify/code-review/SKILL.md +69 -0
  54. package/workflows/verify/code-review/workflow.yaml +32 -0
  55. package/workflows/verify/design/SKILL.md +72 -0
  56. package/workflows/verify/design/workflow.yaml +33 -0
  57. package/workflows/verify/multispec/SKILL.md +86 -0
  58. package/workflows/verify/multispec/workflow.yaml +58 -0
  59. package/workflows/verify/paranoid/SKILL.md +71 -0
  60. package/workflows/verify/paranoid/workflow.yaml +30 -0
  61. package/workflows/verify/progress/SKILL.md +67 -0
  62. package/workflows/verify/progress/workflow.yaml +44 -0
  63. package/workflows/verify/qa/SKILL.md +73 -0
  64. package/workflows/verify/qa/workflow.yaml +31 -0
  65. package/workflows/verify/security/SKILL.md +67 -0
  66. package/workflows/verify/security/workflow.yaml +31 -0
  67. package/workflows/verify/simplify/SKILL.md +67 -0
  68. package/workflows/verify/simplify/workflow.yaml +31 -0
@@ -0,0 +1,72 @@
1
+ ---
2
+ name: verify-design
3
+ description: |
4
+ Stage ④.f verify sub-workflow — gstack /design-review 设计系统一致性 + AI 审美问题识别
5
+ (has_design_changes 触发, 可选 conditional, sister ~/.claude/CLAUDE.md "Verify 阶段 — 可选
6
+ /design-review" verbatim)。
7
+ schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
8
+ (gstack-design-review + ui-ux-pro-max + frontend-design) + 1 phase (gate ref has_design_changes
9
+ conditional)。Triggered by harnessed CLI `harnessed verify-design --phase <num>` or slash
10
+ command `/verify-design` after `harnessed setup`.
11
+ trigger_phrases:
12
+ - "verify design"
13
+ - "设计审查"
14
+ - "design review"
15
+ - "gstack design review"
16
+ - "跑 verify-design"
17
+ ---
18
+
19
+ # verify-design workflow (v3)
20
+
21
+ ## Overview
22
+
23
+ 1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 可选 /design-review" onto harnessed
24
+ runtime (Phase v3.0-3.4 W0.13c — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 +
25
+ Pattern A sub-workflow ship)。
26
+
27
+ | phase | id | upstream | model | capability | gate |
28
+ | ----- | -- | -------- | ----- | ---------- | ---- |
29
+ | 1 | `01-design-review` | gstack | sonnet | `{{ capabilities.gstack-design-review.cmd }}` | `judgments.stage-routing.verify-design-changes.fires` |
30
+
31
+ Per-phase config loads from `workflows/verify/design/workflow.yaml`; engine 4-level gate
32
+ resolver evaluates `phase.has_design_changes == true` via expr-eval — true 则 invoke gstack
33
+ `/design-review` (设计系统一致性 + AI 审美问题识别), false 则 skip。
34
+
35
+ ## Capability refs
36
+
37
+ Sister `workflows/capabilities.yaml` entries:
38
+ - `gstack-design-review` — Bucket 3 治理关卡 (impl: gstack, cmd: /design-review,
39
+ fires_when: has_design_changes)
40
+ - `ui-ux-pro-max` — Bucket 2 special-purpose (impl: gstack, 默认主方案 数据驱动)
41
+ - `frontend-design` — Bucket 2 special-purpose (impl: gstack, UI 创意 / 装饰补充)
42
+
43
+ ## Gate ref
44
+
45
+ Sister `workflows/judgments/stage-routing.yaml`:
46
+ - `verify-design-changes.fires` — `phase.stage == 'verify' and phase.has_design_changes == true`
47
+
48
+ ## Routing rules (sister ~/.claude/rules/web-design.md)
49
+
50
+ - 默认主方案 → `ui-ux-pro-max` (数据驱动、标准化、可解释)
51
+ - 创意补充 / 不要 AI 味 → `frontend-design`
52
+ - 用户明示「独特 / 不要 AI 感」→ frontend-design 主导, 否则 ui-ux-pro-max 优先
53
+
54
+ ## CLI invocation
55
+
56
+ ```bash
57
+ # Dry-run preview — arbitrate-only, never spawns SDK.
58
+ harnessed verify-design --phase <num> --dry-run --non-interactive
59
+
60
+ # Apply path — real SDK spawn (gate eval true 时).
61
+ harnessed verify-design --phase <num> --apply
62
+ ```
63
+
64
+ ## References
65
+
66
+ - D-04 Stage ④ Verify 7 sub 分解
67
+ - D-12 gstack 治理关卡可选
68
+ - ~/.claude/CLAUDE.md "Verify 阶段 — 可选 /design-review" verbatim
69
+ - ~/.claude/rules/web-design.md — ui-ux-pro-max 默认 + frontend-design 补充
70
+ - workflows/capabilities.yaml — gstack-design-review / ui-ux-pro-max / frontend-design
71
+ - workflows/judgments/stage-routing.yaml — verify-design-changes trigger
72
+ - workflows/verify-work/workflow.yaml v2 SHIPPED phase 07-design-review-conditional sister verbatim
@@ -0,0 +1,33 @@
1
+ # workflows/verify/design/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.13c
2
+ #
3
+ # Stage ④.f verify sub-workflow — gstack /design-review 设计系统一致性 + AI 审美问题
4
+ # (has_design_changes 触发, 可选 conditional, sister ~/.claude/CLAUDE.md "可选 /design-review" verbatim)。
5
+ #
6
+ # Sister refs:
7
+ # - ~/.claude/CLAUDE.md "Verify 阶段 — 可选 /design-review" 章节
8
+ # - ~/.claude/rules/web-design.md — ui-ux-pro-max 默认 + frontend-design 补充
9
+ # - workflows/judgments/stage-routing.yaml verify-design-changes trigger (has_design_changes)
10
+ # - workflows/capabilities.yaml — gstack-design-review / ui-ux-pro-max / frontend-design
11
+ # - workflows/verify-work/workflow.yaml v2 SHIPPED phase 07-design-review-conditional sister pattern
12
+ # - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 verify/design example verbatim
13
+
14
+ schema_version: harnessed.workflow.v3
15
+ workflow: verify-design
16
+ description: |
17
+ Stage ④.f gstack /design-review 设计系统一致性 + AI 审美问题识别 (has_design_changes 触发,
18
+ 可选 conditional)。Gate: judgments.stage-routing.verify-design-changes.fires
19
+ (phase.has_design_changes == true) — UI module fire only; 后端 / docs PR skip。
20
+ tools_available 含 ui-ux-pro-max (默认主方案) + frontend-design (创意补充) sister
21
+ ~/.claude/rules/web-design.md routing。
22
+
23
+ disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
24
+ tools_available: [gstack-design-review, ui-ux-pro-max, frontend-design]
25
+
26
+ phases:
27
+ - id: 01-design-review
28
+ name: gstack-design-review (设计系统一致性 + AI 审美问题 — has_design_changes 触发)
29
+ upstream: gstack
30
+ capability: '{{ capabilities.gstack-design-review.cmd }}'
31
+ model: sonnet
32
+ gate: judgments.stage-routing.verify-design-changes.fires
33
+ max_iterations: 3
@@ -0,0 +1,86 @@
1
+ ---
2
+ name: verify-multispec
3
+ description: |
4
+ Stage ④.h verify sub-workflow — 4-specialist Agent Team Pattern C 多维度审查 (关键发布 /
5
+ 大重构 PR 升级, code-review + gstack-review + gstack-cso + gstack-qa 4 teammate 互相
6
+ SendMessage 质询, NOT fire-and-forget subagent fan-out, sister ~/.claude/rules/agent-teams.md
7
+ L42-L52 Pattern C verbatim)。Cleanup mandatory: shutdown_request + TeamDelete (防呆清单)。
8
+ schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
9
+ (agent-teams 3 + 4 specialist capability) + 2 phase (01-team-create on critical-release
10
+ invoke / 02-team-cleanup mandatory shutdown)。
11
+ Triggered by harnessed CLI `harnessed verify-multispec --phase <num>` or slash command
12
+ `/verify-multispec` after `harnessed setup`.
13
+ trigger_phrases:
14
+ - "verify multispec"
15
+ - "4-specialist Agent Team"
16
+ - "Pattern C 多维度审查"
17
+ - "critical release review"
18
+ - "跑 verify-multispec"
19
+ ---
20
+
21
+ # verify-multispec workflow (v3)
22
+
23
+ ## Overview
24
+
25
+ 2-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 关键发布 / 大重构 PR 升级 Agent Team
26
+ Pattern C" onto harnessed runtime (Phase v3.0-3.4 W0.13e — D-04 Stage ④ Verify 7 sub +
27
+ D-11 Agent Teams + Pattern A sub-workflow ship)。
28
+
29
+ | phase | id | upstream | model | capability | gate / on |
30
+ | ----- | -- | -------- | ----- | ---------- | --------- |
31
+ | 1 | `01-team-create` | claude-platform | opus | `{{ capabilities.agent-teams-create.cmd }}` | `parallelism: agent-teams-upgrade.fires`; `on: is_major_release OR is_large_refactor → invoke` |
32
+ | 2 | `02-team-cleanup` | claude-platform | haiku | `{{ capabilities.agent-teams-shutdown.cmd }}` | mandatory 防呆清单 |
33
+
34
+ Per-phase config loads from `workflows/verify/multispec/workflow.yaml`; phase 01 creates 4
35
+ teammate (code-review + gstack-review + gstack-cso + gstack-qa) via TeamCreate, teammates 互相
36
+ SendMessage 质询 findings 是否真问题 (NOT fire-and-forget); phase 02 mandatory shutdown_request
37
+ + TeamDelete (防呆清单 per ~/.claude/rules/agent-teams.md L46-L48)。
38
+
39
+ ## Capability refs
40
+
41
+ Sister `workflows/capabilities.yaml` entries:
42
+ - `agent-teams-create` — Bucket 5 Agent Teams (impl: claude-platform, cmd: TeamCreate)
43
+ - `agent-teams-send-message` — Bucket 5 Agent Teams (impl: claude-platform, cmd: SendMessage)
44
+ - `agent-teams-shutdown` — Bucket 5 Agent Teams (impl: claude-platform, cmd: TeamDelete)
45
+ - `code-review` — Bucket 1 mattpocock (teammate 1)
46
+ - `gstack-review` — Bucket 3 治理关卡 (teammate 2 Paranoid Staff Engineer)
47
+ - `gstack-cso` — Bucket 3 治理关卡 (teammate 3 安全审查)
48
+ - `gstack-qa` — Bucket 3 治理关卡 (teammate 4 端到端 QA)
49
+
50
+ ## Parallelism + on gate refs
51
+
52
+ Sister `workflows/judgments/parallelism-gate.yaml`:
53
+ - `agent-teams-upgrade.fires` — 5 OR-chain (teammate_send_message_needed / subagent_context_overflow /
54
+ shared_task_list / opposing_hypothesis_debate / fullstack_three_way)
55
+
56
+ Phase-level `on` clause (critical-release 升级触发):
57
+ - `if: phase.is_major_release == true or phase.is_large_refactor == true` → `action: invoke`
58
+ - else → `action: skip`
59
+
60
+ ## Routing rules (sister ~/.claude/rules/agent-teams.md)
61
+
62
+ - ✅ **触发**: 关键发布 / 大重构 PR (≥3 specialist 需互相质询而非 fire-and-forget)
63
+ - ❌ **跳过**: 常规 PR / 单点任务 (sister verify-code-review fan-out + verify-paranoid 已够用且省 token)
64
+ - **Token 估算 prereq**: `team_cost < 2 × subagent_cost` (engine-level check per agent-teams.md L34)
65
+ - **Cleanup mandatory**: phase 02-team-cleanup `agent-teams-shutdown` 必跑 (防呆清单)
66
+
67
+ ## CLI invocation
68
+
69
+ ```bash
70
+ # Dry-run preview — arbitrate-only, never spawns SDK.
71
+ harnessed verify-multispec --phase <num> --dry-run --non-interactive
72
+
73
+ # Apply path — real SDK spawn + TeamCreate 4 specialist + 互相 SendMessage 质询 + 末尾 TeamDelete。
74
+ harnessed verify-multispec --phase <num> --apply
75
+ ```
76
+
77
+ ## References
78
+
79
+ - D-04 Stage ④ Verify 7 sub 分解
80
+ - D-11 Agent Teams 4-specialist Pattern C upgrade
81
+ - ~/.claude/CLAUDE.md "Verify 阶段 — 关键发布 / 大重构 PR 升级 Agent Team Pattern C" verbatim
82
+ - ~/.claude/rules/agent-teams.md Pattern C 多维度审查 + 防呆清单 + 完整生命周期
83
+ - workflows/capabilities.yaml — agent-teams-{create,send-message,shutdown} + 4 specialist
84
+ - workflows/judgments/stage-routing.yaml — verify-multispec-critical-release trigger
85
+ - workflows/judgments/parallelism-gate.yaml — agent-teams-upgrade.fires (5 OR-chain)
86
+ - workflows/verify-work/workflow.yaml v2 SHIPPED phase 09-agent-team-multispecialist sister verbatim
@@ -0,0 +1,58 @@
1
+ # workflows/verify/multispec/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.13e
2
+ #
3
+ # Stage ④.h verify sub-workflow — 4-specialist Agent Team Pattern C 多维度审查 critical-release upgrade
4
+ # (sister ~/.claude/CLAUDE.md "Verify 阶段 — 4-specialist Agent Team Pattern C" verbatim +
5
+ # ~/.claude/rules/agent-teams.md L42-L52 Pattern C 多维度审查 ≥3 specialist 互相质询 NOT fire-and-forget)。
6
+ #
7
+ # Sister refs:
8
+ # - ~/.claude/CLAUDE.md "Verify 阶段 — 关键发布 / 大重构 PR 升级 Agent Team Pattern C" verbatim
9
+ # - ~/.claude/rules/agent-teams.md Pattern C 多维度审查 (≥3 specialist lead 委派 + 互相质询)
10
+ # - workflows/judgments/stage-routing.yaml verify-multispec-critical-release trigger
11
+ # - workflows/judgments/parallelism-gate.yaml agent-teams-upgrade.fires (5 OR-chain)
12
+ # - workflows/capabilities.yaml — agent-teams-create / agent-teams-send-message / agent-teams-shutdown
13
+ # + code-review / gstack-review / gstack-cso / gstack-qa (4 specialist 互相质询)
14
+ # - workflows/verify-work/workflow.yaml v2 SHIPPED phase 09-agent-team-multispecialist sister pattern
15
+ # - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 verify/multispec example verbatim
16
+ #
17
+ # Cleanup mandatory per ~/.claude/rules/agent-teams.md 防呆清单 (SendMessage shutdown_request +
18
+ # TeamDelete) — engine-level wiring (phase 02-team-cleanup capability agent-teams-shutdown)。
19
+ # Token estimate prereq per agent-teams.md L34: team_cost < 2 × subagent_cost (engine-level check)。
20
+
21
+ schema_version: harnessed.workflow.v3
22
+ workflow: verify-multispec
23
+ description: |
24
+ Stage ④.h 4-specialist Agent Team Pattern C 多维度审查 (关键发布 / 大重构 PR 升级,
25
+ code-review + gstack-review + gstack-cso + gstack-qa 4 teammate 互相 SendMessage 质询,
26
+ NOT fire-and-forget subagent fan-out)。Cleanup mandatory: shutdown_request + TeamDelete
27
+ (sister ~/.claude/rules/agent-teams.md 防呆清单)。
28
+
29
+ disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
30
+ tools_available:
31
+ - agent-teams-create
32
+ - agent-teams-send-message
33
+ - agent-teams-shutdown
34
+ - code-review
35
+ - gstack-review
36
+ - gstack-cso
37
+ - gstack-qa
38
+
39
+ phases:
40
+ - id: 01-team-create
41
+ name: 4-specialist Agent Team create (Pattern C 多维度审查 critical-release upgrade)
42
+ upstream: claude-platform
43
+ capability: '{{ capabilities.agent-teams-create.cmd }}'
44
+ model: opus
45
+ parallelism: judgments.parallelism-gate.agent-teams-upgrade.fires
46
+ on:
47
+ - if: 'phase.is_major_release == true or phase.is_large_refactor == true'
48
+ action: invoke
49
+ - if: 'phase.is_major_release == false and phase.is_large_refactor == false'
50
+ action: skip
51
+ max_iterations: 1
52
+
53
+ - id: 02-team-cleanup
54
+ name: Agent Team cleanup (shutdown_request + TeamDelete 防呆清单)
55
+ upstream: claude-platform
56
+ capability: '{{ capabilities.agent-teams-shutdown.cmd }}'
57
+ model: haiku
58
+ max_iterations: 1
@@ -0,0 +1,71 @@
1
+ ---
2
+ name: verify-paranoid
3
+ description: |
4
+ Stage ④.c verify sub-workflow — gstack /review Paranoid Staff Engineer 关键模块 PR 前强制
5
+ (sister ~/.claude/CLAUDE.md "🔒 关键模块 PR 前强制" verbatim)。Gate:
6
+ judgments.stage-routing.verify-paranoid-critical.fires (phase.is_critical_module == true) —
7
+ 默认 critical fire only; 非关键模块 skip (sister CLAUDE.md "关键模块" 限定语)。
8
+ schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
9
+ (gstack-review) + 1 phase (gate ref is_critical_module conditional)。
10
+ Triggered by harnessed CLI `harnessed verify-paranoid --phase <num>` or slash command
11
+ `/verify-paranoid` after `harnessed setup`.
12
+ trigger_phrases:
13
+ - "verify paranoid"
14
+ - "paranoid staff engineer review"
15
+ - "关键模块审查"
16
+ - "gstack review"
17
+ - "跑 verify-paranoid"
18
+ ---
19
+
20
+ # verify-paranoid workflow (v3)
21
+
22
+ ## Overview
23
+
24
+ 1-phase sub-workflow mapping CLAUDE.md "gstack 治理关卡 🔒 关键模块 PR 前强制 — `/review`"
25
+ onto harnessed runtime (Phase v3.0-3.4 W0.12 — D-04 Stage ④ Verify 7 sub + D-12 gstack
26
+ 治理关卡 + Pattern A sub-workflow ship)。
27
+
28
+ | phase | id | upstream | model | capability | gate |
29
+ | ----- | -- | -------- | ----- | ---------- | ---- |
30
+ | 1 | `01-review` | gstack | opus | `{{ capabilities.gstack-review.cmd }}` | `judgments.stage-routing.verify-paranoid-critical.fires` |
31
+
32
+ Per-phase config loads from `workflows/verify/paranoid/workflow.yaml`; engine 4-level gate
33
+ resolver evaluates `phase.is_critical_module == true` via expr-eval — true 则 invoke gstack
34
+ `/review`, false 则 skip (chain_isolation 3 铁律 R20.16 sister verify-work v2 phase 04)。
35
+
36
+ ## Capability refs
37
+
38
+ Sister `workflows/capabilities.yaml` entries:
39
+ - `gstack-review` — Bucket 3 治理关卡 (impl: gstack, cmd: /review,
40
+ fires_when: phase.is_critical_module == true)
41
+
42
+ ## Gate ref
43
+
44
+ Sister `workflows/judgments/stage-routing.yaml`:
45
+ - `verify-paranoid-critical.fires` — `phase.stage == 'verify' and phase.is_critical_module == true`
46
+ (默认 critical fire only; 普通 PR 应跳过 — gstack-review 是 Paranoid Staff Engineer 重武器)
47
+
48
+ ## Routing rules (sister CLAUDE.md "gstack 治理关卡")
49
+
50
+ - ✅ **触发**: 关键模块 PR 前 (auth / payment / data migration / core algorithm 等)
51
+ - ❌ **跳过**: 常规 PR / docs / config / 非核心 module
52
+
53
+ ## CLI invocation
54
+
55
+ ```bash
56
+ # Dry-run preview — arbitrate-only, never spawns SDK.
57
+ harnessed verify-paranoid --phase <num> --dry-run --non-interactive
58
+
59
+ # Apply path — real SDK spawn (gate eval true 时).
60
+ harnessed verify-paranoid --phase <num> --apply
61
+ ```
62
+
63
+ ## References
64
+
65
+ - D-04 Stage ④ Verify 7 sub 分解
66
+ - D-12 gstack 治理关卡强制
67
+ - ~/.claude/CLAUDE.md "gstack 治理关卡 🔒 关键模块 PR 前强制" verbatim
68
+ - workflows/capabilities.yaml — gstack-review
69
+ - workflows/judgments/stage-routing.yaml — verify-paranoid-critical trigger
70
+ - workflows/defaults.yaml — ralph_max_iterations.verify-paranoid.* values (W2.2 backfill)
71
+ - workflows/verify-work/workflow.yaml v2 SHIPPED phase 04-gstack-review-conditional sister verbatim
@@ -0,0 +1,30 @@
1
+ # workflows/verify/paranoid/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.12
2
+ #
3
+ # Stage ④.c verify sub-workflow — gstack /review Paranoid Staff Engineer 关键模块 PR 前强制
4
+ # (sister ~/.claude/CLAUDE.md "🔒 关键模块 PR 前强制" verbatim)。
5
+ #
6
+ # Sister refs:
7
+ # - ~/.claude/CLAUDE.md "gstack 治理关卡 🔒 关键模块 PR 前强制" verbatim
8
+ # - workflows/judgments/stage-routing.yaml verify-paranoid-critical trigger (phase.is_critical_module)
9
+ # - workflows/capabilities.yaml — gstack-review (Bucket 3 治理关卡, impl: gstack, cmd: /review)
10
+ # - workflows/verify-work/workflow.yaml v2 SHIPPED phase 04-gstack-review-conditional sister pattern
11
+ # - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 verify/paranoid example verbatim
12
+
13
+ schema_version: harnessed.workflow.v3
14
+ workflow: verify-paranoid
15
+ description: |
16
+ Stage ④.c gstack /review Paranoid Staff Engineer 关键模块 PR 前强制 (sister CLAUDE.md
17
+ "🔒 关键模块 PR 前强制")。Gate: stage-routing.verify-paranoid-critical.fires (phase.is_critical_module)
18
+ — 默认 critical fire only; 非关键模块 skip (sister CLAUDE.md "关键模块" 限定语)。
19
+
20
+ disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
21
+ tools_available: [gstack-review]
22
+
23
+ phases:
24
+ - id: 01-review
25
+ name: gstack-review (Paranoid Staff Engineer 视角 — 关键模块 PR 前强制 🔒)
26
+ upstream: gstack
27
+ capability: '{{ capabilities.gstack-review.cmd }}'
28
+ model: opus
29
+ gate: judgments.stage-routing.verify-paranoid-critical.fires
30
+ max_iterations: '{{ defaults.ralph_max_iterations.verify-paranoid.01-review }}'
@@ -0,0 +1,67 @@
1
+ ---
2
+ name: verify-progress
3
+ description: |
4
+ Stage ④.a verify sub-workflow — gsd-verify-work + gsd-progress 必跑串行 (verify-work 起点)
5
+ + planning-with-files progress.md 持久化 (sister ~/.claude/CLAUDE.md "Verify 阶段" verbatim
6
+ 必跑串行 — gsd-verify-work UAT-driven acceptance + gsd-progress 状态同步 顺序不可调换)。
7
+ schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
8
+ (gsd-verify-work + gsd-progress + planning-with-files) + 3 phases (serial 01→02 + persist
9
+ progress.md sink)。Triggered by harnessed CLI `harnessed verify-progress --phase <num>` or
10
+ slash command `/verify-progress` after `harnessed setup`.
11
+ trigger_phrases:
12
+ - "verify progress"
13
+ - "进度同步"
14
+ - "gsd verify work"
15
+ - "ROADMAP 状态同步"
16
+ - "跑 verify-progress"
17
+ ---
18
+
19
+ # verify-progress workflow (v3)
20
+
21
+ ## Overview
22
+
23
+ 3-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 必跑串行" 起点 onto harnessed runtime
24
+ (Phase v3.0-3.4 W0.10 — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 ref + Pattern A
25
+ sub-workflow ship)。
26
+
27
+ | phase | id | upstream | model | capability / invokes | mode / artifacts |
28
+ | ----- | -- | -------- | ----- | -------------------- | ---------------- |
29
+ | 1 | `01-gsd-verify-work` | gsd | sonnet | `{{ capabilities.gsd-verify-work.cmd }}` | serial — UAT-driven acceptance |
30
+ | 2 | `02-gsd-progress` | gsd | haiku | `{{ capabilities.gsd-progress.cmd }}` | serial — ROADMAP/STATE/REQUIREMENTS 同步 |
31
+ | 3 | `03-progress-update` | planning-with-files | haiku | `{{ capabilities.planning-with-files.cmd }}` + `invokes: /plan` | `artifacts_expected: [progress.md]` |
32
+
33
+ Per-phase config loads from `workflows/verify/progress/workflow.yaml`; engine spawns each
34
+ phase as a sub-agent via `@anthropic-ai/claude-agent-sdk` 0.3.142+ in serial mode (顺序锁定 —
35
+ gsd-verify-work UAT 必先于 gsd-progress 状态同步)。
36
+
37
+ ## Capability refs
38
+
39
+ Sister `workflows/capabilities.yaml` entries:
40
+ - `gsd-verify-work` — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-verify-work)
41
+ - `gsd-progress` — Bucket 2 special-purpose (impl: gsd, cmd: /gsd-progress)
42
+ - `planning-with-files` — Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
43
+
44
+ ## Routing rules (sister CLAUDE.md "Verify 阶段")
45
+
46
+ 总 fire 当 `phase.stage == 'verify'` (sister `workflows/judgments/stage-routing.yaml`
47
+ verify-progress-always trigger)。无 skip 条件 — verify-work 起点必跑。
48
+
49
+ ## CLI invocation
50
+
51
+ ```bash
52
+ # Dry-run preview — arbitrate-only, never spawns SDK.
53
+ harnessed verify-progress --phase <num> --dry-run --non-interactive
54
+
55
+ # Apply path — real SDK spawn + 3-phase serial chain.
56
+ harnessed verify-progress --phase <num> --apply
57
+ ```
58
+
59
+ ## References
60
+
61
+ - D-04 Stage ④ Verify 7 sub 分解
62
+ - D-12 gstack 治理关卡 ref (verify-paranoid 后续 sub)
63
+ - ~/.claude/CLAUDE.md "Verify 阶段 — gsd-verify-work + gsd-progress 必跑串行" verbatim
64
+ - workflows/capabilities.yaml — gsd-verify-work / gsd-progress / planning-with-files
65
+ - workflows/judgments/stage-routing.yaml — verify-progress-always trigger
66
+ - workflows/defaults.yaml — ralph_max_iterations.verify-progress.* values (W2.2 backfill)
67
+ - workflows/verify-work/workflow.yaml v2 SHIPPED phase 01-02 sister verbatim pattern
@@ -0,0 +1,44 @@
1
+ # workflows/verify/progress/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.10
2
+ #
3
+ # Stage ④.a verify sub-workflow — gsd-verify-work + gsd-progress 必跑串行 (verify-work 起点)
4
+ # + planning-with-files persist (progress.md sink, sister CLAUDE.md "Verify 阶段" verbatim)。
5
+ #
6
+ # Sister refs:
7
+ # - ~/.claude/CLAUDE.md "Verify 阶段" 章节 verbatim (gsd-verify-work + gsd-progress 必跑串行)
8
+ # - workflows/judgments/stage-routing.yaml verify-progress-always trigger (总 fire 当 stage=='verify')
9
+ # - workflows/capabilities.yaml — gsd-verify-work / gsd-progress / planning-with-files
10
+ # - workflows/verify-work/workflow.yaml v2 SHIPPED phase 01-02 verbatim pattern
11
+ # - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 verify/progress example verbatim
12
+
13
+ schema_version: harnessed.workflow.v3
14
+ workflow: verify-progress
15
+ description: |
16
+ Stage ④.a GSD /gsd-verify-work + /gsd-progress 必跑串行 (verify-work 起点) + planning-with-files
17
+ progress.md persist。Sister CLAUDE.md "Verify 阶段" 必跑串行 verbatim — gsd-verify-work UAT-driven
18
+ conversational acceptance + gsd-progress 状态同步 (ROADMAP/STATE/REQUIREMENTS) 顺序不可调换。
19
+
20
+ disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
21
+ tools_available: [gsd-verify-work, gsd-progress, planning-with-files]
22
+
23
+ phases:
24
+ - id: 01-gsd-verify-work
25
+ name: gsd-verify-work (UAT-driven conversational verification + acceptance criteria check)
26
+ upstream: gsd
27
+ capability: '{{ capabilities.gsd-verify-work.cmd }}'
28
+ model: sonnet
29
+ max_iterations: '{{ defaults.ralph_max_iterations.verify-progress.01-gsd-verify-work }}'
30
+
31
+ - id: 02-gsd-progress
32
+ name: gsd-progress (状态同步 — ROADMAP/STATE/REQUIREMENTS 更新)
33
+ upstream: gsd
34
+ capability: '{{ capabilities.gsd-progress.cmd }}'
35
+ model: haiku
36
+ max_iterations: 2
37
+
38
+ - id: 03-progress-update
39
+ name: planning-with-files progress.md (verify 进度持久化)
40
+ upstream: planning-with-files
41
+ capability: '{{ capabilities.planning-with-files.cmd }}'
42
+ invokes: '/plan'
43
+ model: haiku
44
+ artifacts_expected: [progress.md]
@@ -0,0 +1,73 @@
1
+ ---
2
+ name: verify-qa
3
+ description: |
4
+ Stage ④.d verify sub-workflow — gstack /qa 端到端 QA 验收 (has_ui_changes 触发, 可选 conditional,
5
+ sister ~/.claude/CLAUDE.md "Verify 阶段 — 可选 /qa" verbatim)。
6
+ schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
7
+ (gstack-qa + playwright-cli + playwright-test + webapp-testing) + 1 phase (gate ref
8
+ has_ui_changes conditional)。
9
+ Triggered by harnessed CLI `harnessed verify-qa --phase <num>` or slash command
10
+ `/verify-qa` after `harnessed setup`.
11
+ trigger_phrases:
12
+ - "verify qa"
13
+ - "端到端 QA"
14
+ - "E2E 验收"
15
+ - "gstack qa"
16
+ - "跑 verify-qa"
17
+ ---
18
+
19
+ # verify-qa workflow (v3)
20
+
21
+ ## Overview
22
+
23
+ 1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 可选 /qa" onto harnessed runtime
24
+ (Phase v3.0-3.4 W0.13a — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 + Pattern A
25
+ sub-workflow ship)。
26
+
27
+ | phase | id | upstream | model | capability | gate |
28
+ | ----- | -- | -------- | ----- | ---------- | ---- |
29
+ | 1 | `01-qa` | gstack | sonnet | `{{ capabilities.gstack-qa.cmd }}` | `judgments.stage-routing.verify-qa-ui.fires` |
30
+
31
+ Per-phase config loads from `workflows/verify/qa/workflow.yaml`; engine 4-level gate resolver
32
+ evaluates `phase.has_ui_changes == true` via expr-eval — true 则 invoke gstack `/qa` (端到端
33
+ QA 验收 + UI dogfood), false 则 skip。
34
+
35
+ ## Capability refs
36
+
37
+ Sister `workflows/capabilities.yaml` entries:
38
+ - `gstack-qa` — Bucket 3 治理关卡 (impl: gstack, cmd: /qa, fires_when: has_ui_changes)
39
+ - `playwright-cli` — Bucket 2 special-purpose (impl: npm-cli, browser_probe)
40
+ - `playwright-test` — Bucket 2 special-purpose (impl: npm-cli, e2e_test typescript)
41
+ - `webapp-testing` — Bucket 2 special-purpose (impl: gstack, e2e_test python)
42
+
43
+ ## Gate ref
44
+
45
+ Sister `workflows/judgments/stage-routing.yaml`:
46
+ - `verify-qa-ui.fires` — `phase.stage == 'verify' and phase.has_ui_changes == true`
47
+
48
+ ## Routing rules (sister ~/.claude/rules/web-testing.md)
49
+
50
+ - 写测试 提交 repo / CI 跑 → `@playwright/test` (默认 frontend/e2e/*.spec.ts)
51
+ - 探查 / 调试 / 一次性确认 → `playwright-cli` (token 最省)
52
+ - setup 需 Python 后端 (Tortoise ORM / pandas) → `webapp-testing` skill
53
+ - 性能 / a11y / 内存诊断 → 不在此 sub-workflow,用 `chrome-devtools-mcp`
54
+
55
+ ## CLI invocation
56
+
57
+ ```bash
58
+ # Dry-run preview — arbitrate-only, never spawns SDK.
59
+ harnessed verify-qa --phase <num> --dry-run --non-interactive
60
+
61
+ # Apply path — real SDK spawn (gate eval true 时).
62
+ harnessed verify-qa --phase <num> --apply
63
+ ```
64
+
65
+ ## References
66
+
67
+ - D-04 Stage ④ Verify 7 sub 分解
68
+ - D-12 gstack 治理关卡可选
69
+ - ~/.claude/CLAUDE.md "Verify 阶段 — 可选 /qa" verbatim
70
+ - ~/.claude/rules/web-testing.md — 三层职责矩阵 (脑 / 手 / 筋骨)
71
+ - workflows/capabilities.yaml — gstack-qa / playwright-cli / playwright-test / webapp-testing
72
+ - workflows/judgments/stage-routing.yaml — verify-qa-ui trigger
73
+ - workflows/verify-work/workflow.yaml v2 SHIPPED phase 05-qa-conditional sister verbatim
@@ -0,0 +1,31 @@
1
+ # workflows/verify/qa/workflow.yaml — Phase v3.0-3.4 W0 T3.4.W0.13a
2
+ #
3
+ # Stage ④.d verify sub-workflow — gstack /qa 端到端 QA 验收 (has_ui_changes 触发, 可选 conditional)
4
+ # (sister ~/.claude/CLAUDE.md "Verify 阶段" "可选 /qa" verbatim)。
5
+ #
6
+ # Sister refs:
7
+ # - ~/.claude/CLAUDE.md "Verify 阶段 — 可选 /qa" 章节
8
+ # - workflows/judgments/stage-routing.yaml verify-qa-ui trigger (has_ui_changes)
9
+ # - workflows/capabilities.yaml — gstack-qa (Bucket 3 治理关卡, impl: gstack, cmd: /qa)
10
+ # - workflows/verify-work/workflow.yaml v2 SHIPPED phase 05-qa-conditional sister pattern
11
+ # - .planning/phase-v3.0-3.2/RESEARCH-workflows.md § Area 2 verify/qa example verbatim
12
+
13
+ schema_version: harnessed.workflow.v3
14
+ workflow: verify-qa
15
+ description: |
16
+ Stage ④.d gstack /qa 端到端 QA 验收 (has_ui_changes 触发, 可选 conditional)。
17
+ Gate: judgments.stage-routing.verify-qa-ui.fires (phase.has_ui_changes == true) —
18
+ frontend / E2E module fire only; 后端 / docs PR skip。tools_available 包含
19
+ playwright-cli / playwright-test / webapp-testing 配套 E2E test 工具链。
20
+
21
+ disciplines_applied: [karpathy, output-style, language, operational, priority, protocols]
22
+ tools_available: [gstack-qa, playwright-cli, playwright-test, webapp-testing]
23
+
24
+ phases:
25
+ - id: 01-qa
26
+ name: gstack-qa (端到端 QA 验收 — has_ui_changes 触发)
27
+ upstream: gstack
28
+ capability: '{{ capabilities.gstack-qa.cmd }}'
29
+ model: sonnet
30
+ gate: judgments.stage-routing.verify-qa-ui.fires
31
+ max_iterations: 3
@@ -0,0 +1,67 @@
1
+ ---
2
+ name: verify-security
3
+ description: |
4
+ Stage ④.e verify sub-workflow — gstack /cso 安全审查 OWASP/auth/secrets (has_auth_or_secrets
5
+ 触发, 可选 conditional, sister ~/.claude/CLAUDE.md "Verify 阶段 — 可选 /cso" verbatim)。
6
+ schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available
7
+ (gstack-cso) + 1 phase (gate ref has_auth_or_secrets conditional)。
8
+ Triggered by harnessed CLI `harnessed verify-security --phase <num>` or slash command
9
+ `/verify-security` after `harnessed setup`.
10
+ trigger_phrases:
11
+ - "verify security"
12
+ - "安全审查"
13
+ - "OWASP audit"
14
+ - "gstack cso"
15
+ - "跑 verify-security"
16
+ ---
17
+
18
+ # verify-security workflow (v3)
19
+
20
+ ## Overview
21
+
22
+ 1-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 可选 /cso" onto harnessed runtime
23
+ (Phase v3.0-3.4 W0.13b — D-04 Stage ④ Verify 7 sub + D-12 gstack 治理关卡 + Pattern A
24
+ sub-workflow ship)。
25
+
26
+ | phase | id | upstream | model | capability | gate |
27
+ | ----- | -- | -------- | ----- | ---------- | ---- |
28
+ | 1 | `01-cso` | gstack | opus | `{{ capabilities.gstack-cso.cmd }}` | `judgments.stage-routing.verify-security-secrets.fires` |
29
+
30
+ Per-phase config loads from `workflows/verify/security/workflow.yaml`; engine 4-level gate
31
+ resolver evaluates `phase.has_auth_or_secrets == true` via expr-eval — true 则 invoke gstack
32
+ `/cso` (OWASP / auth / credentials / secrets 全面审查), false 则 skip。
33
+
34
+ ## Capability refs
35
+
36
+ Sister `workflows/capabilities.yaml` entries:
37
+ - `gstack-cso` — Bucket 3 治理关卡 (impl: gstack, cmd: /cso,
38
+ fires_when: phase.stage == 'verify' AND phase.has_auth_or_secrets == true)
39
+
40
+ ## Gate ref
41
+
42
+ Sister `workflows/judgments/stage-routing.yaml`:
43
+ - `verify-security-secrets.fires` — `phase.stage == 'verify' and phase.has_auth_or_secrets == true`
44
+
45
+ ## Routing rules
46
+
47
+ - ✅ **触发**: auth flow / session / credentials / API keys / SQL injection 路径 / OWASP top 10 area
48
+ - ❌ **跳过**: docs / 纯 UI styling / 内部 refactor / non-security PR
49
+
50
+ ## CLI invocation
51
+
52
+ ```bash
53
+ # Dry-run preview — arbitrate-only, never spawns SDK.
54
+ harnessed verify-security --phase <num> --dry-run --non-interactive
55
+
56
+ # Apply path — real SDK spawn (gate eval true 时).
57
+ harnessed verify-security --phase <num> --apply
58
+ ```
59
+
60
+ ## References
61
+
62
+ - D-04 Stage ④ Verify 7 sub 分解
63
+ - D-12 gstack 治理关卡可选
64
+ - ~/.claude/CLAUDE.md "Verify 阶段 — 可选 /cso" verbatim
65
+ - workflows/capabilities.yaml — gstack-cso
66
+ - workflows/judgments/stage-routing.yaml — verify-security-secrets trigger
67
+ - workflows/verify-work/workflow.yaml v2 SHIPPED phase 06-cso-conditional sister verbatim