maestro-flow 0.5.2 → 0.5.31

package/.agy/skills/maestro-player/SKILL.md

@@ -14,170 +14,170 @@ allowed-tools:
   - view_file
   - write_to_file
 ---
-<purpose>
-Load workflow template (from maestro-composer) → bind context variables → execute DAG nodes in topological order → persist state at checkpoints → support resume.
-
-Session: `.workflow/.maestro/player-{YYYYMMDD-HHmmss}/status.json`
-</purpose>
-
-<context>
-$ARGUMENTS — template slug/path, or flags.
-
-**Flags**:
-- `--context key=value`: Bind context variables (repeatable)
-- `-c [session-id]`: Resume paused/interrupted session
-- `--list`: List available templates from index.json
-- `--dry-run`: Show execution plan without executing
-
-**Node execution mechanisms**:
-
-| Node type | Mechanism | Blocking |
-|-----------|-----------|----------|
-| skill | `Skill(skill, args)` | sync |
-| command | `Skill(skill, args)` | sync |
-| cli | `maestro delegate --to tool --mode mode` via `run_command(run_in_background: true)` | async, STOP + wait |
-| agent | `invoke_subagent([{ TypeName: "<TypeName>", Role: "<Role>", Prompt: "<Prompt>", Workspace: "inherit" }])` | configurable |
-| checkpoint | State save + optional user pause | — |
-
-**Runtime reference resolution** in args_template:
-
-| Reference | Resolves to |
-|-----------|-------------|
-| `{variable}` | session context[variable] |
-| `{N-001.session_id}` | node's session_id |
-| `{N-001.output_path}` | node's output_path |
-| `{prev_session_id}` | previous non-checkpoint node's session_id |
-| `{prev_output_path}` | previous non-checkpoint node's output_path |
-
-**Session schema** (status.json — must align with maestro.md tracking):
-```json
-{
-  "session_id": "player-<YYYYMMDD>-<HHmmss>",
-  "status": "running|paused|completed|failed|aborted",
-  "template_id": "wft-<slug>-<date>",
-  "template_path": "<path>",
-  "auto_mode": false,
-  "context": { "goal": "..." },
-  "steps": [{
-    "index": 0, "node_id": "N-001", "skill": "<executor>",
-    "args": "<resolved>", "type": "skill|cli|agent|checkpoint",
-    "status": "pending|running|completed|skipped|failed",
-    "session_id": null, "output_path": null, "artifacts": []
-  }],
-  "current_step": 0,
-  "last_checkpoint": null
-}
-```
-</context>
-
-<state_machine>
-
-<states>
-S_ROUTE        — 入口路由（list/resume/dry-run/normal）     PERSIST: —
-S_RESUME       — 恢复已暂停 session                         PERSIST: —
-S_LOAD         — 加载模板、收集变量、绑定引用                 PERSIST: —
-S_INIT         — 创建 session、拓扑排序、初始化 steps         PERSIST: status.json
-S_EXEC_LOOP    — 逐步执行（核心循环）                        PERSIST: status.json (每步更新)
-S_COMPLETE     — 标记完成、输出摘要                           PERSIST: status.json (final)
-</states>
-
-<transitions>
-
-S_ROUTE:
-  → handleList    WHEN: --list                              DO: scan index.json, display templates
-  → S_RESUME      WHEN: -c flag
-  → S_LOAD        WHEN: template slug/path provided
-  → handleList    WHEN: no args                             DO: display templates + ask_question
-
-S_RESUME:
-  → S_EXEC_LOOP   WHEN: session found                      DO: A_RESUME_SESSION
-  → ERROR(E004)   WHEN: no session found
-
-S_LOAD:
-  → S_INIT        DO: A_LOAD_AND_BIND
-
-S_INIT:
-  → END           WHEN: --dry-run                           DO: display execution plan
-  → S_EXEC_LOOP   DO: A_INIT_SESSION (topological sort → steps[], write status.json, display banner)
-
-S_EXEC_LOOP:
-  → S_EXEC_LOOP   WHEN: step completed, more steps          DO: A_EXECUTE_STEP → advance current_step
-  → S_COMPLETE     WHEN: all steps completed
-  → END           WHEN: checkpoint pause                    DO: set status=paused, display resume command
-  → END           WHEN: abort chosen                        DO: set status=aborted, save progress
-  GUARD: cli nodes → run_command(run_in_background: true) + STOP, wait for callback
-  GUARD: on failure → on_fail: skip (log, advance) | retry (once) | abort (ask_question: Retry/Skip/Abort)
-  GUARD: after step 3+ → display context hint "可随时 /maestro-player -c 恢复"
-
-S_COMPLETE:
-  → END           DO: A_COMPLETE_SESSION
-
-</transitions>
-
-<actions>
-
-### A_RESUME_SESSION
-
-1. If session-id: load status.json. If none: scan player-*/status.json for running|paused.
-2. Reset any "running" steps to "pending" (interrupted mid-execution)
-3. Set current_step to resume point after last_checkpoint
-4. Enter S_EXEC_LOOP
-
-### A_LOAD_AND_BIND
-
-1. Resolve template: absolute path → as-is; relative → from cwd; slug → index.json lookup
-2. Parse `--context key=value` pairs
-3. Validate template (template_id, nodes, edges, context_schema required)
-4. Collect missing required variables via ask_question
-5. Bind {variable} placeholders (leave {N-xxx.field} and {prev_*} for runtime)
-
-### A_INIT_SESSION
-
-1. Generate session_id: player-{YYYYMMDD-HHmmss}
-2. Topological sort (Kahn's algorithm) → flatten to steps[] (parallel nodes share batch index)
-3. All steps status: "pending"
-4. Write status.json
-
-### A_EXECUTE_STEP
-
-1. Resolve runtime references ({N-xxx.field}, {prev_*}) in args
-2. Set step status="running", write status.json
-3. Execute by type:
-   - **skill/command**: `Skill(skill, resolved_args)` → extract session_id, output_path, artifacts
-   - **cli**: `run_command(run_in_background: true)` → STOP, wait for callback → `maestro delegate output <id>`
-   - **agent**: `invoke_subagent([{ TypeName: "<TypeName>", Role: "<Role>", Prompt: "<Prompt>", Workspace: "inherit" }])`
-   - **checkpoint**: write checkpoint snapshot. If auto_continue==false:
-     ask_question (single-select, header: "Checkpoint"):
-     - **Continue** — proceed to next step
-     - **Pause** — save progress, exit (resume with `-c`)
-     - **Abort** — stop workflow
-4. Set step status="completed" (or "skipped"/"failed"), write status.json
-
-### A_COMPLETE_SESSION
-
-Set status="completed", completed_at. Display summary: session, template, steps completed, context, per-step results, artifacts, session dir.
-ask_question (single-select, header: "完成"):
-- **Keep session** — preserve artifacts for reference
-- **Run again** — re-execute with same template
-- **Done** — clean up and exit
-
-</actions>
-
-</state_machine>
-
-<error_codes>
-| Code | Condition | Recovery |
-|------|-----------|----------|
-| E001 | Template not found | Show --list, suggest closest match |
-| E002 | Template JSON invalid (missing template_id/nodes/edges) | Point to template file for fix |
-| E004 | Resume session not found | List available player-*/ sessions |
-| E005 | DAG cycle in template | Point to template, suggest --edit |
-| E006 | Node execution failed + abort chosen | Save state, suggest `-c` resume |
-</error_codes>
-
-<success_criteria>
-- [ ] Template loaded, variables bound, session created with topological steps
-- [ ] status.json written after every step change (resume-safe)
-- [ ] CLI nodes use run_command(run_in_background) + STOP pattern
-- [ ] Checkpoints saved, resume via -c works
-</success_criteria>
+<purpose>
+Load workflow template (from maestro-composer) → bind context variables → execute DAG nodes in topological order → persist state at checkpoints → support resume.
+
+Session: `.workflow/.maestro/player-{YYYYMMDD-HHmmss}/status.json`
+</purpose>
+
+<context>
+$ARGUMENTS — template slug/path, or flags.
+
+**Flags**:
+- `--context key=value`: Bind context variables (repeatable)
+- `-c [session-id]`: Resume paused/interrupted session
+- `--list`: List available templates from index.json
+- `--dry-run`: Show execution plan without executing
+
+**Node execution mechanisms**:
+
+| Node type | Mechanism | Blocking |
+|-----------|-----------|----------|
+| skill | `Skill(skill, args)` | sync |
+| command | `Skill(skill, args)` | sync |
+| cli | `maestro delegate --to tool --mode mode` via `run_command(run_in_background: true)` | async, STOP + wait |
+| agent | `invoke_subagent([{ TypeName: "<TypeName>", Role: "<Role>", Prompt: "<Prompt>", Workspace: "inherit" }])` | configurable |
+| checkpoint | State save + optional user pause | — |
+
+**Runtime reference resolution** in args_template:
+
+| Reference | Resolves to |
+|-----------|-------------|
+| `{variable}` | session context[variable] |
+| `{N-001.session_id}` | node's session_id |
+| `{N-001.output_path}` | node's output_path |
+| `{prev_session_id}` | previous non-checkpoint node's session_id |
+| `{prev_output_path}` | previous non-checkpoint node's output_path |
+
+**Session schema** (status.json — must align with maestro.md tracking):
+```json
+{
+  "session_id": "player-<YYYYMMDD>-<HHmmss>",
+  "status": "running|paused|completed|failed|aborted",
+  "template_id": "wft-<slug>-<date>",
+  "template_path": "<path>",
+  "auto_mode": false,
+  "context": { "goal": "..." },
+  "steps": [{
+    "index": 0, "node_id": "N-001", "skill": "<executor>",
+    "args": "<resolved>", "type": "skill|cli|agent|checkpoint",
+    "status": "pending|running|completed|skipped|failed",
+    "session_id": null, "output_path": null, "artifacts": []
+  }],
+  "current_step": 0,
+  "last_checkpoint": null
+}
+```
+</context>
+
+<state_machine>
+
+<states>
+S_ROUTE        — 入口路由（list/resume/dry-run/normal）     PERSIST: —
+S_RESUME       — 恢复已暂停 session                         PERSIST: —
+S_LOAD         — 加载模板、收集变量、绑定引用                 PERSIST: —
+S_INIT         — 创建 session、拓扑排序、初始化 steps         PERSIST: status.json
+S_EXEC_LOOP    — 逐步执行（核心循环）                        PERSIST: status.json (每步更新)
+S_COMPLETE     — 标记完成、输出摘要                           PERSIST: status.json (final)
+</states>
+
+<transitions>
+
+S_ROUTE:
+  → handleList    WHEN: --list                              DO: scan index.json, display templates
+  → S_RESUME      WHEN: -c flag
+  → S_LOAD        WHEN: template slug/path provided
+  → handleList    WHEN: no args                             DO: display templates + ask_question
+
+S_RESUME:
+  → S_EXEC_LOOP   WHEN: session found                      DO: A_RESUME_SESSION
+  → ERROR(E004)   WHEN: no session found
+
+S_LOAD:
+  → S_INIT        DO: A_LOAD_AND_BIND
+
+S_INIT:
+  → END           WHEN: --dry-run                           DO: display execution plan
+  → S_EXEC_LOOP   DO: A_INIT_SESSION (topological sort → steps[], write status.json, display banner)
+
+S_EXEC_LOOP:
+  → S_EXEC_LOOP   WHEN: step completed, more steps          DO: A_EXECUTE_STEP → advance current_step
+  → S_COMPLETE     WHEN: all steps completed
+  → END           WHEN: checkpoint pause                    DO: set status=paused, display resume command
+  → END           WHEN: abort chosen                        DO: set status=aborted, save progress
+  GUARD: cli nodes → run_command(run_in_background: true) + STOP, wait for callback
+  GUARD: on failure → on_fail: skip (log, advance) | retry (once) | abort (ask_question: Retry/Skip/Abort)
+  GUARD: after step 3+ → display context hint "可随时 /maestro-player -c 恢复"
+
+S_COMPLETE:
+  → END           DO: A_COMPLETE_SESSION
+
+</transitions>
+
+<actions>
+
+### A_RESUME_SESSION
+
+1. If session-id: load status.json. If none: scan player-*/status.json for running|paused.
+2. Reset any "running" steps to "pending" (interrupted mid-execution)
+3. Set current_step to resume point after last_checkpoint
+4. Enter S_EXEC_LOOP
+
+### A_LOAD_AND_BIND
+
+1. Resolve template: absolute path → as-is; relative → from cwd; slug → index.json lookup
+2. Parse `--context key=value` pairs
+3. Validate template (template_id, nodes, edges, context_schema required)
+4. Collect missing required variables via ask_question
+5. Bind {variable} placeholders (leave {N-xxx.field} and {prev_*} for runtime)
+
+### A_INIT_SESSION
+
+1. Generate session_id: player-{YYYYMMDD-HHmmss}
+2. Topological sort (Kahn's algorithm) → flatten to steps[] (parallel nodes share batch index)
+3. All steps status: "pending"
+4. Write status.json
+
+### A_EXECUTE_STEP
+
+1. Resolve runtime references ({N-xxx.field}, {prev_*}) in args
+2. Set step status="running", write status.json
+3. Execute by type:
+   - **skill/command**: `Skill(skill, resolved_args)` → extract session_id, output_path, artifacts
+   - **cli**: `run_command(run_in_background: true)` → STOP, wait for callback → `maestro delegate output <id>`
+   - **agent**: `invoke_subagent([{ TypeName: "<TypeName>", Role: "<Role>", Prompt: "<Prompt>", Workspace: "inherit" }])`
+   - **checkpoint**: write checkpoint snapshot. If auto_continue==false:
+     ask_question (single-select, header: "Checkpoint"):
+     - **Continue** — proceed to next step
+     - **Pause** — save progress, exit (resume with `-c`)
+     - **Abort** — stop workflow
+4. Set step status="completed" (or "skipped"/"failed"), write status.json
+
+### A_COMPLETE_SESSION
+
+Set status="completed", completed_at. Display summary: session, template, steps completed, context, per-step results, artifacts, session dir.
+ask_question (single-select, header: "完成"):
+- **Keep session** — preserve artifacts for reference
+- **Run again** — re-execute with same template
+- **Done** — clean up and exit
+
+</actions>
+
+</state_machine>
+
+<error_codes>
+| Code | Condition | Recovery |
+|------|-----------|----------|
+| E001 | Template not found | Show --list, suggest closest match |
+| E002 | Template JSON invalid (missing template_id/nodes/edges) | Point to template file for fix |
+| E004 | Resume session not found | List available player-*/ sessions |
+| E005 | DAG cycle in template | Point to template, suggest --edit |
+| E006 | Node execution failed + abort chosen | Save state, suggest `-c` resume |
+</error_codes>
+
+<success_criteria>
+- [ ] Template loaded, variables bound, session created with topological steps
+- [ ] status.json written after every step change (resume-safe)
+- [ ] CLI nodes use run_command(run_in_background) + STOP pattern
+- [ ] Checkpoints saved, resume via -c works
+</success_criteria>

package/.agy/skills/maestro-quick/SKILL.md

@@ -14,66 +14,72 @@ allowed-tools:
   - view_file
   - write_to_file
 ---
-<purpose>
-Execute small, ad-hoc tasks with workflow guarantees (atomic commits, state tracking) using a shortened pipeline. Invoked for tasks that are well-understood and do not require full phase-level planning. Produces scratch task directory with plan, execution results, and optional verification. Flags --discuss and --full enable additional pipeline stages.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/quick.md
-</required_reading>
-
-<context>
-$ARGUMENTS
-
-Parse for:
-- `--full` flag -- Enables plan-checking (max 2 iterations) and post-execution verification
-- `--discuss` flag -- Decision extraction before planning (gray areas, Locked/Free/Deferred classification)
-- Remaining text as task description
-
-### Pre-load context
-
-1. **Coding specs + tools**: Run `maestro spec load --category coding` to load coding conventions and discoverable tools. Apply to implementation.
-2. **UI specs (conditional)**: If the task involves frontend/UI work (description contains component, page, style, layout, CSS, HTML, frontend), also run `maestro spec load --category ui`.
-3. **Role Knowledge**:
-   - Browse: `maestro search --category coding`
-   - Load task-relevant entries: `maestro wiki load <id1> [id2...]`
-3. All are optional — proceed without if unavailable.
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/quick.md' completely.
-
-### Artifact Verification (before completion)
-
-```
-REQUIRED_ARTIFACTS = [
-  "plan.json",                              // Task definitions
-  ".summaries/TASK-*-summary.md" (per task)  // Execution results
-]
-```
-If any artifact is missing: DO NOT report completion. Complete the missing step first.
-
-Task summaries MUST include concrete evidence of completion (files changed, tests run, commands executed) — not just "task completed successfully."
-
-**Next-step routing on completion:**
-- Task done, --full verification passed → /manage-status
-- Task done, verification found gaps → /quality-debug {issue}
-- Task done, want to sync docs → /quality-sync
-- Need a full phase workflow instead → /maestro-plan {phase}
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Task description required (no text provided) | Check arguments format, re-run with correct input |
-| E002 | error | Scratch directory creation failed | Check disk space and .workflow/ permissions |
-| W001 | warning | Verification found minor gaps | Review gaps and determine if they need fixing |
-</error_codes>
-
-<success_criteria>
-- [ ] Scratch task directory created under .workflow/scratch/
-- [ ] plan.json written with task definitions
-- [ ] All tasks executed with summaries written
-- [ ] state.json updated with scratch task entry
-- [ ] Commit created with task changes
-</success_criteria>
+<purpose>
+Execute small, ad-hoc tasks with workflow guarantees (atomic commits, state tracking) via a shortened pipeline.
+Flags --discuss and --full enable additional pipeline stages.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/quick.md
+</required_reading>
+
+<context>
+$ARGUMENTS
+
+Parse for:
+- `--full` flag -- Enables plan-checking (max 2 iterations) and post-execution verification
+- `--discuss` flag -- Decision extraction before planning (gray areas, Locked/Free/Deferred classification)
+- Remaining text as task description
+
+### Pre-load context
+
+1. **Coding specs + tools**: Run `maestro spec load --category coding` to load coding conventions and discoverable tools. Apply to implementation.
+2. **UI specs (conditional)**: If the task involves frontend/UI work (description contains component, page, style, layout, CSS, HTML, frontend), also run `maestro spec load --category ui`.
+3. **Role Knowledge**:
+   - Browse: `maestro search --category coding`
+   - Load task-relevant entries: `maestro wiki load <id1> [id2...]`
+3. All are optional — proceed without if unavailable.
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/quick.md' completely.
+
+### Artifact Verification (before completion)
+
+```
+REQUIRED_ARTIFACTS = [
+  "plan.json",                              // Task definitions
+  ".summaries/TASK-*-summary.md" (per task)  // Execution results
+]
+```
+If any artifact is missing: DO NOT report completion. Complete the missing step first.
+
+Task summaries MUST include concrete evidence of completion (files changed, tests run, commands executed) — not just "task completed successfully."
+
+</execution>
+
+<completion>
+### Next-step routing
+| Condition | Suggestion |
+|-----------|-----------|
+| Task done, --full verification passed | `/manage-status` |
+| Task done, verification found gaps | `/quality-debug {issue}` |
+| Task done, want to sync docs | `/quality-sync` |
+| Need a full phase workflow instead | `/maestro-plan {phase}` |
+</completion>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Task description required (no text provided) | Check arguments format, re-run with correct input |
+| E002 | error | Scratch directory creation failed | Check disk space and .workflow/ permissions |
+| W001 | warning | Verification found minor gaps | Review gaps and determine if they need fixing |
+</error_codes>
+
+<success_criteria>
+- [ ] Scratch task directory created under .workflow/scratch/
+- [ ] plan.json written with task definitions
+- [ ] All tasks executed with summaries written
+- [ ] state.json updated with scratch task entry
+- [ ] Commit created with task changes
+</success_criteria>

package/.agy/skills/maestro-ralph/SKILL.md

@@ -11,42 +11,8 @@ allowed-tools:
   - write_to_file
 ---
 <purpose>
-Closed-loop decision engine for the maestro workflow lifecycle.
-Reads project state → infers position → builds adaptive chain → delegates execution.
-
-Entry points:
-- **`/maestro-ralph "intent"`** — New session: infer → decompose → build → emit /goal prompt（如有 decomposition）→ dispatch ralph-execute
-- **`/maestro-ralph continue`** — Wrapper; dispatches to ralph-execute（首选直接 `/maestro-ralph-execute` 推进 step）
-- **`/maestro-ralph status`** — Display session progress
-
-> 推进规则：**step 推进由 `/maestro-ralph-execute` 负责**；ralph 仅在 build / decision 评估时介入。decision 节点由 ralph-execute 自动 `Skill("maestro-ralph")` handoff，无需用户手动切换。
-
-Initial decomposition (S_DECOMPOSE): boundary-clarified via ≤3 questions for broad intents (重构/全面/迁移/重写). 写入 status.json 的 `boundary_contract` / `execution_criteria` / `task_decomposition`，附 `/goal` prompt。
-
-Step kinds:
-- **执行 step**: ralph-execute 调 `run_command("maestro ralph next")` 加载 command .md + required_reading 全文，按 stdout 内联执行
-- **decision step**: `step.decision` 字段非空；回 ralph 评估（CLI 只读分析）
-
-Key difference from maestro coordinator:
-- maestro: static chain → one-time selection → runs all steps
-- ralph: living chain → decision nodes re-evaluate → chain grows/shrinks dynamically
-
-Session: `.workflow/.maestro/ralph-{YYYYMMDD-HHmmss}/status.json`
-Mutual invocation with `/maestro-ralph-execute` forms a self-perpetuating work loop.
-
-### Execution Flow
-
-```
- /maestro-ralph "intent" ─▶ ralph        infer → decompose → build chain
-                              │           resolves command_path per step
-                              │           writes status.json
-                              │           emits /goal prompt
-                              ▼
-                       ralph-execute  ◀─┐ 执行 step → `maestro ralph next` + inline + `ralph complete`
-                              │         │ decision step → Skill("maestro-ralph")
-                              └─────────┘ CLI writes step.completion_confirmed
-                       loop until all completion_confirmed | paused
-```
+Closed-loop decision engine: read project state → infer position → build adaptive chain → delegate execution.
+Ralph builds/evaluates; ralph-execute runs steps. Session: `.workflow/.maestro/ralph-{YYYYMMDD-HHmmss}/status.json`.
 </purpose>
 
 <context>
@@ -267,8 +233,7 @@ resolve_milestone(phase_number):
 | phase 已存在 + 无任何 artifact | `analyze` |
 | phase 已存在 + 最新 artifact = analyze | `plan` |
 | phase 已存在 + 最新 artifact = plan | `execute` |
-| phase 已存在 + 最新 artifact = execute | `verify` |
-| phase 已存在 + 最新 artifact = verify | → refine from result files |
+| phase 已存在 + 最新 artifact = execute | → refine from post-execute results |
 
 **关键不变量**：artifact 过滤按 `session.phase`，不读 `state.json.current_phase`。`phase_is_new` → 直接 `analyze`。
 
@@ -287,11 +252,13 @@ resolve_milestone(phase_number):
 | `medium` / `small` | analyze-macro → plan --from analyze:{ANL_ID} → execute → ...（跳过 roadmap + analyze-phase） |
 | `unknown` | 默认走 large 路径，post-analyze-scope 决策节点再纠正 |
 
-**Refine from verify results:**
+**Refine from post-execute results:**
+
+在 execute artifact 的 scratch dir 中检查结果文件（verification.json 由 execute 内置 gate 产出）：
 
 | Condition | Position |
 |-----------|----------|
-| verification.json: passed==false or gaps[] | `verify-failed` |
+| 无 verification.json 或 passed==false 或 gaps[] | `execute` (触发 post-execute fix loop) |
 | passed==true, no review.json | `business-test` |
 | review.json: verdict=="BLOCK" | `review-failed` |
 | review.json: verdict!="BLOCK" | `test` |
@@ -302,7 +269,7 @@ resolve_milestone(phase_number):
 
 决定下游质量管线长度。读 `session.quality_mode_override`（CLI 标志 `--quality`），无则按规则推断：
 
-| Condition | Mode | Pipeline (verify 之后) |
+| Condition | Mode | Pipeline (execute 之后) |
 |-----------|------|-------------------------|
 | Has `specs/REQ-*.md` + 当前 phase 业务范围明确 | `full` | business-test → review → test-gen → test |
 | Default | `standard` | review → test-gen (当 coverage<80%) → test |
@@ -333,7 +300,7 @@ options:
   - label: "统一规划 (Recommended)"
     description: "一次性分析+规划整个里程碑所有 phase，analyze/plan 走里程碑级，适合 phase 间关联紧密"
   - label: "独立规划"
-    description: "逐个 phase 走完整生命周期（analyze→plan→execute→verify→...），适合 phase 间独立性高"
+    description: "逐个 phase 走完整生命周期（analyze→plan→execute→...），适合 phase 间独立性高"
 ```
 
 写入 `session.planning_mode`（`"unified"` 或 `"independent"`）。`A_BUILD_STEPS` 据此决定 skill args 是否携带 `{phase}` 占位符。
@@ -367,7 +334,7 @@ narrow → derive defaults from intent + codebase, skip questions.
 { "id": "G1", "goal": "<deliverable>", "boundary": "<in/out note>",
   "done_when": "<objectively checkable condition>",
   "evidence": "verification.json|review.json|uat.md|<test path>",
-  "lifecycle": ["analyze","execute","verify"], "status": "pending" }
+  "lifecycle": ["analyze","execute"], "status": "pending" }
 ```
 `done_when` 必须客观可验证，且引用 ralph 已产出的 artifact；`lifecycle` 字段映射到产出 evidence 的生命周期 stage。
 
@@ -408,7 +375,7 @@ Generate steps from `session.lifecycle_position` to `milestone-complete`.
 3. **quality_mode 过滤**：按 `session.quality_mode` 排除不匹配 stage
 3.5. **grill auto_confirm 跳过**：`auto_confirm == true` 时删除 `grill` stage（grill 为交互式苏格拉底拷问，不支持自动模式）；brainstorm args 不含 `--from grill:*`
 4. **决策节点**：每个 Decision after 非空的 stage 之后插入 `{ decision: "<gate>", retry_count: 0, max_retries: 2, command_scope: null, command_path: null }`
-5. **goal-audit 插入**：`task_decomposition` 存在时，在最后一个 evidence-producing stage（verify/review/test）之后、`milestone-complete` 之前插入 `decision:post-goal-audit`
+5. **goal-audit 插入**：`task_decomposition` 存在时，在最后一个 evidence-producing stage（execute/review/test）之后、`milestone-complete` 之前插入 `decision:post-goal-audit`
 6. **终点硬约束**：chain 以 `milestone-complete` 结尾
 7. **goal_ref 传播**：`task_decomposition` 存在时，每个 step 按 `step.stage ∈ g.lifecycle` 匹配 `step.goal_ref = g.id`（多匹配取字典序最小）；decision 节点不打 goal_ref
 8. **占位符**：independent 保留 `{phase}` `{intent}`；unified 不带 `{phase}`
@@ -556,7 +523,7 @@ Runs only when `task_decomposition` present.
 3. 路径 B（`medium` / `small`）：
    - 删除 `goal-audit` 之前所有未完成的 `roadmap` + `analyze` (phase) step
    - 把下一个未完成的 `plan` step 改为 `maestro-plan --from analyze:{analyze_macro_id}`，去掉 `{phase}`，`source_artifact_ref = analyze:{analyze_macro_id}`
-   - 后续 `execute` / `verify` 等沿用同一 standalone scope（不带 `{phase}`，由 plan 写出的 task 列表驱动）
+   - 后续 `execute` 等沿用同一 standalone scope（不带 `{phase}`，由 plan 写出的 task 列表驱动）
 4. 路径 C（`unknown`）：
    - 非 auto_confirm → ask_question 二选一（large / medium-small）；auto_confirm → 默认 large
 5. Reindex steps，标 decision completed，write status.json
@@ -617,7 +584,7 @@ Runs only when `task_decomposition` present.
     "index": 0,
     "skill": "",                  // 执行 step 有值；decision 节点为空字符串/null
     "args": "",
-    "stage": "",                  // brainstorm|blueprint|init|analyze-macro|roadmap|analyze|plan|execute|verify|...
+    "stage": "",                  // brainstorm|blueprint|init|analyze-macro|roadmap|analyze|plan|execute|...
     "scope": null,                // "phase"|"standalone"|"milestone"|null（plan 等需要）
     "decision": null,             // 非 null → decision 节点（值为 gate 名，如 "post-execute"）；null → 执行 step
     "retry_count": 0,             // decision 节点专用