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 - Slash command: `/plan-architecture <name>` (after `harnessed setup`) ## Routing rules 触发条件 (sister CLAUDE.md "⚠️ 复杂架构前"): - 涉及多模块跨界设计 (≥3 模块协同) - 新引入核心抽象 (新 framework / 新数据模型 / 新协议) - 性能 / scaling 关键路径 - 引入显著技术债 / migration 风险 ## How to invoke !`harnessed checkpoint intent plan-architecture` > The banner above (when present) means this invocation is REGISTERED with the engine (an intent marker) — not yet compliant: the steps below (prompt → spawn → checkpoint complete) resolve it, and a per-turn `<workflow-intent>` reminde...