maestro-flow 0.4.10 → 0.4.12

package/.agents/skills/maestro-execute/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: maestro-execute
+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_file
+  - write_file
+  - edit_file
+  - shell
+  - find_files
+  - search
+  - delegate_subagent
+  - ask_user
+---
+<!-- Open-standard mirror generated by scripts/build-agents-standard.mjs — do not edit; re-run after editing .claude/ source. -->
+
+<purpose>
+Execute all tasks in a plan using wave-based parallel execution with dependency-aware ordering. Each plan is executed independently (plans串行, plan内wave并行). Task summaries are written to the plan's scratch directory under `.summaries/`. Registers EXC artifact in state.json.
+
+Invoked after /maestro-plan produces a confirmed plan. When called without args on a milestone, finds all pending plans and executes them sequentially.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/execute.md
+</required_reading>
+
+<deferred_reading>
+- [task.json](~/.maestro/templates/task.json) — read when reading task definitions
+- [state.json](~/.maestro/templates/state.json) — read when registering artifact
+</deferred_reading>
+
+<context>
+$ARGUMENTS — phase number, or no args for milestone-wide execution, with optional flags.
+
+Scope routing, flags, resolution logic, output directory format, artifact registration schema, and incremental knowhow extraction are defined in workflow `execute.md`.
+
+### Pre-load context (before task execution)
+
+1. **Codebase docs**: If `.workflow/codebase/doc-index.json` exists, read `ARCHITECTURE.md` for module boundaries. Pass as shared context to executor agents.
+2. **Wiki knowledge**: Run `maestro wiki search "<phase keywords>" --json 2>/dev/null`. If results found, extract top 5 entries as prior knowledge context for agents.
+3. **Coding specs + tools**: Run `maestro spec load --category coding` to load coding conventions AND discoverable knowhow tools (tool: true entries). Pass as specs context to all executor agents.
+4. **UI specs (conditional)**: If any task involves frontend/UI work (task scope/description contains keywords like component, page, style, layout, CSS, HTML, frontend; or focus_paths in `src/components/`, `src/pages/`, `src/styles/`, `src/ui/`), also run `maestro spec load --category ui` and include in agent context.
+5. All are optional — proceed without if unavailable (log warning).
+
+### Role Knowledge
+`maestro wiki list --category coding` → select relevant → `maestro wiki load`
+</context>
+
+<execution>
+### Pre-flight: team conflict check
+
+Before any task execution, run:
+```
+shell("maestro collab preflight --phase <phase-number>")
+```
+If exit code is 1, present warnings and ask whether to proceed.
+
+Follow '~/.maestro/workflows/execute.md' completely.
+
+### Post-task Knowledge Inquiry
+
+After each task completion, check triggers:
+
+| Condition | Ask | Route |
+|-----------|-----|-------|
+| Summary mentions approach change / plan deviation | "Record as arch constraint?" | spec-add arch |
+| retry_count >= 2 | "Document fix pattern?" | spec-add debug |
+| Summary contains design rationale ("chose X because") | "Record as knowhow?" | spec-add learning |
+
+On confirm → `invoke_skill("spec-add", "<category> <content>")`.
+
+### Issue Status Sync
+
+On each task completion, if `task.issue_id` exists, sync status back to the issue in `.workflow/issues/issues.jsonl`:
+
+```
+For each completed/failed TASK with issue_id:
+  Read issue from issues.jsonl by issue_id
+  Collect all task_refs[] statuses for that issue:
+    all task_refs completed → issue.status = "resolved"
+    any task_ref failed    → issue.status = "in_progress"
+  Append history entry: { action: "executed", at: <ISO>, by: "maestro-execute", summary: "TASK-{NNN} {status}" }
+  Write updated issue back to issues.jsonl
+```
+
+**Report format on completion:**
+
+```
+=== EXECUTION COMPLETE ===
+Plans executed: {plans_count}
+Completed: {completed_count}/{total_count} tasks
+Failed:    {failed_count} tasks
+
+Summaries: {plan_dir}/.summaries/
+Tasks:     {plan_dir}/.task/
+
+Next steps:
+  /maestro-verify              -- Verify execution results
+  /maestro-verify --dir {dir}  -- Verify specific plan
+  /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>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | No pending plans found | Verify plans exist, run maestro-plan first |
+| E002 | error | Plan directory not found | Check --dir path |
+| E003 | error | plan.json not found in directory | Verify plan.json exists, run maestro-plan first |
+| E004 | error | No pending tasks, all tasks already completed | Check task statuses, reset if needed |
+| W001 | warning | Executor completed with partial failures | Check task dependencies, retry failed wave |
+</error_codes>
+
+<success_criteria>
+- [ ] All pending plans identified and executed sequentially
+- [ ] Within each plan: waves executed in parallel, waves串行
+- [ ] `.summaries/TASK-{NNN}-summary.md` written for each completed task
+- [ ] `.task/TASK-{NNN}.json` statuses updated (completed|blocked)
+- [ ] EXC artifact registered in state.json for each plan executed
+- [ ] Incremental knowhow extracted to specs/learnings.md
+- [ ] state.json updated with execution progress
+</success_criteria>

package/.agents/skills/maestro-fork/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: maestro-fork
+description: Create or sync milestone worktree for parallel dev
+argument-hint: "-m <milestone-number> [--base <branch>] [--sync]"
+allowed-tools:
+  - read_file
+  - write_file
+  - edit_file
+  - shell
+  - find_files
+  - search
+  - delegate_subagent
+  - ask_user
+---
+<!-- Open-standard mirror generated by scripts/build-agents-standard.mjs — do not edit; re-run after editing .claude/ source. -->
+
+<purpose>
+Create a git worktree for an entire milestone, enabling inter-milestone parallel development. The worktree scope is milestone-level — all scratch artifacts for that milestone are owned by the worktree.
+
+Since `.workflow/` is gitignored, this command explicitly copies project context and existing milestone scratch artifacts into the worktree. Per-phase parallelism within a milestone is NOT supported.
+
+Also supports `--sync` mode to pull latest main branch changes and shared artifacts into an active worktree (prevents source and artifact drift for long-lived worktrees).
+
+Produces `.workflow/worktrees.json` registry in the main worktree and `.workflow/worktree-scope.json` marker in the worktree.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/fork.md
+</required_reading>
+
+<deferred_reading>
+- [worktrees.json](~/.maestro/templates/worktrees.json) — read when updating registry
+- [worktree-scope.json](~/.maestro/templates/worktree-scope.json) — read when writing scope marker
+</deferred_reading>
+
+<context>
+$ARGUMENTS -- milestone number and optional flags.
+
+Modes (`Fork` / `Sync`), flags (`-m`, `--base`, `--sync`), milestone resolution, worktree layout, and artifact scoping are defined in workflow `fork.md`.
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/fork.md' completely.
+
+Fork and sync algorithm steps are defined in workflow `fork.md`.
+
+**Next-step routing on completion:**
+
+Fork mode:
+- Enter worktree → `cd {wt.path} && /maestro-analyze`
+- Automated → `maestro delegate "run full lifecycle for milestone" --cd {wt.path} --mode write`
+- Status → invoke_skill({ skill: "manage-status" })
+
+Sync mode:
+- Sync complete → resume work in worktree
+- Conflicts found → resolve manually, then retry
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | Project not initialized | Run maestro-init first |
+| E002 | error | No roadmap found | Run maestro-roadmap first |
+| E003 | error | Running inside a worktree | Run from main worktree |
+| E004 | error | No milestone number provided | Provide `-m <N>` |
+| E005 | error | No milestones defined in state.json | Run maestro-roadmap first |
+| E006 | error | Milestone number out of range | Check available milestones |
+| E007 | error | No active worktree for milestone (--sync) | Check worktrees.json |
+| E008 | error | Milestone already has active worktree | Merge or cleanup first |
+</error_codes>
+
+<success_criteria>
+Fork mode:
+- [ ] Milestone resolved from state.json.milestones[]
+- [ ] Git worktree created with branch (`milestone/{slug}`)
+- [ ] Shared `.workflow/` files copied (project.md, roadmap.md, config.json, specs/)
+- [ ] Milestone scratch artifacts copied (filtered from artifact registry)
+- [ ] `worktree-scope.json` written with milestone scope
+- [ ] Scoped `state.json` written (only this milestone's artifacts)
+- [ ] `worktrees.json` registry updated in main worktree
+- [ ] Milestone marked as `"forked"` in main `state.json.milestones[]`
+- [ ] Summary displayed with next-step commands
+
+Sync mode:
+- [ ] Git merge main into worktree branch
+- [ ] Shared artifacts re-copied (project.md, roadmap.md, config.json, specs/)
+- [ ] Conflicts reported if any
+</success_criteria>

package/.agents/skills/maestro-guard/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: maestro-guard
+description: Manage editing boundary restrictions
+argument-hint: "<on|off|status|allow <path>|deny <path>>"
+allowed-tools:
+  - read_file
+  - write_file
+  - shell
+  - find_files
+---
+<!-- Open-standard mirror generated by scripts/build-agents-standard.mjs — do not edit; re-run after editing .claude/ source. -->
+
+<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/.agents/skills/maestro-help/SKILL.md

@@ -0,0 +1,300 @@
+---
+name: maestro-help
+description: Maestro Flow 命令帮助系统。搜索命令、浏览技能、工作流推荐、新手引导。Triggers on "maestro-help", "帮助", "命令", "怎么用", "skill", "workflow", "maestro 怎么用".
+allowed-tools: read_file, search, find_files, ask_user
+---
+<!-- Open-standard mirror generated by scripts/build-agents-standard.mjs — do not edit; re-run after editing .claude/ source. -->
+
+
+# Maestro Help
+
+Maestro Flow 命令帮助系统，提供命令搜索、技能浏览、工作流推荐、新手引导功能。
+
+## Trigger Conditions
+
+- 关键词: "maestro-help", "帮助", "命令", "怎么用", "maestro 怎么用", "工作流", "skill", "workflow", "有哪些命令", "用什么命令"
+- 场景: 询问命令用法、搜索命令、请求下一步建议、选择工作流、浏览 Skill/Agent 目录
+- 斜杠: `/maestro-help`, `/maestro-help search <keyword>`, `/maestro-help skills`, `/maestro-help guide`
+
+## Architecture Overview
+
+```
+┌──────────────────────────────────────────────────────────────────┐
+│  Maestro Help (SKILL.md) — Orchestrator                          │
+│  → Parse intent → Route to mode → Execute phase → Present        │
+└────────────────────────┬─────────────────────────────────────────┘
+                         │
+    ┌────────────────────┼────────────────────────┐
+    ↓                    ↓                        ↓
+┌──────────┐      ┌──────────────┐         ┌──────────┐
+│ Phase 1  │      │  Phase 2     │         │ Phase 3  │
+│ Parse    │─────→│  Search &    │────────→│ Workflow │
+│ Intent   │      │  Present     │         │ Guide    │
+└──────────┘      └──────────────┘         └──────────┘
+                       ↑       ↗                │
+                       └──────┘                  ↓
+                    (refine search)          present guide
+```
+
+## Key Design Principles
+
+1. **Catalog 驱动**: 所有查询基于 `index/catalog.json`，不做硬编码
+2. **Guide 深度链接**: 命令详情链接到 `guide/` 目录中的参考文档
+3. **上下文感知**: 根据项目状态（.workflow/ 是否存在、当前 Phase）调整推荐
+4. **中英双语**: 命令名英文，说明和示例中文
+
+## Data Source
+
+Single source of truth: **[index/catalog.json](index/catalog.json)**
+
+| Field | Purpose |
+|-------|---------|
+| `commands[]` | 56 个 slash 命令，含分类和描述 |
+| `skills[]` | 10 个 Skill，含分类和描述 |
+| `agents[]` | 22 个 Agent，含分类和描述 |
+| `cli_commands[]` | 21 个终端命令 |
+| `guide_files[]` | 17 个 Guide 文档索引 |
+| `essential_commands[]` | 10 个核心命令（新手用） |
+| `workflows` | 主干管线、快速渠道、Issue 闭环、初始化路径 |
+
+## Operation Modes
+
+### Mode 1: Command Search
+
+**Triggers**: "搜索命令", "find command", "search", 命令名关键词
+
+**Process**:
+1. Read `Ref: phases/01-parse-intent.md` — 解析搜索意图
+2. Query `catalog.json` commands[] + cli_commands[]
+3. Filter by name, description, category
+4. Present top 5 相关结果，含命令名、描述、分类
+
+### Mode 2: Command Documentation
+
+**Triggers**: "怎么用", "how to use", "详情", 具体命令名
+
+**Process**:
+1. Locate command in `catalog.json`
+2. Read source file via `source` path（从 catalog 相对路径）
+3. 若有对应 guide 文档，读取并提取相关段落
+4. 提供上下文相关的用法示例
+
+### Mode 3: Smart Recommendations
+
+**Triggers**: "下一步", "what's next", "推荐", "继续"
+
+**Process**:
+1. 检测当前项目状态（.workflow/state.json）
+2. 根据 workflows 配置推荐后续命令
+3. Explain WHY 每个推荐适合当前状态
+
+### Mode 4: Workflow Guide
+
+**Triggers**: "工作流", "workflow", "怎么开始", "用什么流程"
+
+**Process**:
+1. Read `Ref: phases/03-workflow-guide.md`
+2. 分析用户任务类型和复杂度
+3. 推荐匹配的工作流（主干管线/快速渠道/Issue 闭环）
+4. 给出具体命令序列
+
+### Mode 5: Beginner Onboarding
+
+**Triggers**: "新手", "getting started", "常用命令", "入门"
+
+**Process**:
+1. Query `catalog.json` essential_commands[]
+2. 逐个展示核心命令的简要说明
+3. 引导用户完成首次项目初始化
+
+### Mode 6: Skill & Agent Browsing
+
+**Triggers**: "skill", "agent", "技能", "有哪些 skill", "团队"
+
+**Process**:
+1. Read `Ref: phases/02-search-present.md`
+2. Query `catalog.json` skills[] 或 agents[]
+3. Filter by category
+4. 呈现分类列表，含描述
+
+### Mode 7: CLI Command Reference
+
+**Triggers**: "终端命令", "CLI", "maestro 命令", "terminal"
+
+**Process**:
+1. Query `catalog.json` cli_commands[]
+2. 按分类分组呈现
+3. 含别名和常用选项
+
+## Execution Flow
+
+```
+Input: $ARGUMENTS (free text)
+
+Phase 1: Parse Intent
+   └─ Ref: phases/01-parse-intent.md
+      ├─ 分析关键词确定 operation mode
+      ├─ 提取搜索词 / 命令名 / 分类过滤
+      └─ Output: { mode, query, category?, context? }
+
+Phase 2: Search & Present  (Mode 1/2/3/6/7)
+   └─ Ref: phases/02-search-present.md
+      ├─ 查询 catalog.json
+      ├─ 按模式过滤和排序
+      ├─ 读取 source 文件（Mode 2）
+      └─ Output: 格式化结果
+
+Phase 3: Workflow Guide  (Mode 4/5)
+   └─ Ref: phases/03-workflow-guide.md
+      ├─ 检测项目状态
+      ├─ 匹配工作流模板
+      ├─ 生成推荐命令序列
+      └─ Output: 引导信息
+```
+
+**Phase Reference Documents** (read on-demand):
+
+| Phase | Document | Purpose |
+|-------|----------|---------|
+| 1 | [phases/01-parse-intent.md](phases/01-parse-intent.md) | 意图解析和模式路由 |
+| 2 | [phases/02-search-present.md](phases/02-search-present.md) | 搜索和呈现 |
+| 3 | [phases/03-workflow-guide.md](phases/03-workflow-guide.md) | 工作流推荐和引导 |
+
+## Input Processing
+
+```
+$ARGUMENTS → Parse:
+  ├─ "search <keyword>"  → Mode 1: Command Search
+  ├─ 命令名 (如 "analyze") → Mode 2: Documentation
+  ├─ "下一步" / "next"     → Mode 3: Smart Recommendations
+  ├─ "工作流" / "workflow" → Mode 4: Workflow Guide
+  ├─ "新手" / "入门"       → Mode 5: Beginner Onboarding
+  ├─ "skill" / "agent"    → Mode 6: Skill & Agent Browsing
+  ├─ "CLI" / "终端"        → Mode 7: CLI Reference
+  ├─ 空参数               → Mode 5: Beginner Onboarding
+  └─ 其他自由文本          → Mode 1: Command Search (fuzzy)
+```
+
+## Command Catalog Quick Reference
+
+### 上游起源 + 核心 (core)
+
+| 命令 | 用途 |
+|------|------|
+| `/maestro` | 智能协调器，自动路由 |
+| `/maestro-init` | 项目初始化 |
+| `/maestro-brainstorm` | 头脑风暴 — 发散探索，多角色创意 |
+| `/maestro-blueprint` | 正式规格文档化 — 7-phase 收敛规格链 |
+| `/maestro-roadmap` | 路线图编排 — 消费上游 context，纯 Milestone > Phase 分解 |
+| `/maestro-quick` | 快速任务 |
+| `/maestro-overlay` | Overlay 管理 |
+| `/maestro-amend` | 修正补丁 |
+
+### 理解层 + 执行管线 (pipeline)
+
+| 命令 | 用途 |
+|------|------|
+| `/maestro-analyze` | 双层分析 — 宏观(文本参数)探索影响面 / 微观(数字参数)Phase 级深入 |
+| `/maestro-plan` | 任务规划 — 支持 `--from analyze:ANL-xxx` 直达 |
+| `/maestro-execute` | 任务执行 |
+| `/maestro-verify` | 验证确认 |
+
+### 质量管线 (quality)
+
+| 命令 | 用途 |
+|------|------|
+| `/quality-review` | 代码审查 |
+| `/quality-auto-test` | 自动测试 |
+| `/quality-test` | 业务测试 |
+| `/quality-debug` | 质量调试 |
+| `/quality-refactor` | 重构 |
+| `/quality-retrospective` | 复盘 |
+
+### 管理命令 (manage)
+
+| 命令 | 用途 |
+|------|------|
+| `/manage-issue` | Issue 管理 |
+| `/manage-issue-discover` | Issue 发现 |
+| `/manage-knowhow` | 知识管理 |
+| `/manage-status` | 状态查看 |
+| `/manage-wiki` | Wiki 管理 |
+| `/manage-harvest` | 收获 |
+
+## Workflow Mapping
+
+### 层级模型
+
+```
+Roadmap > Milestone > Phase > Task
+```
+
+- **Roadmap** = 项目级常驻规划文档
+- **Milestone** = 可独立交付的版本节点（v0.1.0-rc1, v0.2.0）
+- **Phase** = Milestone 内的同步屏障执行阶段
+- **Task** = Phase 内的具体代码修改单元（wave DAG 管理并行）
+
+### 命令拓扑
+
+```
+上游起源层（并列，可选）
+  brainstorm（发散/轻量）  |  blueprint（收敛/重型）
+
+理解层
+  analyze 双层: 宏观(文本参数) → scope_verdict | 微观(数字参数) → Phase 级决策
+
+编排层（可选）
+  roadmap — 消费上游 context，纯 Milestone > Phase 分解
+
+执行层
+  plan → execute → verify
+```
+
+### 合法路径
+
+| 路径 | 场景 | 命令序列 |
+|------|------|---------|
+| Path A | 完整新项目 | `brainstorm` → `blueprint`(可选) → `analyze "topic"` → `roadmap` → `analyze 1` → `plan 1` → `execute` → `verify` |
+| Path B | 旧项目大功能 | `analyze "feature X"` → `roadmap` → `analyze 1` → `plan 1` → `execute` → `verify` |
+| Path C | 中等功能 | `analyze "feature X"` → `plan --from analyze:ANL-xxx` → `execute` → `verify` |
+| Path D | 小改动 | `plan "fix auth bug"` → `execute` → `verify` |
+| Path E | 纯规格文档 | `blueprint "project idea"` → (供人阅读) |
+| Path F | 纯探索 | `brainstorm "idea"` → (供人决策) |
+| 快速修复 | 已知简单问题 | `/maestro-quick "修复描述"` |
+| Bug 追踪 | Issue 闭环 | `/manage-issue-discover` → `/manage-issue create` → analyze/plan/execute → close |
+| 全自动 | /maestro 入口 | `/maestro -y "任务描述"` |
+| 代码审查 | 质量管线 | `/quality-review` → `/quality-auto-test` → `/quality-test` |
+| 团队开发 | Team Lite | `/maestro-collab` |
+
+## Core Rules
+
+1. **Catalog First**: 先查 catalog.json，再按需读 source 文件
+2. **Guide 链接**: 对深层问题引用 guide/ 文档，告知用户具体文件名
+3. **上下文感知**: 检查 .workflow/ 存在性和 state.json 当前状态
+4. **精确匹配**: 搜索时支持命令名（不含前缀）、分类名、关键词
+5. **不执行命令**: 本 skill 只提供信息和推荐，不执行任何 maestro 命令
+
+## Error Handling
+
+| 场景 | 处理 |
+|------|------|
+| 命令未找到 | 模糊搜索最近匹配，提示正确命令名 |
+| 项目未初始化 | 推荐先运行 `/maestro-init` |
+| Guide 文件不存在 | 跳过，仅提供 catalog 中的描述 |
+| 参数为空 | 默认进入 Beginner Onboarding 模式 |
+
+## Related Resources
+
+- **Guide 目录**: `guide/` — 17 个专题指南文档
+- **Delegate 参考**: `~/.maestro/workflows/delegate-usage.md`
+- **Coding 哲学**: `~/.maestro/workflows/coding-philosophy.md`
+- **CLI 工具配置**: `~/.maestro/cli-tools.json`
+
+## Statistics
+
+- **Slash 命令**: 56 个（7 个分类）
+- **CLI 命令**: 21 个
+- **Skills**: 10 个（3 个分类）
+- **Agents**: 22 个（5 个分类）
+- **Guide 文档**: 17 个
+- **工作流路径**: 6 个合法路径 (Path A-F) + 3 个辅助流程