maestro-flow 0.5.1 → 0.5.3

package/.codex/skills/maestro-composer/SKILL.md

@@ -1,217 +1,217 @@
----
-name: maestro-composer
-description: Compose reusable workflow templates from natural language
-argument-hint: "\"workflow description\" [--resume] [--edit <template-path>]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-Interactive workflow template composer. Parses natural language into a reusable DAG template
-via 5 phases with user confirmation at each boundary. Templates saved globally at
-`~/.maestro/templates/workflows/`. Progressive disclosure — specs loaded only when phase needs them.
-
-Sequential interactive flow (no spawn_agents_on_csv — this is design, not execution):
-```
-Parse NL → [confirm] → Resolve to nodes → [confirm] → Inject checkpoints → Confirm pipeline → Persist
-```
-
-Three entry modes:
-1. **New design**: Phase 1-5
-2. **Resume design**: Load draft from `.workflow/templates/design-drafts/`
-3. **Edit template**: Load existing, modify, re-save
-</purpose>
-
-<context>
-$ARGUMENTS — natural language workflow description, or flags.
-
-**Flags:**
-- `--resume` — Resume in-progress design session
-- `--edit <template-path>` — Edit an existing template
-
-**Shared constants:**
-
-| Constant | Value |
-|----------|-------|
-| Session prefix | `WFD` |
-| Template dir (global) | `~/.maestro/templates/workflows/` |
-| Template index (global) | `~/.maestro/templates/workflows/index.json` |
-| Design drafts dir (local) | `.workflow/templates/design-drafts/` |
-| Template ID format | `wft-<slug>-<YYYYMMDD>` |
-| Node ID format | `N-<seq>` (e.g. N-001), `CP-<seq>` for checkpoints |
-| Max nodes | 20 |
-
-**Entry routing:**
-
-| Detection | Condition | Handler |
-|-----------|-----------|---------|
-| Resume | `--resume` or existing WFD session | Phase 0: Resume |
-| Edit | `--edit <path>` | Phase 0: Load + Edit |
-| New | Default | Phase 1: Parse |
-
-**Node catalog**: Read `~/.maestro/templates/workflows/specs/node-catalog.md` at Phase 2 (deferred).
-**Template schema**: Read `~/.maestro/templates/workflows/specs/template-schema.md` at Phase 5 (deferred).
-
-### Pre-load specs
-1. **Architecture specs**: Run `maestro spec load --category arch` to load architecture constraints. Use as context for node resolution — ensures workflow design respects documented patterns.
-2. **Coding specs**: Run `maestro spec load --category coding` to load coding conventions. Informs executor argument defaults and context injection.
-3. Optional — proceed without if unavailable.
-</context>
-
-<execution>
-
-### Phase 0: Resume / Edit (conditional)
-
-**Resume** (`--resume`):
-1. Scan `.workflow/templates/design-drafts/WFD-*/` for in-progress designs
-2. Multiple → AskUserQuestion for selection
-3. Load draft → skip to last incomplete phase
-
-**Edit** (`--edit <path>`):
-1. Load template JSON
-2. Show pipeline visualization (Phase 4 format)
-3. AskUserQuestion: which nodes to modify/add/remove
-4. Re-enter at Phase 3
-
----
-
-### Phase 1: Parse — Semantic Intent Extraction
-
-**Step 1.1** — Parse `$ARGUMENTS`. If empty, AskUserQuestion:
-```
-"Describe the workflow you want to automate.
-Include: what steps to run, in what order, and what varies each time.
-Example: 'analyze the code, then plan, implement, and test the feature'"
-```
-
-**Step 1.2** — Extract sequential actions as candidate nodes:
-
-| Signal | Candidate Type |
-|--------|---------------|
-| "analyze", "review", "explore" | analysis (cli) |
-| "plan", "design", "spec" | planning (skill) |
-| "implement", "build", "code", "fix" | execution (skill) |
-| "test", "validate", "verify" | testing (skill) |
-| "brainstorm", "ideate" | brainstorm (skill) |
-| "review code" | review (skill) |
-| "then", "next", "after" | sequential edge |
-| "parallel", "simultaneously" | parallel edge |
-
-**Step 1.3** — Extract variables (inputs that vary per run).
-
-**Step 1.4** — Classify task type: `bugfix | feature | tdd | review | brainstorm | spec-driven | roadmap | refactor | integration-test | quick-task | custom`
-
-**Step 1.5** — Assess complexity: `simple` (1-3 nodes), `medium` (4-7), `complex` (8+)
-
-**Step 1.6** — Write `intent.json` to `.workflow/templates/design-drafts/WFD-<slug>-<date>/`.
-
-**Step 1.7 — Interactive confirmation**: Display description, task type, complexity, detected steps (numbered with type_hint), and variables. AskUserQuestion: `Continue to resolution` / `Edit steps` / `Add a step` / `Cancel`
-
----
-
-### Phase 2: Resolve — Map Steps to Executor Nodes
-
-**Read deferred**: `~/.maestro/templates/workflows/specs/node-catalog.md`
-
-If spec not found, use built-in fallback:
-
-| type_hint | executor type | executor |
-|-----------|--------------|----------|
-| `planning` | skill | `maestro-plan` |
-| `execution` | skill | `maestro-execute` |
-| `testing` | skill | `quality-test` |
-| `review` | skill | `quality-review` |
-| `brainstorm` | skill | `maestro-brainstorm` |
-| `analysis` | cli | `maestro delegate --role analyze --mode analysis` |
-| `refactor` | skill | `quality-refactor` |
-| `debug` | skill | `quality-debug` |
-| `spec` | skill | `maestro-blueprint` |
-| `checkpoint` | checkpoint | — |
-
-**Step 2.1** — Load `intent.json`, map each step to executor.
-
-**Step 2.2** — Build `args_template` with variable placeholders and context injection:
-- Planning after analysis → `--context {prev_output_path}`
-- Execution after planning → inherit phase
-- Testing after execution → inherit phase
-
-**Step 2.3** — Assign `parallel_group` for parallel steps.
-
-**Step 2.4** — Write `nodes.json`.
-
-**Step 2.5 — Interactive confirmation**: Display resolved nodes table (ID, type, executor, args) and parallel groups. AskUserQuestion: `Continue to checkpoint injection` / `Change executor` / `Change node type` / `Back to intent` / `Cancel`
-
----
-
-### Phase 3: Enrich — Inject Checkpoints + Build DAG
-
-**Step 3.1** — Load `nodes.json`. Build sequential edges. For parallel groups: fan-out/fan-in.
-
-**Step 3.2** — Auto-inject checkpoint nodes:
-
-| Rule | Condition |
-|------|-----------|
-| Artifact boundary | Source output_ports: plan, spec, analysis, review-findings |
-| Execution gate | Target executor contains `execute` |
-| Agent spawn | Target type is `agent` |
-| Long-running | Target is maestro-plan, maestro-roadmap |
-| User-defined | Step had `type_hint: checkpoint` |
-| Post-testing | Source executor contains `test` or `integration-test` |
-
-Set `auto_continue: false` for checkpoints before user-facing deliverables.
-
-**Step 3.3** — Finalize `context_schema`, validate DAG (no cycles, no orphans).
-
-**Step 3.4** — Write `dag.json`. → Proceed to Phase 4.
-
----
-
-### Phase 4: Confirm — Visualize + User Approval
-
-**Step 4.1** — Render ASCII pipeline: vertical node chain with `|` connectors showing each node (ID, type, executor, args) and checkpoint nodes (auto-continue vs pause-for-user). Footer: required variables, checkpoint counts, node counts.
-
-**Step 4.2** — AskUserQuestion: `Confirm & Save` / `Edit a node` / `Add a node` / `Remove a node` / `Rename template` / `Re-run checkpoint injection` / `Cancel`
-
-**Step 4.3** — Loop edits until Confirm or Cancel.
-
----
-
-### Phase 5: Persist — Assemble + Save Template
-
-**Read deferred**: `~/.maestro/templates/workflows/specs/template-schema.md`
-
-**Step 5.1** — Load `intent.json` + `dag.json`. Assemble template JSON.
-
-**Step 5.2** — Determine slug (kebab-case). If exists, append `-v2`.
-
-**Step 5.3** — Write `~/.maestro/templates/workflows/<slug>.json`.
-
-**Step 5.4** — Update `~/.maestro/templates/workflows/index.json`.
-
-**Step 5.5** — Output summary: path, template ID, node/checkpoint counts, required variables. Include usage commands: `$maestro-player <slug> --context goal="..."`, `$maestro-composer --edit <path>`, `$maestro-player --list`.
-
-**Step 5.6** — Clean up design draft directory.
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Empty description and no flags | AskUserQuestion for description |
-| E002 | error | 0 steps extracted | Ask to rephrase with action verbs |
-| E003 | error | Node count exceeds 20 | Suggest splitting into sub-workflows |
-| E004 | error | DAG cycle detected | Show cycle, ask to resolve |
-| E005 | error | Resume session not found | Show available drafts |
-| E006 | error | Edit template not found | Show available templates |
-| W001 | warning | Ambiguous executor mapping | Show candidates, let user choose |
-| W002 | warning | No checkpoint rules triggered | Warn, offer manual add |
-| W003 | warning | Deferred spec not found | Use built-in fallback |
-</error_codes>
-
-<success_criteria>
-- [ ] Intent parsed and confirmed by user (Phase 1 gate)
-- [ ] Nodes resolved and confirmed by user (Phase 2 gate)
-- [ ] DAG built with auto-injected checkpoints
-- [ ] Pipeline visualized and confirmed by user (Phase 4 gate)
-- [ ] Template JSON written to `~/.maestro/templates/workflows/<slug>.json`
-- [ ] Template index updated
-- [ ] Deferred specs loaded only when phase needs them
-</success_criteria>
+---
+name: maestro-composer
+description: Compose reusable workflow templates from natural language
+argument-hint: "\"workflow description\" [--resume] [--edit <template-path>]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
+---
+
+<purpose>
+Interactive workflow template composer. Parses natural language into a reusable DAG template
+via 5 phases with user confirmation at each boundary. Templates saved globally at
+`~/.maestro/templates/workflows/`. Progressive disclosure — specs loaded only when phase needs them.
+
+Sequential interactive flow (no spawn_agents_on_csv — this is design, not execution):
+```
+Parse NL → [confirm] → Resolve to nodes → [confirm] → Inject checkpoints → Confirm pipeline → Persist
+```
+
+Three entry modes:
+1. **New design**: Phase 1-5
+2. **Resume design**: Load draft from `.workflow/templates/design-drafts/`
+3. **Edit template**: Load existing, modify, re-save
+</purpose>
+
+<context>
+$ARGUMENTS — natural language workflow description, or flags.
+
+**Flags:**
+- `--resume` — Resume in-progress design session
+- `--edit <template-path>` — Edit an existing template
+
+**Shared constants:**
+
+| Constant | Value |
+|----------|-------|
+| Session prefix | `WFD` |
+| Template dir (global) | `~/.maestro/templates/workflows/` |
+| Template index (global) | `~/.maestro/templates/workflows/index.json` |
+| Design drafts dir (local) | `.workflow/templates/design-drafts/` |
+| Template ID format | `wft-<slug>-<YYYYMMDD>` |
+| Node ID format | `N-<seq>` (e.g. N-001), `CP-<seq>` for checkpoints |
+| Max nodes | 20 |
+
+**Entry routing:**
+
+| Detection | Condition | Handler |
+|-----------|-----------|---------|
+| Resume | `--resume` or existing WFD session | Phase 0: Resume |
+| Edit | `--edit <path>` | Phase 0: Load + Edit |
+| New | Default | Phase 1: Parse |
+
+**Node catalog**: Read `~/.maestro/templates/workflows/specs/node-catalog.md` at Phase 2 (deferred).
+**Template schema**: Read `~/.maestro/templates/workflows/specs/template-schema.md` at Phase 5 (deferred).
+
+### Pre-load specs
+1. **Architecture specs**: Run `maestro spec load --category arch` to load architecture constraints. Use as context for node resolution — ensures workflow design respects documented patterns.
+2. **Coding specs**: Run `maestro spec load --category coding` to load coding conventions. Informs executor argument defaults and context injection.
+3. Optional — proceed without if unavailable.
+</context>
+
+<execution>
+
+### Phase 0: Resume / Edit (conditional)
+
+**Resume** (`--resume`):
+1. Scan `.workflow/templates/design-drafts/WFD-*/` for in-progress designs
+2. Multiple → request_user_input for selection
+3. Load draft → skip to last incomplete phase
+
+**Edit** (`--edit <path>`):
+1. Load template JSON
+2. Show pipeline visualization (Phase 4 format)
+3. request_user_input: which nodes to modify/add/remove
+4. Re-enter at Phase 3
+
+---
+
+### Phase 1: Parse — Semantic Intent Extraction
+
+**Step 1.1** — Parse `$ARGUMENTS`. If empty, request_user_input:
+```
+"Describe the workflow you want to automate.
+Include: what steps to run, in what order, and what varies each time.
+Example: 'analyze the code, then plan, implement, and test the feature'"
+```
+
+**Step 1.2** — Extract sequential actions as candidate nodes:
+
+| Signal | Candidate Type |
+|--------|---------------|
+| "analyze", "review", "explore" | analysis (cli) |
+| "plan", "design", "spec" | planning (skill) |
+| "implement", "build", "code", "fix" | execution (skill) |
+| "test", "validate", "verify" | testing (skill) |
+| "brainstorm", "ideate" | brainstorm (skill) |
+| "review code" | review (skill) |
+| "then", "next", "after" | sequential edge |
+| "parallel", "simultaneously" | parallel edge |
+
+**Step 1.3** — Extract variables (inputs that vary per run).
+
+**Step 1.4** — Classify task type: `bugfix | feature | tdd | review | brainstorm | spec-driven | roadmap | refactor | integration-test | quick-task | custom`
+
+**Step 1.5** — Assess complexity: `simple` (1-3 nodes), `medium` (4-7), `complex` (8+)
+
+**Step 1.6** — Write `intent.json` to `.workflow/templates/design-drafts/WFD-<slug>-<date>/`.
+
+**Step 1.7 — Interactive confirmation**: Display description, task type, complexity, detected steps (numbered with type_hint), and variables. request_user_input: `Continue to resolution` / `Edit steps` / `Add a step` / `Cancel`
+
+---
+
+### Phase 2: Resolve — Map Steps to Executor Nodes
+
+**Read deferred**: `~/.maestro/templates/workflows/specs/node-catalog.md`
+
+If spec not found, use built-in fallback:
+
+| type_hint | executor type | executor |
+|-----------|--------------|----------|
+| `planning` | skill | `maestro-plan` |
+| `execution` | skill | `maestro-execute` |
+| `testing` | skill | `quality-test` |
+| `review` | skill | `quality-review` |
+| `brainstorm` | skill | `maestro-brainstorm` |
+| `analysis` | cli | `maestro delegate --role analyze --mode analysis` |
+| `refactor` | skill | `quality-refactor` |
+| `debug` | skill | `quality-debug` |
+| `spec` | skill | `maestro-blueprint` |
+| `checkpoint` | checkpoint | — |
+
+**Step 2.1** — Load `intent.json`, map each step to executor.
+
+**Step 2.2** — Build `args_template` with variable placeholders and context injection:
+- Planning after analysis → `--context {prev_output_path}`
+- Execution after planning → inherit phase
+- Testing after execution → inherit phase
+
+**Step 2.3** — Assign `parallel_group` for parallel steps.
+
+**Step 2.4** — Write `nodes.json`.
+
+**Step 2.5 — Interactive confirmation**: Display resolved nodes table (ID, type, executor, args) and parallel groups. request_user_input: `Continue to checkpoint injection` / `Change executor` / `Change node type` / `Back to intent` / `Cancel`
+
+---
+
+### Phase 3: Enrich — Inject Checkpoints + Build DAG
+
+**Step 3.1** — Load `nodes.json`. Build sequential edges. For parallel groups: fan-out/fan-in.
+
+**Step 3.2** — Auto-inject checkpoint nodes:
+
+| Rule | Condition |
+|------|-----------|
+| Artifact boundary | Source output_ports: plan, spec, analysis, review-findings |
+| Execution gate | Target executor contains `execute` |
+| Agent spawn | Target type is `agent` |
+| Long-running | Target is maestro-plan, maestro-roadmap |
+| User-defined | Step had `type_hint: checkpoint` |
+| Post-testing | Source executor contains `test` or `integration-test` |
+
+Set `auto_continue: false` for checkpoints before user-facing deliverables.
+
+**Step 3.3** — Finalize `context_schema`, validate DAG (no cycles, no orphans).
+
+**Step 3.4** — Write `dag.json`. → Proceed to Phase 4.
+
+---
+
+### Phase 4: Confirm — Visualize + User Approval
+
+**Step 4.1** — Render ASCII pipeline: vertical node chain with `|` connectors showing each node (ID, type, executor, args) and checkpoint nodes (auto-continue vs pause-for-user). Footer: required variables, checkpoint counts, node counts.
+
+**Step 4.2** — request_user_input: `Confirm & Save` / `Edit a node` / `Add a node` / `Remove a node` / `Rename template` / `Re-run checkpoint injection` / `Cancel`
+
+**Step 4.3** — Loop edits until Confirm or Cancel.
+
+---
+
+### Phase 5: Persist — Assemble + Save Template
+
+**Read deferred**: `~/.maestro/templates/workflows/specs/template-schema.md`
+
+**Step 5.1** — Load `intent.json` + `dag.json`. Assemble template JSON.
+
+**Step 5.2** — Determine slug (kebab-case). If exists, append `-v2`.
+
+**Step 5.3** — Write `~/.maestro/templates/workflows/<slug>.json`.
+
+**Step 5.4** — Update `~/.maestro/templates/workflows/index.json`.
+
+**Step 5.5** — Output summary: path, template ID, node/checkpoint counts, required variables. Include usage commands: `$maestro-player <slug> --context goal="..."`, `$maestro-composer --edit <path>`, `$maestro-player --list`.
+
+**Step 5.6** — Clean up design draft directory.
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Empty description and no flags | request_user_input for description |
+| E002 | error | 0 steps extracted | Ask to rephrase with action verbs |
+| E003 | error | Node count exceeds 20 | Suggest splitting into sub-workflows |
+| E004 | error | DAG cycle detected | Show cycle, ask to resolve |
+| E005 | error | Resume session not found | Show available drafts |
+| E006 | error | Edit template not found | Show available templates |
+| W001 | warning | Ambiguous executor mapping | Show candidates, let user choose |
+| W002 | warning | No checkpoint rules triggered | Warn, offer manual add |
+| W003 | warning | Deferred spec not found | Use built-in fallback |
+</error_codes>
+
+<success_criteria>
+- [ ] Intent parsed and confirmed by user (Phase 1 gate)
+- [ ] Nodes resolved and confirmed by user (Phase 2 gate)
+- [ ] DAG built with auto-injected checkpoints
+- [ ] Pipeline visualized and confirmed by user (Phase 4 gate)
+- [ ] Template JSON written to `~/.maestro/templates/workflows/<slug>.json`
+- [ ] Template index updated
+- [ ] Deferred specs loaded only when phase needs them
+</success_criteria>

package/.codex/skills/maestro-grill/SKILL.md

@@ -11,7 +11,7 @@ Positioned BEFORE brainstorm in the pipeline: grill stress-tests and sharpens; b
 
 Codex specifics:
 - **No agent spawning** — codebase exploration runs directly via Glob/Grep/Read in coordinator context.
-- **request_user_input** replaces AskUserQuestion for Socratic Q&A.
+- **request_user_input** replaces request_user_input for Socratic Q&A.
 - **CLI delegation** for auto mode: `exec_command("maestro delegate ... --role analyze --mode analysis")`.
 </purpose>
 

package/.codex/skills/maestro-help/SKILL.md

@@ -1,8 +1,8 @@
 ---
 name: maestro-help
-description: Maestro Flow command help system — search, browse, recommend commands, skills, agents, CLI tools, and workflows
+description: "Maestro Flow command help system — search, browse, recommend commands, skills, agents, CLI tools, and workflows"
 argument-hint: "[search <keyword>|workflow|skills|agents|cli|新手|下一步|<command-name>]"
-allowed-tools: Read, Grep, Glob, AskUserQuestion
+allowed-tools: Read, Grep, Glob, request_user_input
 ---
 
 <purpose>
@@ -79,10 +79,10 @@ Mode 3 (Smart Recommendations) 需要检测项目状态：
 ```
 找到 N 个匹配命令：
 
-/maestro-analyze — 多维度分析
+$maestro-analyze — 多维度分析
   分类: pipeline | 查看详情 →
 
-/maestro-plan — 任务规划
+$maestro-plan — 任务规划
   分类: pipeline | 查看详情 →
 ...
 ```
@@ -90,7 +90,7 @@ Mode 3 (Smart Recommendations) 需要检测项目状态：
 ### Mode 2: Command Documentation
 
 1. 在 `catalog.json` commands[] 中定位命令
-2. 通过 `source` 路径读取命令源文件（如 `../../commands/maestro-analyze.md`）
+2. 通过 `source` 路径读取命令源文件（如 `../../commands$maestro-analyze.md`）
 3. 提取 `<purpose>`、`argument-hint`、`<context>` 中的用法示例
 4. 如有对应 guide 文档，读取相关段落
 
@@ -108,16 +108,16 @@ Guide 映射：
 
 | 当前状态 | 推荐命令 | 原因 |
 |---------|---------|------|
-| 无 .workflow/ | `/maestro-init` | 项目未初始化 |
-| init 完成，无上游 context | `/maestro-brainstorm` 或 `/maestro-analyze "topic"` | 先探索再规划；brainstorm 发散，analyze 宏观探索影响面 |
-| analyze 完成，scope_verdict=large | `/maestro-roadmap --from analyze:ANL-xxx` | 大范围需求，需要 Milestone > Phase 分解 |
-| analyze 完成，scope_verdict=medium/small | `/maestro-plan --from analyze:ANL-xxx` | 跳过 roadmap 直达规划（Path C） |
-| roadmap 完成，phase=pending | `/maestro-analyze 1` | 微观分析：Phase 级深入探索 |
-| analyze (微观) 完成 | `/maestro-plan 1` | Phase 级规划 |
-| plan 完成 | `/maestro-execute` | 开始执行 |
-| execute 完成 | `/quality-review` | 进入质量管线 |
-| quality 全通过 | `/maestro-milestone-audit` | 里程碑审计 |
-| 所有 Phase 完成 | `/maestro-milestone-complete` | 关闭里程碑 |
+| 无 .workflow/ | `$maestro-init` | 项目未初始化 |
+| init 完成，无上游 context | `$maestro-brainstorm` 或 `$maestro-analyze "topic"` | 先探索再规划；brainstorm 发散，analyze 宏观探索影响面 |
+| analyze 完成，scope_verdict=large | `$maestro-roadmap --from analyze:ANL-xxx` | 大范围需求，需要 Milestone > Phase 分解 |
+| analyze 完成，scope_verdict=medium/small | `$maestro-plan --from analyze:ANL-xxx` | 跳过 roadmap 直达规划（Path C） |
+| roadmap 完成，phase=pending | `$maestro-analyze 1` | 微观分析：Phase 级深入探索 |
+| analyze (微观) 完成 | `$maestro-plan 1` | Phase 级规划 |
+| plan 完成 | `$maestro-execute` | 开始执行 |
+| execute 完成 | `$quality-review` | 进入质量管线 |
+| quality 全通过 | `$maestro-milestone-audit` | 里程碑审计 |
+| 所有 Phase 完成 | `$maestro-milestone-complete` | 关闭里程碑 |
 
 ### Mode 4: Workflow Guide
 
@@ -134,7 +134,7 @@ Guide 映射：
 
 **Path D — 小改动**:
 - `plan "fix auth bug"` → `execute` → `quality-review`
-- 快速: `/maestro-quick "功能描述"`
+- 快速: `$maestro-quick "功能描述"`
 - 全自动: `/maestro -y "功能描述"`
 
 **Path E/F — 纯文档/纯探索**:
@@ -142,12 +142,12 @@ Guide 映射：
 - `brainstorm "idea"` → (供人决策)
 
 **Bug 修复**:
-- 快速: `/maestro-quick "Bug 描述"`
+- 快速: `$maestro-quick "Bug 描述"`
 - Issue 闭环: discover → create → analyze --gaps → plan --gaps → execute → close
 
 **代码审查**:
-- `/quality-review` → `/quality-auto-test` → `/quality-test`
-- 失败循环: `/quality-debug` → `/maestro-plan --gaps` → `/maestro-execute`
+- `$quality-review` → `$quality-auto-test` → `$quality-test`
+- 失败循环: `$quality-debug` → `$maestro-plan --gaps` → `$maestro-execute`
 
 ### Mode 5: Beginner Onboarding
 
@@ -155,20 +155,20 @@ Guide 映射：
 
 | 命令 | 用途 | 何时使用 |
 |------|------|---------|
-| `/maestro` | 智能协调器 | 不确定用哪个命令时 |
-| `/maestro-init` | 初始化项目 | 首次使用 |
-| `/maestro-brainstorm` | 头脑风暴 | 新项目发散探索、多角色创意 |
-| `/maestro-blueprint` | 规格文档化 | 正式 7-phase 收敛规格链 |
-| `/maestro-analyze` | 双层分析 | 宏观: `"topic"` 探索影响面；微观: `1` Phase 级深入 |
-| `/maestro-roadmap` | 路线图编排 | scope_verdict=large 时，Milestone > Phase 分解 |
-| `/maestro-plan` | 规划 | 分析完成后，支持 `--from analyze:ANL-xxx` 直达 |
-| `/maestro-execute` | 执行 | 计划完成后 |
-| `/maestro-quick` | 快速任务 | 简单任务跳过管线 |
+| `$maestro` | 智能协调器 | 不确定用哪个命令时 |
+| `$maestro-init` | 初始化项目 | 首次使用 |
+| `$maestro-brainstorm` | 头脑风暴 | 新项目发散探索、多角色创意 |
+| `$maestro-blueprint` | 规格文档化 | 正式 7-phase 收敛规格链 |
+| `$maestro-analyze` | 双层分析 | 宏观: `"topic"` 探索影响面；微观: `1` Phase 级深入 |
+| `$maestro-roadmap` | 路线图编排 | scope_verdict=large 时，Milestone > Phase 分解 |
+| `$maestro-plan` | 规划 | 分析完成后，支持 `--from analyze:ANL-xxx` 直达 |
+| `$maestro-execute` | 执行 | 计划完成后 |
+| `$maestro-quick` | 快速任务 | 简单任务跳过管线 |
 
 快速上手路径：
 1. `maestro install --force`
-2. `/maestro-init`
-3. `/maestro "任务描述"` — 自动选择最佳工作流
+2. `$maestro-init`
+3. `$maestro "任务描述"` — 自动选择最佳工作流
 
 ### Mode 6: Skill & Agent Browsing
 
@@ -208,7 +208,7 @@ Guide 映射：
 | E001 | error | catalog.json 读取失败 | 回退到 Glob 扫描 .claude/commands/*.md |
 | W001 | warning | 搜索无结果 | 模糊匹配最近命令，建议查看全部 |
 | W002 | warning | Source 文件不存在 | 仅展示 catalog 描述 |
-| W003 | warning | 项目未初始化 | 推荐先运行 /maestro-init |
+| W003 | warning | 项目未初始化 | 推荐先运行 $maestro-init |
 </error_codes>
 
 <success_criteria>

package/.codex/skills/maestro-impeccable/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-impeccable
-description: Use when designing, auditing, polishing, or improving frontend UI — websites, dashboards, landing pages, components
+description: "Use when designing, auditing, polishing, or improving frontend UI — websites, dashboards, landing pages, components"
 argument-hint: "<command|chain|intent> [target] [flags]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
 ---

package/.codex/skills/maestro-init/SKILL.md

@@ -123,7 +123,7 @@ Write collected configuration to `.workflow/config.json`.
 Run `Bash("maestro spec init")` to create empty seed files in `.workflow/specs/`.
 
 If project state is **code** (existing source files detected in Step 2):
-- Auto-trigger `Skill({ skill: "spec-setup" })` to scan codebase and populate specs with detected conventions
+- Auto-trigger `$spec-setup` to scan codebase and populate specs with detected conventions
 - This runs unconditionally for `code` state — existing source means conventions can be extracted
 
 If project state is **empty** (greenfield, no source files found in Step 2):