maestro-flow 0.4.1 → 0.4.3

package/.claude/commands/maestro-analyze.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-analyze
-description: Multi-angle analysis with CLI-assisted exploration
+description: Use when a topic needs structured multi-dimensional investigation before planning or decision-making
 argument-hint: "[phase|topic] [-y] [-c] [-q] [--gaps [ISS-ID]]"
 allowed-tools:
   - Read

package/.claude/commands/maestro-brainstorm.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-brainstorm
-description: Brainstorm with auto pipeline or single-role analysis
+description: Use when exploring ideas, evaluating approaches, or needing multi-perspective analysis before implementation
 argument-hint: "[topic|role-name] [--yes] [--count N] [--session ID] [--update] [--skip-questions] [--include-questions] [--style-skill PKG]"
 allowed-tools:
   - Read

package/.claude/commands/maestro-collab.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-collab
-description: Multi-CLI collaborative analysis -- fan-out to multiple CLI tools, cross-verify, synthesize
+description: Use when a question needs cross-verification from multiple CLI tools or diverse analytical perspectives
 argument-hint: "\"<requirement>\" [--tools gemini,qwen,claude] [--mode analysis|write] [--rule <template>] [-y]"
 allowed-tools:
   - Read

package/.claude/commands/maestro-execute.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-execute
-description: Execute plan with parallel waves and atomic commits
+description: Use when a confirmed plan is ready for implementation
 argument-hint: "[phase] [--auto-commit] [--method agent|cli|auto] [--executor <tool>] [--dir <path>] [-y]"
 allowed-tools:
   - Read
@@ -98,6 +98,15 @@ Next steps:
   /manage-status               -- View project dashboard
 ```
 
+**Completion status:**
+```
+--- COMPLETION STATUS ---
+STATUS: DONE|DONE_WITH_CONCERNS|NEEDS_RETRY
+CONCERNS: {failed_count} tasks failed (if any)
+NEXT: /maestro-verify
+--- END STATUS ---
+```
+
 If failed tasks exist, suggest /quality-debug for investigation.
 </execution>
 

package/.claude/commands/maestro-guard.md

@@ -0,0 +1,101 @@
+---
+name: maestro-guard
+description: Manage editing boundary restrictions
+argument-hint: "<on|off|status|allow <path>|deny <path>>"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+---
+<purpose>
+Configure directory-level write boundaries enforced by the workflow-guard PreToolUse hook.
+When enabled, Write and Edit tool calls targeting files outside allowed paths are blocked.
+
+Subcommands:
+- **on** — Enable path guard (defaults to `src/` if no paths configured)
+- **off** — Disable path guard (preserves path list)
+- **status** — Show current guard configuration
+- **allow `<path>`** — Add a directory to the allowed paths list
+- **deny `<path>`** — Switch to deny mode and add path to deny list
+</purpose>
+
+<context>
+$ARGUMENTS — Parse subcommand and optional path argument.
+
+**Config location:** `.workflow/config.json` → `guard` section
+
+```json
+{
+  "guard": {
+    "enabled": false,
+    "mode": "allow",
+    "paths": []
+  }
+}
+```
+
+**Enforcement:** The `workflow-guard` hook (PreToolUse on Write/Edit) reads this config
+and blocks operations targeting files outside boundaries. Requires hooks level >= `full`.
+</context>
+
+<execution>
+
+**Step 1: Parse subcommand**
+
+Extract from $ARGUMENTS:
+- `on` / `off` / `status` / `allow <path>` / `deny <path>`
+- If no subcommand, default to `status`
+
+**Step 2: Read config**
+
+Read `.workflow/config.json`. If file missing, initialize with empty guard section.
+
+**Step 3: Execute subcommand**
+
+**`status`:**
+- Display: enabled/disabled, mode (allow/deny), paths list
+- Check if workflow-guard hook is active (read `.claude/settings.json` for hook presence)
+- If guard enabled but hook not active, warn: "⚠ PathGuard enabled but workflow-guard hook not installed. Run `maestro hooks level full` to activate."
+
+**`on`:**
+- Set `guard.enabled = true`
+- If `guard.paths` is empty, set default: `["src/", "tests/", ".workflow/"]`
+- Check hook level, warn if < full
+- Write config
+
+**`off`:**
+- Set `guard.enabled = false`
+- Preserve existing paths and mode
+- Write config
+
+**`allow <path>`:**
+- Normalize path to forward slashes, ensure trailing slash for directories
+- If `guard.mode` is `deny`, switch to `allow` and clear paths with warning
+- Add path to `guard.paths` (deduplicate)
+- Set `guard.enabled = true` if not already
+- Write config
+
+**`deny <path>`:**
+- Normalize path to forward slashes
+- Set `guard.mode = "deny"`
+- Add path to `guard.paths` (deduplicate)
+- Set `guard.enabled = true` if not already
+- Write config
+
+**Step 4: Confirm**
+
+Display updated guard configuration.
+
+</execution>
+
+<error_codes>
+- E001: `.workflow/config.json` not found and cannot be created (not a maestro project)
+- W001: PathGuard enabled but workflow-guard hook not installed
+</error_codes>
+
+<success_criteria>
+- [ ] Config read/written correctly
+- [ ] Hook level warning displayed when applicable
+- [ ] Updated configuration shown after changes
+</success_criteria>

package/.claude/commands/maestro-impeccable.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-impeccable
-description: Production-grade UI design — 24 commands + chain orchestration with quality gates + design search
+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
@@ -76,81 +76,84 @@ responsive-design.md, spatial-design.md, typography.md, ux-writing.md
 
 | 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 | 实时迭代 |
+| build | teach? → explore? → shape → craft → critique → [refine] → audit → polish | New from scratch |
+| redesign | document → explore → shape → craft → critique → [refine] → audit → polish | Redesign existing code |
+| improve | critique → [refine] → polish → audit | Iterative improvement |
+| enhance | {cmd...} → critique → [refine] → polish | Targeted enhancement (multi-command) |
+| launch | harden → adapt → optimize → audit → polish | Full production readiness |
+| harden | harden → audit → polish | Edge case hardening |
+| foundation | teach? → explore → document → extract | Design system setup |
+| live | live | Real-time iteration |
 
 - `?` = 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 支持多命令，逗号分隔：`enhance colorize,typeset landing-page`
+- `{cmd...}` = enhance supports multiple commands, comma-separated: `enhance colorize,typeset landing-page`
 
 Chain flags: --threshold <N> (default 26/40), --max-loops <N> (default 3), --skip-design, --styles <N>, -y
 
 ## Free Text Routing
 
-Free text 按优先级三层匹配。命中即停，不继续向下。
+Three-layer priority matching. Stop on first match — do not continue to lower layers.
 
-### Layer 1: 意图匹配单个命令 → Direct
+### Layer 1: Single command intent → Direct
 
-将用户描述与 Command Routing 表的 Description 列语义匹配。匹配最接近的**一个**命令。
+Semantically match user description against the Command Routing table's Description column. Match the closest **single** command.
+
+**Skip condition**: If the prompt also contains a Layer 2 chain keyword AND does not focus on a single design dimension, skip this layer.
+Example: `enhance colors and typography` — "enhance" is a chain keyword + multiple design dimensions → skip to Layer 2.
 
 | Intent signal | Command |
 |---------------|---------|
-| 评审, review, 检查UX, 评分, heuristic | critique |
-| 审计, a11y, 可访问性, 技术检查, performance audit, 代码质量 | audit |
-| 加动画, 动效, transitions, micro-interactions, 过渡 | animate |
-| 配色, 颜色, palette, 色彩, OKLCH, contrast | colorize |
-| 字体, 排版, typography, font, 字号, 行高 | typeset |
-| 布局, 间距, spacing, grid, 对齐, alignment, 视觉层次 | layout |
-| 太花, 太吵, tone down, 视觉噪音, 简洁点 | quieter |
-| 太平淡, 加强, 更大胆, more personality, 更有个性 | bolder |
-| 太复杂, 简化, strip, 去掉多余, cognitive load | distill |
-| 打磨, 微调, pixel perfect, final pass, 最终润色 | polish |
-| 文案, copy, 标签, 错误提示, UX writing, microcopy | clarify |
-| 响应式, mobile, 适配, breakpoints, touch targets | adapt |
-| 性能, loading, bundle, 卡顿, jank, 速度 | optimize |
-| 边界, error states, i18n, 溢出, 空状态加固 | harden |
-| 引导, 新手, 首次使用, onboarding, empty state, 激活 | onboard |
-| 趣味, 惊喜, personality, memorable, joy | delight |
-| 炫酷, 极限, extraordinary, 超常规, 技术极限 | overdrive |
-| 规划, plan UX, wireframe, 信息架构, 视觉方向 | shape |
-| 多风格, 变体, variants, compare styles, 风格对比 | explore |
-| 品牌定义, PRODUCT.md, 产品上下文 | teach |
-| 提取设计, DESIGN.md, 设计文档化 | document |
-| 提取组件, pull tokens, 设计系统提取 | extract |
-| 实时, browser iteration, 浏览器迭代 | live |
-
-### Layer 2: 具体构建任务 → Direct craft
-
-Layer 1 未命中，但意图是"构建/创建某个具体东西"：
-- 包含具体文件路径或目标（`d:\path`, `src/pages/`, `index.html`）
-- 包含详细视觉规格（布局、风格、配色方案）
-- 包含参考素材（`参考...`, `based on...`, `like...`）
-
-→ 路由到 **craft**（Direct）
-
-### Layer 3: 项目意图 → Chain
-
-Layer 1+2 未命中，意图是泛泛的项目方向：
+| review, check UX, score, heuristic, evaluate usability | critique |
+| audit, a11y, accessibility, technical check, performance audit, code quality | audit |
+| add animation, motion, transitions, micro-interactions | animate |
+| color, palette, OKLCH, contrast, color scheme | colorize |
+| font, typography, type scale, line height, font pairing | typeset |
+| layout, spacing, grid, alignment, visual hierarchy | layout |
+| too loud, tone down, visual noise, make it simpler, too busy | quieter |
+| too bland, bolder, more personality, stronger, more contrast | bolder |
+| too complex, simplify, strip, remove clutter, cognitive load | distill |
+| polish, fine-tune, pixel perfect, final pass, refine details | polish |
+| copy, labels, error messages, UX writing, microcopy, CTAs | clarify |
+| responsive, mobile, adapt, breakpoints, touch targets | adapt |
+| performance, loading, bundle, jank, speed, rendering | optimize |
+| edge cases, error states, i18n, overflow, empty state hardening | harden |
+| onboarding, first-run, empty state, activation, progressive disclosure | onboard |
+| fun, surprise, personality, memorable, joy, delight | delight |
+| extraordinary, push limits, ambitious effects, cutting-edge | overdrive |
+| plan UX, wireframe, information architecture, visual direction | shape |
+| multi-style, variants, compare styles, style comparison | explore |
+| brand definition, PRODUCT.md, product context | teach |
+| extract design, DESIGN.md, document design system | document |
+| pull tokens, extract components, design system extraction | extract |
+| real-time, browser iteration, live editing | live |
+
+### Layer 2: Project intent → Chain
+
+Layer 1 did not match. Check for chain-level keywords — even if the prompt also contains a specific target/path, chain matching takes priority.
 
 | Pattern | Chain |
 |---------|-------|
-| 新建, create, build, new, 从零开始 | build |
-| 重做, redesign, 重新设计, rethink, 换风格, 改版 | redesign |
-| 改进, improve, iterate, better, 迭代 | improve |
-| 增强, enhance, 视觉升级, visual upgrade | enhance |
-| 上线, launch, deploy, ship, 发布准备, production-ready | launch |
-| 加固, harden, 生产化, 边界情况 | harden |
-| 设计系统, design system, tokens, 设计规范, 设计基建 | foundation |
-| 实时, live, browser | live |
+| new, create, build, from scratch, start fresh | build |
+| redo, redesign, rethink, restyle, overhaul, revamp | redesign |
+| improve, iterate, better, refine overall | improve |
+| enhance, visual upgrade, level up | enhance |
+| launch, deploy, ship, production-ready, go live | launch |
+| harden, production-harden, edge cases | harden |
+| design system, tokens, design foundation, design infrastructure | foundation |
+| real-time, live, browser | live |
 
 Ambiguous + no `-y` → AskUserQuestion.
 
+### Layer 3: Concrete build task → Direct craft
+
+Layer 1+2 both did not match, but intent is to build/create a specific thing:
+- Contains a specific file path or target (`d:\path`, `src/pages/`, `index.html`)
+- Contains detailed visual specs (layout, style, color scheme)
+- Contains reference material (`based on...`, `like...`, `similar to...`)
+
+→ Route to **craft** (Direct)
+
 ## Prerequisites
 
 Before reading any command workflow:
@@ -162,23 +165,23 @@ Before reading any command workflow:
 ## Direct Execution
 
 1. Prerequisites ✓
-2. **显示执行信息**：
+2. **Display execution info**:
    ```
    ── Command: {command} ────────────────────
    Category: {category} | Target: {target}
    ─────────────────────────────────────────
    ```
 3. Read `~/.maestro/workflows/impeccable/{command}.md`
-4. **TodoWrite 跟踪**：按 workflow 文件中的主要阶段创建 todo 项
-   - 格式：`[{command}] {phase description}`
-   - 每个阶段完成后立即标记 completed
+4. **TodoWrite tracking**: create todo items for each major phase in the workflow file
+   - Format: `[{command}] {phase description}`
+   - Mark each phase completed immediately upon finishing
 5. Follow workflow file instructions
 6. Post: suggest logical next command (teach→shape, shape→craft, craft→critique, etc.)
 
 ## Chain Execution
 
 1. Prerequisites ✓
-2. **显示执行链**：解析 chain 定义，输出完整步骤预览：
+2. **Display chain preview**: parse chain definition, output full step preview:
    ```
    ── Chain: build ──────────────────────────
     1. teach        (conditional: PRODUCT.md missing)
@@ -192,31 +195,31 @@ Before reading any command workflow:
    ─────────────────────────────────────────
    Target: {target}
    ```
-   - `◆` 标记 quality gate 步骤，显示阈值
-   - `↺` 标记 refine loop，显示最大循环次数
-   - conditional 步骤注明触发条件
-   - 跳过的 conditional 步骤标记 `(skipped)`
+   - `◆` marks quality gate steps with threshold
+   - `↺` marks refine loop with max iteration count
+   - Conditional steps show trigger condition
+   - Skipped conditional steps marked `(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" }
    ```
-4. **TodoWrite 初始化**：为 chain 所有步骤创建 todo 项
-   - 每步一项，格式：`[chain] step N: {command} — {description}`
-   - conditional 步骤若跳过，立即标记 completed
-   - quality gate 步骤标注阈值：`[chain] step 5: critique ◆ gate ≥26/40`
+4. **TodoWrite init**: create todo items for all chain steps
+   - One item per step, format: `[chain] step N: {command} — {description}`
+   - If conditional step is skipped, immediately mark completed
+   - Quality gate steps include threshold: `[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) + 记录原因
+   - **Step start**: TodoWrite marks current step in_progress
+   - **Step done**: TodoWrite marks completed + update status.json (`current_step`, step `status`)
+   - **Step failed**: TodoWrite marks completed (with note) + record reason
 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）
+   - TodoWrite: record gate result in current step notes (score, P0/P1 count, pass/fail)
 7. Final report: scores + trend + commands executed
 
 ## Resume

package/.claude/commands/maestro-plan.md

@@ -1,7 +1,7 @@
 ---
 name: maestro-plan
-description: Plan phase execution with exploration and verification
-argument-hint: "[phase] [--collab] [--spec SPEC-xxx] [-y] [--gaps] [--dir <path>] [--revise [instructions]] [--check <plan-dir>]"
+description: Use when creating, revising, or verifying an execution plan for a phase or task
+argument-hint: "[phase] [--collab] [--spec SPEC-xxx] [-y] [--gaps] [--tdd] [--dir <path>] [--revise [instructions]] [--check <plan-dir>]"
 allowed-tools:
   - Read
   - Write
@@ -122,6 +122,19 @@ Next steps:
   /maestro-plan {phase}         -- Re-plan with modifications
 ```
 
+**Completion status:**
+```
+--- COMPLETION STATUS ---
+STATUS: DONE|NEEDS_CONTEXT
+CONCERNS: {description if applicable}
+NEXT: /maestro-execute
+--- END STATUS ---
+```
+
+Status mapping:
+- **DONE** — Plan created/revised and confirmed → NEXT: /maestro-execute
+- **NEEDS_CONTEXT** — Ambiguous requirements, insufficient context to produce plan
+
 ### Mode: Revise / Check
 
 Follow workflow plan.md § "Revise Mode" and § "Check Mode" respectively. These modes bypass the standard P1-P5 create pipeline.

package/.claude/commands/maestro-ralph-execute.md

@@ -180,8 +180,15 @@ Write enriched args back to status.json (resume-safe).
    - `PHASE: N` → session.phase
    - `scratch_dir: path` → context.scratch_dir
    - `SPEC-xxx` → context.spec_session_id
-3. Write status.json
-4. Display: `[{index}/{total}] ✓ {skill} completed`
+3. Scan output for `--- COMPLETION STATUS ---` block. If found, parse and map:
+   - `STATUS: DONE` → `step.status = "completed"`
+   - `STATUS: DONE_WITH_CONCERNS` → `step.status = "completed"`, `step.concerns = CONCERNS value`
+   - `STATUS: NEEDS_RETRY` → trigger retry: set `step.status = "pending"`, `step.retried = true` → S_HANDLE_FAIL
+   - `STATUS: BLOCKED` → `session.status = "paused"`, display blocker reason from CONCERNS
+   - `STATUS: NEEDS_CONTEXT` → `session.status = "paused"`, display context gap from CONCERNS
+   - If no `--- COMPLETION STATUS ---` block found → fall back to existing heuristic (backward compatible)
+4. Write status.json
+5. Display: `[{index}/{total}] ✓ {skill} completed`
 
 ### A_RETRY
 

package/.claude/commands/maestro-ralph.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-ralph
-description: Adaptive lifecycle engine — infer state, build command chain
+description: Use when the optimal command sequence is unclear and needs automated state-based determination
 argument-hint: "[-y] \"intent\" | status | continue"
 allowed-tools:
   - Read
@@ -238,6 +238,13 @@ Build rules: start from position, skip completed, insert decision nodes with `{
    ```
 6. On callback: parse verdict; if parse fails → fallback STATUS="fix"
 7. Confidence adjustment: <60 + proceed → fix; >95 + fix + retry>0 → suggest proceed
+8. **Decision log**: Append to `{session_dir}/decisions.ndjson`:
+   ```json
+   { "id": "DEC-{timestamp}", "timestamp": "{ISO}", "source": "ralph",
+     "node_id": "{step.decision}", "type": "quality-gate",
+     "verdict": "{adjusted_verdict}", "confidence_score": {N},
+     "close_call": {N>=50 && N<=70}, "summary": "{REASON}" }
+   ```
 
 ### A_STRUCTURAL_EVALUATE
 

package/.claude/commands/maestro-verify.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-verify
-description: Verify goals with must-have checks and test coverage validation
+description: Use after execution to verify goals are actually achieved with evidence-based structural checks
 argument-hint: "[phase] [--skip-tests] [--skip-antipattern] [--dir <path>]"
 allowed-tools:
   - Read
@@ -70,6 +70,20 @@ On confirm → `Skill("spec-add", "<category> <content>")`.
 
 **Gap-fix closure loop:**
 Gaps found → maestro-plan --gaps → maestro-execute → maestro-verify (re-run)
+
+**Completion status:**
+```
+--- COMPLETION STATUS ---
+STATUS: DONE|DONE_WITH_CONCERNS|NEEDS_RETRY
+CONCERNS: {description if applicable}
+NEXT: /quality-review
+--- END STATUS ---
+```
+
+Status mapping:
+- **DONE** — All checks pass, no gaps → NEXT: /quality-review
+- **DONE_WITH_CONCERNS** — Gaps found (must-have failures or anti-pattern blockers) → NEXT: /maestro-execute (after /maestro-plan --gaps)
+- **NEEDS_RETRY** — Verification could not complete (missing artifacts, corrupt data)
 </execution>
 
 <error_codes>

package/.claude/commands/quality-auto-test.md

@@ -1,6 +1,6 @@
 ---
 name: quality-auto-test
-description: Auto-generate and run tests from specs or coverage gaps
+description: Use when test coverage needs automated expansion or existing tests need iterative convergence
 argument-hint: "<phase> [-y] [-c N] [--max-iter <N>] [--layer <L0-L3>] [--strategy <name>] [--dry-run] [--re-run]"
 allowed-tools:
   - spawn_agents_on_csv

package/.claude/commands/quality-debug.md

@@ -1,6 +1,6 @@
 ---
 name: quality-debug
-description: Debug with parallel hypotheses and root cause analysis
+description: Use when bugs, test failures, or unexpected behavior need systematic root cause investigation
 argument-hint: "[issue description] [--from-uat <phase>] [--parallel]"
 allowed-tools:
   - Read

package/.claude/commands/quality-refactor.md

@@ -1,6 +1,6 @@
 ---
 name: quality-refactor
-description: Reduce tech debt with reflection-driven iteration
+description: Use when accumulated tech debt needs systematic identification and safe reduction
 argument-hint: "[<scope>]"
 allowed-tools:
   - Read

package/.claude/commands/quality-retrospective.md

@@ -1,6 +1,6 @@
 ---
 name: quality-retrospective
-description: Phase retrospective with insight routing to specs and knowhow
+description: Use after completing a phase to extract lessons, patterns, and improvement opportunities
 argument-hint: "[phase|N..M] [--lens technical|process|quality|decision] [--all] [--no-route] [--compare N] [-y]"
 allowed-tools:
   - Read

package/.claude/commands/quality-review.md

@@ -1,6 +1,6 @@
 ---
 name: quality-review
-description: Tiered code review with severity classification
+description: Use after execution to evaluate code quality across correctness, security, performance, and architecture
 argument-hint: "<phase> [--level quick|standard|deep] [--dimensions security,architecture,...] [--skip-specs]"
 allowed-tools:
   - Read
@@ -87,6 +87,20 @@ Report format and next-step routing by verdict defined in workflow review.md Rep
 - PASS → `/quality-test {phase}`
 - WARN → `/quality-test {phase}` (proceed with caveats)
 - BLOCK → `/maestro-plan {phase} --gaps` (fix critical findings first)
+
+**Completion status:**
+```
+--- COMPLETION STATUS ---
+STATUS: DONE|DONE_WITH_CONCERNS|NEEDS_RETRY
+CONCERNS: {description if applicable}
+NEXT: /quality-refactor
+--- END STATUS ---
+```
+
+Status mapping:
+- **DONE** — PASS verdict, no critical findings → NEXT: /quality-refactor
+- **DONE_WITH_CONCERNS** — WARN verdict, issues found but non-blocking → NEXT: /maestro-verify
+- **NEEDS_RETRY** — BLOCK verdict, critical findings require fix first
 </execution>
 
 <error_codes>

package/.claude/commands/quality-test.md

@@ -1,6 +1,6 @@
 ---
 name: quality-test
-description: Conversational UAT with auto-diagnosis and gap closure
+description: Use when implementation needs user acceptance testing with interactive verification and gap closure
 argument-hint: "[phase] [--smoke] [--auto-fix]"
 allowed-tools:
   - Read