maestro-flow 0.3.48 → 0.4.1

package/.codex/skills/maestro-help/catalog.json

@@ -27,7 +27,7 @@
     {"name": "maestro-ralph", "command": "/maestro-ralph", "category": "ralph", "description": "Ralph 引擎 — 自适应生命周期决策节点管理", "source": "../../commands/maestro-ralph.md"},
     {"name": "maestro-ralph-execute", "command": "/maestro-ralph-execute", "category": "ralph", "description": "Ralph 执行 — 运行自适应决策链", "source": "../../commands/maestro-ralph-execute.md"},
     {"name": "maestro-learn", "command": "/maestro-learn", "category": "core", "description": "学习 — 从执行中提取知识和模式", "source": "../../commands/maestro-learn.md"},
-    {"name": "maestro-ui-design", "command": "/maestro-ui-design", "category": "ui", "description": "UI 设计 — 设计系统原型和 Token 管理", "source": "../../commands/maestro-ui-design.md"},
+    {"name": "maestro-impeccable", "command": "/maestro-impeccable", "category": "ui", "description": "UI 生产管线 — 设计系统原型、自动化生产和质量门控", "source": "../../commands/maestro-impeccable.md"},
     {"name": "maestro-ui-codify", "command": "/maestro-ui-codify", "category": "ui", "description": "UI 固化 — 将设计产出转化为知识资产", "source": "../../commands/maestro-ui-codify.md"},
     {"name": "maestro-update", "command": "/maestro-update", "category": "core", "description": "版本更新 — 检查并安装最新版本", "source": "../../commands/maestro-update.md"},
     {"name": "maestro-tools-register", "command": "/maestro-tools-register", "category": "tools", "description": "MCP 工具注册 — 注册外部工具到 Maestro", "source": "../../commands/maestro-tools-register.md"},

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

@@ -1,112 +1,245 @@
 ---
 name: maestro-impeccable
-description: Production-grade UI design with knowhow accumulation -- 23 commands for build, evaluate, refine, enhance, fix
-argument-hint: "[craft|shape · audit|critique · animate|bolder|colorize|delight|layout|overdrive|quieter|typeset · adapt|clarify|distill · harden|onboard|optimize|polish · teach|document|extract|live] [target] [--skip-harvest] [-y]"
+description: Production-grade UI design — 24 commands + chain orchestration with quality gates + design search
+argument-hint: "<command|chain|intent> [target] [flags]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
 ---
+
 <purpose>
-Designs and iterates production-grade frontend interfaces. Real working code, committed design choices, exceptional craft.
-After each command, automatically harvests design knowledge to `.workflow/knowhow/` (category: ui) for cross-session accumulation.
+Sequential UI design skill. Parse input → prerequisites → read workflow file → execute → track via status.json.
 
-Replaces the standalone impeccable skill. 23 commands covering the full design lifecycle.
+- **Direct**: single command via workflow file
+- **Chain**: orchestrate command sequence with quality gates
+- **Search**: query design knowledge base via CLI
 </purpose>
 
 <context>
-$ARGUMENTS -- sub-command + target + optional flags.
-
-**Sub-commands** (23):
-
-| Category | Commands |
-|----------|----------|
-| Build | craft, shape, teach, document, extract |
-| Evaluate | critique, audit |
-| Refine | polish, bolder, quieter, distill, harden, onboard |
-| Enhance | animate, colorize, typeset, layout, delight, overdrive |
-| Fix | clarify, adapt, optimize |
-| Iterate | live |
-
-**Flags:**
-- `--skip-harvest` -- Execute command without knowhow capture
-- `-y` -- Auto-confirm where the skill allows
+$ARGUMENTS first word determines mode:
+
+| First Word | Mode |
+|------------|------|
+| Known command (see routing table) | Direct |
+| Chain name: build, redesign, improve, enhance, launch, harden, foundation, live | Chain |
+| continue / next / -c | Resume |
+| search | Search: `maestro impeccable search "$REST"` |
+| Free text (concrete task) | Direct craft — has specific target + specs/reference |
+| Free text (project intent) | Intent → classify → chain |
+| (empty) | Menu: show commands by category |
+
+**Common flags**: `-y` (auto-confirm), `--skip-harvest`, `--skip-design`, `--styles <N>`
+**Chain flags**: `--threshold <N>` (default 26/40), `--max-loops <N>` (default 3)
 </context>
 
-<execution>
-
-## Setup
+## Command Routing
+
+All workflows at `~/.maestro/workflows/impeccable/{command}.md`:
+
+| Command | Category | Description |
+|---------|----------|-------------|
+| craft | Build | Shape then build end-to-end — full page/component implementation |
+| shape | Build | Plan UX/UI before code — information architecture, wireframe, visual direction |
+| teach | Build | Set up PRODUCT.md — users, brand, tone, anti-references, principles |
+| document | Build | Generate DESIGN.md from existing code — extract tokens, typography, colors |
+| extract | Build | Pull tokens/components into reusable design system |
+| explore | Build | Multi-style comparison — generate variants, render prototypes, visual compare, select/mix |
+| critique | Evaluate | UX heuristic review with Nielsen scoring (/40) + P0/P1 findings |
+| audit | Evaluate | Technical quality checks — a11y, performance, responsive, code quality (/20) |
+| polish | Refine | Final quality pass — micro-adjustments, pixel perfection |
+| bolder | Refine | Amplify bland/safe designs — stronger personality, more contrast |
+| quieter | Refine | Tone down aggressive/overwhelming designs — reduce visual noise |
+| distill | Refine | Strip to essence — remove clutter, reduce cognitive load |
+| harden | Refine | Production-ready — error states, i18n, edge cases, overflow, empty states |
+| onboard | Refine | First-run flows, empty states, activation paths, progressive disclosure |
+| animate | Enhance | Add purposeful motion — transitions, micro-interactions, scroll effects |
+| colorize | Enhance | Add strategic color — OKLCH palette, contrast, color strategy |
+| typeset | Enhance | Improve typography — scale, hierarchy, font pairing, line length |
+| layout | Enhance | Fix spacing, rhythm, visual hierarchy, alignment, grid |
+| delight | Enhance | Add personality — memorable details, joy, surprise moments |
+| overdrive | Enhance | Push past conventional limits — ambitious visual effects |
+| clarify | Fix | Improve UX copy — labels, error messages, microcopy, CTAs |
+| adapt | Fix | Adapt for devices/screens — responsive, touch targets, breakpoints |
+| optimize | Fix | Fix UI performance — loading, rendering, bundle, paint/layout jank |
+| live | Iterate | Browser-based variant iteration — real-time design in DevTools |
+
+Reference files (loaded by workflow as needed, not standalone commands):
+brand.md, product.md, design.md, codex.md, heuristics-scoring.md, cognitive-load.md,
+color-and-contrast.md, interaction-design.md, motion-design.md, personas.md,
+responsive-design.md, spatial-design.md, typography.md, ux-writing.md
+
+## Chains
+
+| Chain | Steps | Scenario |
+|-------|-------|----------|
+| build | teach? → explore? → shape → craft → critique → [refine] → audit → polish | 从零新建 |
+| redesign | document → explore → shape → craft → critique → [refine] → audit → polish | 基于现有代码重设计 |
+| improve | critique → [refine] → polish → audit | 迭代改进 |
+| enhance | {cmd...} → critique → [refine] → polish | 定向增强（支持多命令） |
+| launch | harden → adapt → optimize → audit → polish | 全方位上线准备 |
+| harden | harden → audit → polish | 边界加固 |
+| foundation | teach? → explore → document → extract | 纯设计系统建设 |
+| live | live | 实时迭代 |
+
+- `?` = conditional: teach if PRODUCT.md missing; explore if DESIGN.md missing and --skip-design not set
+- `[refine]` = quality gate loop: gate fails → auto-select fix commands from findings → re-gate
+- `{cmd...}` = enhance supports multiple commands, comma-separated: `enhance colorize,typeset target`
+
+## Free Text Routing
+
+Three-layer priority matching. Stop on first match.
+
+### Layer 1: Intent matches single command → Direct
+
+Match user description against Command Routing descriptions. Route to the closest single command.
+
+| Intent signal | Command |
+|---------------|---------|
+| review, UX check, heuristic, 评审, 评分 | critique |
+| a11y, audit, accessibility, performance audit, 技术检查 | audit |
+| animation, motion, transitions, 动效, 加动画 | animate |
+| color, palette, contrast, OKLCH, 配色, 颜色 | colorize |
+| typography, font, type scale, 字体, 排版 | typeset |
+| layout, spacing, grid, alignment, 布局, 间距 | layout |
+| tone down, too loud, 太花, 视觉噪音 | quieter |
+| too bland, bolder, more personality, 太平淡 | bolder |
+| simplify, strip, too complex, cognitive load, 太复杂 | distill |
+| polish, micro-adjust, pixel perfect, 打磨 | polish |
+| copy, labels, error messages, UX writing, 文案 | clarify |
+| responsive, mobile, breakpoints, 适配 | adapt |
+| performance, loading, bundle, jank, 性能 | optimize |
+| edge cases, error states, i18n, overflow, 边界 | harden |
+| onboarding, first-run, empty state, 引导 | onboard |
+| delight, personality, joy, memorable, 趣味 | delight |
+| extraordinary, push limits, 炫酷, 极限 | overdrive |
+| plan UX, wireframe, information architecture, 规划 | shape |
+| variants, compare styles, multi-style, 多风格 | explore |
+| PRODUCT.md, brand definition, 品牌定义 | teach |
+| DESIGN.md, design documentation, 设计文档 | document |
+| pull tokens, extract components, 提取组件 | extract |
+| browser iteration, 实时迭代 | live |
+
+### Layer 2: Concrete build task → Direct craft
+
+Layer 1 missed, but intent is "build/create specific thing":
+- Has specific file path or target
+- Has detailed visual specs (layout, style, palette)
+- Has reference material
+
+→ Route to **craft** (Direct)
+
+### Layer 3: Project intent → Chain
+
+Layer 1+2 missed, broad project direction:
+
+| Pattern | Chain |
+|---------|-------|
+| create, build, new, from scratch | build |
+| redesign, rethink, restyle | redesign |
+| improve, iterate, better | improve |
+| enhance, visual upgrade | enhance |
+| launch, deploy, ship, production-ready | launch |
+| harden, production, edge cases | harden |
+| design system, tokens, design spec | foundation |
+| live, browser | live |
+
+Ambiguous + no `-y` → `request_user_input`.
+
+<invariants>
+1. Prerequisites before any design work — never skip context loading or register detection
+2. Read workflow file before execution — never execute a command without loading its .md
+3. Interactive gates respected — teach, shape, craft retain user confirmation gates
+4. status.json before chain steps — session created before any chain step runs
+</invariants>
+
+## Prerequisites
+
+Before reading any command workflow:
+
+1. **Context**: `maestro spec load --category ui` → if empty → `maestro impeccable load-context`
+2. **PRODUCT.md**: missing/placeholder (<200 chars / `[TODO]`) → execute teach first, then resume original task
+3. **Register**: identify brand/product → Read `~/.maestro/workflows/impeccable/{brand|product}.md`
+
+## Direct Execution
+
+1. Prerequisites ✓
+2. **显示执行信息**：
+   ```
+   ── Command: {command} ────────────────────
+   Category: {category} | Target: {target}
+   ─────────────────────────────────────────
+   ```
+3. Read `~/.maestro/workflows/impeccable/{command}.md`
+4. **TodoWrite 跟踪**：按 workflow 文件中的主要阶段创建 todo 项
+   - 格式：`[{command}] {phase description}`
+   - 每个阶段完成后立即标记 completed
+5. Follow workflow file instructions
+6. Post: suggest logical next command (teach→shape, shape→craft, craft→critique, etc.)
 
-Before any design work:
+## Chain Execution
 
-1. Load context (PRODUCT.md / DESIGN.md) via spec system:
-   ```bash
-   maestro spec load --category ui
+1. Prerequisites ✓
+2. **显示执行链**：解析 chain 定义，输出完整步骤预览：
    ```
-   This surfaces all design context (product + visual) from `.workflow/specs/ui-conventions.md`.
-
-   If specs are not initialized, fall back to the legacy loader:
-   ```bash
-   maestro impeccable load-context
+   ── Chain: build ──────────────────────────
+    1. teach        (conditional: PRODUCT.md missing)
+    2. explore      (conditional: DESIGN.md missing)
+    3. shape
+    4. craft
+    5. critique     ◆ quality gate (threshold: 26/40)
+    6. [refine]     ↺ auto-fix loop (max: 3)
+    7. audit        ◆ quality gate (threshold: 14/20)
+    8. polish
+   ─────────────────────────────────────────
+   Target: {target}
+   ```
+   - `◆` 标记 quality gate 步骤，显示阈值
+   - `↺` 标记 refine loop，显示最大循环次数
+   - conditional 步骤注明触发条件
+   - 跳过的 conditional 步骤标记 `(skipped)`
+3. Create session: `.workflow/.maestro/ui-craft-{YYYYMMDD-HHmmss}/status.json`
+   ```json
+   { "chain_type": "...", "target": "...", "steps": [...], "current_step": 0,
+     "gate_history": [], "loop_count": 0, "status": "running" }
    ```
-   The loader searches `.workflow/impeccable/` first, then the project root, then `.agents/context/` and `docs/`.
-   PRODUCT.md and DESIGN.md are stored at `.workflow/impeccable/`.
-
-2. Identify register (brand vs product) and load matching reference from `~/.maestro/workflows/impeccable/brand.md` or `product.md`.
-3. If sub-command invoked, load its reference file from `~/.maestro/workflows/impeccable/{command}.md`.
-
-If PRODUCT.md missing → run `teach` first, then resume original task.
-
-## Command Execution
-
-Route by first argument:
-1. **Matches command** → load `~/.maestro/workflows/impeccable/{command}.md`, follow instructions
-2. **No argument** → show command menu grouped by category
-3. **No match** → general design invocation with full argument as context
-
-## Harvest (Post-Execution)
-
-After command completes (except `live`), unless `--skip-harvest`:
-
-| Command | Knowhow Type | Prefix |
-|---------|-------------|--------|
-| craft | decision + asset | DCS- + AST- |
-| shape | decision | DCS- |
-| teach | reference | REF- |
-| document, extract | asset | AST- |
-| critique, audit, polish, harden, onboard, clarify, adapt, optimize | tip | TIP- |
-| colorize, typeset, layout, animate, bolder, quieter, distill, delight, overdrive | decision | DCS- |
-
-Write knowhow with `category: ui`. For DCS-/AST- types, also create spec index:
-```bash
-maestro spec add ui "<title>" "<summary>" --keywords impeccable,<cmd>,... --ref knowhow/<file>
-```
-
-</execution>
-
-<shared_design_laws>
-
-- **Color**: OKLCH only. Never #000/#fff. Pick color strategy first (Restrained → Committed → Full palette → Drenched).
-- **Theme**: Write physical scene sentence before choosing dark/light.
-- **Typography**: Body 65-75ch. Hierarchy via scale + weight (>=1.25 ratio).
-- **Layout**: Vary spacing for rhythm. Cards only when truly best. No nested cards.
-- **Motion**: No CSS layout animations. Ease-out exponential curves.
-- **Bans**: Side-stripe borders, gradient text, glassmorphism default, hero-metric template, identical card grids, modal as first thought.
-- **Copy**: Every word earns its place. No em dashes.
-- **AI slop test**: Two-altitude category-reflex check.
-
-</shared_design_laws>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | Invalid sub-command |
-| E002 | error | No intent or target specified |
-| W001 | warning | Harvest failed (command still succeeded) |
-| W002 | warning | PRODUCT.md missing, auto-triggering teach |
-</error_codes>
-
-<success_criteria>
-- [ ] Sub-command recognized and reference file loaded
-- [ ] Context loaded from .workflow/impeccable/ (PRODUCT.md, register identified)
-- [ ] Design changes applied to target files
-- [ ] Knowhow entry created in .workflow/knowhow/ with category: ui (unless --skip-harvest or live)
-- [ ] Spec index entry created for DCS-/AST- types
-</success_criteria>
+4. **TodoWrite 初始化**：为 chain 所有步骤创建 todo 项
+   - 每步一项，格式：`[chain] step N: {command} — {description}`
+   - conditional 步骤若跳过，立即标记 completed
+   - quality gate 步骤标注阈值：`[chain] step 5: critique ◆ gate ≥26/40`
+5. For each step:
+   - Read `~/.maestro/workflows/impeccable/{command}.md` → execute
+   - **步骤开始**：TodoWrite 标记当前步骤 in_progress
+   - **步骤完成**：TodoWrite 标记 completed + update status.json (`current_step`, step `status`)
+   - **步骤失败**：TodoWrite 标记 completed(with note) + 记录原因
+6. **Quality gate** (critique/audit steps):
+   - Parse score: critique `**Total** | | **N/40**`, audit `**Total** | | **N/20**`
+   - Count `[P0]` / `[P1]` tags
+   - Pass: score ≥ threshold AND P0 == 0 → advance
+   - Fail: collect suggested commands from findings → execute → re-gate
+   - Max loops exceeded → force advance with warning
+   - TodoWrite：gate 结果记入当前步骤备注（score, P0/P1 count, pass/fail）
+7. Final report: scores + trend + commands executed
+
+## Resume
+
+Scan `.workflow/.maestro/ui-craft-*/status.json` for `status == "running"` → most recent → resume from `current_step`.
+
+## Quality Gate — Finding → Command Fallback
+
+When findings lack explicit suggested command:
+
+| Finding Category | Command |
+|-----------------|---------|
+| Layout, spacing, hierarchy, alignment | layout |
+| Color, contrast, palette | colorize |
+| Typography, font, readability | typeset |
+| Animation, motion, transitions | animate |
+| Copy, labels, UX writing | clarify |
+| Responsive, mobile, breakpoints | adapt |
+| Performance, loading, speed | optimize |
+| Complexity, overload, clutter | distill |
+| Bland, safe, generic | bolder |
+| Aggressive, overwhelming | quieter |
+| Onboarding, empty state | onboard |
+| Edge cases, i18n, error handling | harden |
+| Personality, memorability | delight |
+
+Never auto-select: teach, shape, craft, live, document, extract, overdrive, critique, audit.

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

@@ -40,6 +40,9 @@ $ARGUMENTS — milestone number and optional flags.
 <execution>
 Follow '~/.maestro/workflows/merge.md' completely.
 
+**Knowledge inquiry on completion:**
+After successful merge, ask user once: "Record milestone learnings?" If yes, persist via `maestro spec add learning "<title>" "<insight>" --keywords <kw1>,<kw2>`.
+
 **Next steps:**
 - View dashboard → `$manage-status`
 - Audit milestone → `$maestro-milestone-audit`

package/.codex/skills/maestro-milestone-audit/SKILL.md

@@ -2,11 +2,13 @@
 name: maestro-milestone-audit
 description: Audit current milestone for cross-phase integration gaps
 argument-hint: "[milestone, e.g., 'M1']"
-allowed-tools: Read, Write, Bash, Glob, Grep, Agent
+allowed-tools: spawn_agents_on_csv, Read, Write, Bash, Glob, Grep
 ---
 
 <purpose>
-Sequential audit based on artifact registry in state.json. Checks phase coverage (ANL->PLN->EXC chains), ad-hoc completeness, execution completeness, and cross-artifact integration. Produces PASS/FAIL verdict report.
+Sequential audit based on artifact registry in state.json. Checks phase coverage (ANL->PLN->EXC chains), ad-hoc completeness, execution completeness, and cross-artifact integration via `spawn_agents_on_csv`. Produces PASS/FAIL verdict report.
+
+**Core workflow**: Load Artifacts -> Coverage Check -> Completeness Check -> CSV Wave (Integration Check) -> Verdict
 </purpose>
 
 <context>
@@ -16,14 +18,52 @@ $maestro-milestone-audit ""
 $maestro-milestone-audit "M1"
 ```
 
-**Output**: Audit report with artifact chain verification, integration analysis, and PASS/FAIL verdict
+**Output**: `.workflow/milestones/{milestone}/audit-report.md` with artifact chain verification, integration analysis, and PASS/FAIL verdict
 
+**Session**: `.workflow/.csv-wave/{YYYYMMDD}-audit-{milestone}/`
 </context>
 
+<csv_schema>
+
+### tasks.csv (Master State)
+
+```csv
+id,title,description,scope,check_targets,deps,wave,status,findings,gaps_found,severity,error
+"integ-1","Interface & dependency chains","Verify shared interfaces are consistent across phases: re-exports match, dependency chains unbroken, no circular imports between phase outputs","cross-phase imports, shared types, re-exports","grep for shared type names across phase output dirs; verify export/import consistency","","1","","","","",""
+"integ-2","Data contracts & API consistency","Verify request/response schemas match across phases: API signatures consistent, error codes aligned, no contract drift","request/response schemas, API signatures, error codes","diff API type definitions across phases; check error code enum consistency","","1","","","","",""
+```
+
+**Columns**:
+
+| Column | Phase | Description |
+|--------|-------|-------------|
+| `id` | Input | Worker identifier: `integ-{N}` |
+| `title` | Input | Integration dimension name |
+| `description` | Input | Detailed check instructions |
+| `scope` | Input | What to examine |
+| `check_targets` | Input | Specific verification commands/grep patterns |
+| `deps` | Input | Dependencies (empty — all wave 1) |
+| `wave` | Computed | Wave number (always 1 — single parallel wave) |
+| `status` | Output | `pending` -> `pass` / `fail` / `warning` |
+| `findings` | Output | Detailed findings per dimension (max 500 chars) |
+| `gaps_found` | Output | Semicolon-separated list of integration gaps |
+| `severity` | Output | `critical` / `warning` / `info` per gap |
+| `error` | Output | Error message if check failed |
+
+### Session Structure
+
+```
+.workflow/.csv-wave/{YYYYMMDD}-audit-{milestone}/
++-- tasks.csv
++-- wave-1.csv (temporary)
++-- wave-1-results.csv
+```
+</csv_schema>
+
 <invariants>
 1. **Artifact registry is source of truth** — don't scan directories, read state.json
 2. **Non-blocking warnings** — missing analyze is warning, missing execute is error
-3. **Integration check is required** — always spawn checker agent
+3. **Integration check is required** — always spawn checker via CSV wave
 4. **Clear verdict** — PASS or FAIL with specific reasons
 </invariants>
 
@@ -45,9 +85,26 @@ For each phase: check for completed analyze (optional), plan (required), execute
 
 Verify all adhoc-scoped artifacts completed. For each execute artifact, verify all tasks in plan dir completed.
 
-### Step 5: Integration Check
+### Step 5: Integration Check via CSV Wave
+
+1. Create session folder: `.workflow/.csv-wave/{dateStr}-audit-{milestone}/`
+2. Build `tasks.csv` from csv_schema — populate `scope` and `check_targets` columns using phase artifacts discovered in Step 2
+3. Write `wave-1.csv` from pending rows, then execute:
+
+```javascript
+spawn_agents_on_csv({
+  csv_path: `${sessionFolder}/wave-1.csv`,
+  id_column: "id",
+  instruction: `You are an integration checker for milestone ${milestone}. For each row, examine the scope and check_targets. Search the codebase for inconsistencies, contract drift, and broken dependencies across phase outputs. Report findings with file:line references. Set status to pass/fail/warning. List specific gaps in gaps_found (semicolon-separated).`,
+  max_concurrency: 2, max_runtime_seconds: 600,
+  output_csv_path: `${sessionFolder}/wave-1-results.csv`,
+  output_schema: { id, status: [pass|fail|warning], findings, gaps_found, severity, error }
+})
+```
 
-Spawn Agent for cross-phase validation: shared interfaces, dependency chains, data contracts, API consistency. Write report to `.workflow/milestones/{milestone}/audit-report.md`.
+4. Merge results into master `tasks.csv`
+5. Parse `gaps_found` from all workers — aggregate into `.workflow/milestones/{milestone}/audit-report.md`
+6. Any worker with `status == fail` and `severity == critical` → milestone verdict = FAIL
 
 ### Step 6: Verdict
 
@@ -81,7 +138,7 @@ Display structured audit report.
 - [ ] Artifact registry loaded and filtered by milestone
 - [ ] Phase coverage matrix generated
 - [ ] Ad-hoc and execution completeness verified
-- [ ] Integration check performed via agent
+- [ ] Integration check performed via spawn_agents_on_csv (2 parallel workers)
 - [ ] Audit report written to milestones/ directory
 - [ ] Clear PASS/FAIL verdict with specific reasons
 </success_criteria>

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

@@ -2,7 +2,7 @@
 name: maestro-quick
 description: Quick task execution, skip optional agents
 argument-hint: "\"task description\" [--discuss] [--full]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
 
 <purpose>

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

@@ -158,7 +158,7 @@ Build prev_context from wave 1. Inject strategy + --phases constraint (light mod
    +-- readiness-report.md
    ```
 7. Update state.json milestones + current_milestone
-8. Next-step routing: need analysis -> maestro-analyze; ready to plan -> maestro-plan; UI first -> maestro-ui-design; full mode setup -> maestro-init
+8. Next-step routing: need analysis -> maestro-analyze; ready to plan -> maestro-plan; UI first -> maestro-impeccable build; full mode setup -> maestro-init
 
 </actions>
 

package/.codex/skills/maestro-tools-execute/SKILL.md

@@ -2,7 +2,7 @@
 name: maestro-tools-execute
 description: Load and execute tool specs by role or name
 argument-hint: "[tool-name | --category <category>]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
 
 <purpose>

package/.codex/skills/maestro-tools-register/SKILL.md

@@ -2,7 +2,7 @@
 name: maestro-tools-register
 description: Register tool specs - extract, generate, or optimize reusable process definitions
 argument-hint: "[description or intent]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion, Agent
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
 ---
 
 <purpose>