plan

Solid

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 slash command `/plan` (bare per ADR 0030 namespace policy D-02 LOCK) after `harnessed setup`.

AI & Automation 2 stars 1 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 78/100

Stars 20%
16
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# plan master orchestrator (v3) ## Overview 4-stage cadence Stage ② master orchestrator delegating to 2 sequential sub-workflows (bundled Plan-stage cadence + 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`) - **禁...

Details

Author
easyinplay
Repository
easyinplay/harnessed
Created
2 months ago
Last Updated
today
Language
TypeScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

plan-architecture

Stage ②.a 架构层 plan sub-workflow — gstack /plan-eng-review (复杂架构强制治理关卡; bundled plan-stage cadence: mandatory before complex-architecture phases)。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`.

2 Updated today
easyinplay
AI & Automation Solid

plan-phase

Stage ②.b 计划层 plan sub-workflow — GSD /gsd-plan-phase Wave A research + Wave B planner + Wave C plan-checker + planning-with-files Claude Code plugin /plan 持久化 task_plan.md + progress.md (bundled Plan-stage cadence: GSD + planning-with-files)。Stage ② 铁律: dual capability (GSD orchestration + planning-with-files plugin)。schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available [gsd-plan-phase, planning-with-files] + 2 phases (01-gsd-plan + 02-persist)。Triggered by harnessed CLI `harnessed plan-phase --phase <num>` or slash command `/plan-phase` after `harnessed setup`.

2 Updated today
easyinplay
AI & Automation Solid

discuss

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 slash command `/discuss` (bare per ADR 0030 namespace policy D-02 LOCK) after `harnessed setup`.

2 Updated today
easyinplay