maestro-flow-one 0.2.27 → 0.2.29

package/maestro-flow/commands/lifecycle/impeccable.md

@@ -145,7 +145,11 @@ Layer 1 did not match. Check for chain-level keywords — even if the prompt als
 | design system, tokens, design foundation, design infrastructure | foundation |
 | real-time, live, browser | live |
 
-Ambiguous + no `-y` → AskUserQuestion.
+Ambiguous + no `-y`:
+
+AskUserQuestion (single-select, header: "意图确认"):
+- Options: top 2-3 matched chains from Layer 2 table, each with label = chain name, description = matched keywords
+- Last option: **"直接构建"** — skip chain, route to Layer 3 craft
 
 ### Layer 3: Concrete build task → Direct craft
 

package/maestro-flow/commands/lifecycle/next.md

@@ -218,7 +218,13 @@ brainstorm → blueprint → init → analyze-macro → roadmap
 执行参数: <args>
 ```
 
-`--dry-run` 展示后结束；`-y` 直接 S_EXECUTE；否则 AskUserQuestion 提供：执行 top pick / 选备选 / 修改参数 / 取消。
+`--dry-run` 展示后结束；`-y` 直接 S_EXECUTE；否则：
+
+AskUserQuestion (single-select, header: "执行确认"):
+- **执行推荐** (Recommended) — run top pick with shown args
+- **选择备选** — pick from alternative commands
+- **修改参数** — adjust args before executing
+- **取消** — do nothing
 
 </presentation>
 

package/maestro-flow/commands/lifecycle/player.md

@@ -145,13 +145,20 @@ S_COMPLETE:
    - **skill/command**: `Skill(skill, resolved_args)` → extract session_id, output_path, artifacts
    - **cli**: `Bash(run_in_background: true)` → STOP, wait for callback → `maestro delegate output <id>`
    - **agent**: `Agent(subagent_type, resolved_args)`
-   - **checkpoint**: write checkpoint snapshot. If auto_continue==false: AskUserQuestion (Continue/Pause/Abort)
+   - **checkpoint**: write checkpoint snapshot. If auto_continue==false:
+     AskUserQuestion (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.
-AskUserQuestion: Keep session / Run again / Done.
+AskUserQuestion (single-select, header: "完成"):
+- **Keep session** — preserve artifacts for reference
+- **Run again** — re-execute with same template
+- **Done** — clean up and exit
 
 </actions>
 

package/maestro-flow/commands/lifecycle/tools-execute.md

@@ -71,10 +71,10 @@ maestro wiki load <knowhow-id>
 
 ### Step 3: Confirm Execution
 
-Ask user:
-- Execute steps as-is?
-- Adjust parameters/scope?
-- View only, do not execute?
+AskUserQuestion (single-select, header: "执行方式"):
+- **Execute as-is** (Recommended) — run all steps with current parameters
+- **Adjust parameters** — modify scope or parameters before executing
+- **View only** — display steps without executing
 
 ### Step 4: Step-by-Step Execution
 

package/maestro-flow/commands/manage/codebase-rebuild.md

@@ -35,7 +35,7 @@ $ARGUMENTS -- optional flags.
 | Agent | Focus | Output file |
 |-------|-------|-------------|
 | Mapper 1 | **Tech stack** -- languages, frameworks, dependencies, build system | `tech-stack.md` |
-| Mapper 2 | **Architecture** -- produced by KG pipeline Step 14 (UA architecture-analyzer delegate); layers, module boundaries, data flow, entry points | `architecture.md` |
+| Mapper 2 | **Architecture** -- layers, module boundaries, data flow, entry points | `architecture.md` |
 | Mapper 3 | **Features** -- capabilities, API surface, user-facing functionality | `features.md` |
 | Mapper 4 | **Cross-cutting concerns** -- error handling, logging, auth, config, testing | `concerns.md` |
 
@@ -43,9 +43,7 @@ $ARGUMENTS -- optional flags.
 - `.workflow/` -- must be initialized (project.md, state.json exist)
 - `.workflow/codebase/` -- target directory (will be cleared and rebuilt)
 - `.workflow/codebase/doc-index.json` -- generated documentation index
-- `.workflow/codebase/knowledge-graph.json` -- Knowledge Graph with nodes, edges, layers, and tour (generated by KG pipeline Steps 10–17 if UA vendor is installed)
-
-**UA vendor requirement:** The KG pipeline (Steps 10–17) requires the UA vendor at `~/.maestro/vendor/ua/understand-anything-plugin/`. If not installed, these steps are skipped automatically. Run `scripts/ua-vendor-setup.sh` to install.
+- `.workflow/codebase/knowledge-graph.json` -- Knowledge Graph with nodes, edges, layers, and tour (generated by `maestro kg index`)
 </context>
 
 <execution>
@@ -79,8 +77,8 @@ Follow '~/.maestro/workflows/codebase-rebuild.md' completely.
 - [ ] All documentation files regenerated
 - [ ] state.json updated with rebuild timestamp
 - [ ] project.md Tech Stack section updated if changes detected
-- [ ] KG pipeline executed (if UA vendor installed)
-- [ ] knowledge-graph.json generated in .workflow/codebase/ (if UA vendor installed)
+- [ ] KG pipeline executed (`maestro kg index`)
+- [ ] knowledge-graph.json generated in .workflow/codebase/
 - [ ] KG nodes indexed as virtual wiki entries (automatic via WikiIndexer on next wiki access)
 - [ ] Next step routing: `/manage-status` or `/manage-codebase-refresh` for incremental updates later
 - [ ] KG impact check available: `maestro kg diff-wiki` for future change impact analysis

package/maestro-flow/commands/spec/load.md

@@ -1,7 +1,7 @@
 ---
 name: spec-load
 description: Load specs and lessons for current context
-argument-hint: "[--category <category>] [--keyword <word>]"
+argument-hint: "[--scope <scope>] [--category <category>] [--keyword <word>]"
 allowed-tools:
   - Read
   - Bash
@@ -9,8 +9,9 @@ allowed-tools:
   - Grep
 ---
 <purpose>
-Load relevant specs filtered by category (file-level) and/or keyword (entry-level).
+Load relevant specs filtered by scope, category (file-level) and/or keyword (entry-level).
 Category-based loading: loads the category's primary doc in full + matching entries from other files.
+By default, loads from both global (~/.maestro/specs/) and project (.workflow/specs/) layers.
 </purpose>
 
 <required_reading>
@@ -21,6 +22,11 @@ Category-based loading: loads the category's primary doc in full + matching entr
 $ARGUMENTS -- optional flags and keyword
 
 **Flags:**
+- `--scope <scope>` — Load scope (default: global + project merged):
+  - `project`: project baseline only (.workflow/specs/)
+  - `global`: global + project merged (~/.maestro/specs/ + .workflow/specs/)
+  - `team`: project + team shared (.workflow/collab/specs/)
+  - `personal`: project + team + personal (requires uid)
 - `--category <category>` — Load by category: primary category doc (full) + cross-file entries with matching category attr. Categories: coding, arch, test, review, debug, learning, ui.
 - `--keyword <word>` — Filter by keyword within entries
 
@@ -38,7 +44,8 @@ $ARGUMENTS -- optional flags and keyword
 
 **Examples:**
 ```
-/spec-load --category coding            # coding全文 + 跨文件coding条目
+/spec-load --category coding            # coding全文 + 跨文件coding条目 (global + project)
+/spec-load --scope global --category arch  # 明确包含全局 arch 规范
 /spec-load --category review            # review-standards + quality-rules + 跨文件review条目
 /spec-load --category coding --keyword auth
 /spec-load --keyword auth
@@ -57,7 +64,7 @@ Follow '~/.maestro/workflows/specs-load.md' completely.
 <error_codes>
 | Code | Severity | Description | Stage |
 |------|----------|-------------|-------|
-| E001 | fatal | `.workflow/specs/` not initialized -- run `/spec-setup` first | detect_context |
+| E001 | warning | `.workflow/specs/` not initialized -- run `/spec-setup` first (global specs still available) | detect_context |
 | W001 | warning | No matching specs found for keyword -- showing all specs in category instead | load_specs |
 </error_codes>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "maestro-flow-one",
-  "version": "0.2.27",
+  "version": "0.2.29",
   "description": "All Maestro workflow commands as a single Claude Code skill — intent routing, decision gates, minimal closed-loop chains",
   "bin": {
     "maestro-flow": "bin/maestro-flow.js"