maestro-flow 0.5.36 → 0.5.38

package/.agy/skills/manage-knowhow-capture/SKILL.md

@@ -10,82 +10,82 @@ allowed-tools:
   - view_file
   - write_to_file
 ---
-<purpose>
-Capture reusable knowledge into `.workflow/knowhow/` with type-specific structured fields.
-Auto-indexed by WikiIndexer (type=knowhow), searchable via `maestro search --type knowhow`.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/knowhow.md
-</required_reading>
-
-<context>
-$ARGUMENTS — type token + description + optional flags.
-
-**Flags**: `--lang <lang>`, `--source <url>`, `--tag tag1,tag2`, `--title <title>`, `--description <desc>`, `--asset-type <type>`, `--code-paths <paths>`, `--category <cat>`
-
-**Type routing** (first token match):
-
-| Token | Type | Prefix | Key fields |
-|-------|------|--------|------------|
-| `compact`/`session`/`压缩`/`保存` | compact | KNW- | objective, files, decisions, plan, pending |
-| `template`/`tpl`/`模板` | template | TPL- | language, code block, usage, parameters |
-| `recipe`/`rcp`/`配方`/`步骤` | recipe | RCP- | prerequisites, steps, expected outcome, pitfalls |
-| `reference`/`ref`/`参考`/`引用` | reference | REF- | source URL, key points, scenarios, examples |
-| `decision`/`dcs`/`决策`/`adr` | decision | DCS- | context, alternatives table, rationale, consequences |
-| `tip`/`note`/`记录`/`快速` | tip | TIP- | content, tags |
-| `asset`/`ast`/`资产`/`契约` | asset | AST- | assetType, codePaths, category |
-| `blueprint`/`blp`/`蓝图` | blueprint | BLP- | codePaths, category |
-| `document`/`doc`/`文档` | document | DOC- | (general fallback) |
-| `insight`/`ins`/`洞察`/`经验` | insight | INS- | content, tags, phase (replaces former manage-learn) |
-| Short text + `--tag` | tip | TIP- | — |
-| No args | — | — | ask_question (10 options) |
-
-**Output**: `.workflow/knowhow/{PREFIX}-{YYYYMMDD}-{slug}.md` with YAML frontmatter (title, description, type, category, created, tags, source, lang, status)
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/knowhow.md' completely.
-
-**Description rule**: Every entry MUST have a `description` field in frontmatter — a one-line summary (under 120 chars) for search results. WikiIndexer uses priority chain: `description > content[:240]`. Use `--description` flag value if provided; otherwise auto-generate from content.
-
-**Tags language rule**: Tags must match content language. Chinese content → Chinese tags (如 `认证,令牌,刷新`). English content → English tags. Mixed → bilingual.
-
-**Type-specific content rules**:
-
-| Type | Content extraction |
-|------|-------------------|
-| compact | Extract from conversation: session ID, objective, execution plan (verbatim), working files (3-8), decisions, constraints, pending. Plan priority: workflow IMPL_PLAN.md > TodoWrite > user-stated > inferred. |
-| template | Ask for: language, code block, parameters (placeholders), usage context, dependencies |
-| recipe | Ask for: goal, prerequisites, numbered steps, expected outcome, common pitfalls |
-| reference | From --source URL or ask. Key points, applicable scenarios, quick examples. Offer WebFetch if URL provided. |
-| decision | Context, alternatives (table: alt/pros/cons/rejected-because), rationale, consequences. Status: proposed/accepted/superseded. |
-| tip | Content = everything after type token. Auto-detect context from recent files. |
-| asset | assetType (api-contract/data-model/prompt/config), codePaths, category for agent discovery |
-| blueprint | Architecture design with codePaths and category |
-</execution>
-
-<error_codes>
-| Code | Condition | Recovery |
-|------|-----------|----------|
-| E002 | Template: no code provided after prompt | Ask again or cancel |
-| E003 | Recipe: no steps provided after prompt | Ask again or cancel |
-| W001 | No active workflow session (compact) | Captures conversation only |
-| W002 | Plan detection found no explicit plan (compact) | Uses inferred plan |
-</error_codes>
-
-<success_criteria>
-- [ ] Type detected or selected, all type-specific fields populated
-- [ ] File written to .workflow/knowhow/ with correct prefix and YAML frontmatter
-- [ ] Confirmation displayed with ID, type, path
-</success_criteria>
-
-<completion>
-### Next-step routing
-
-| Condition | Suggestion |
-|-----------|-----------|
-| Entry captured | `/manage-knowhow list` to view library |
-| Want to connect entries | `/manage-wiki connect` |
-| Want to bridge to specs | `/spec-add <category>` with `--spec-category` |
-</completion>
+<purpose>
+Capture reusable knowledge into `.workflow/knowhow/` with type-specific structured fields.
+Auto-indexed by WikiIndexer (type=knowhow), searchable via `maestro search --type knowhow`.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/knowhow.md
+</required_reading>
+
+<context>
+$ARGUMENTS — type token + description + optional flags.
+
+**Flags**: `--lang <lang>`, `--source <url>`, `--tag tag1,tag2`, `--title <title>`, `--description <desc>`, `--asset-type <type>`, `--code-paths <paths>`, `--category <cat>`
+
+**Type routing** (first token match):
+
+| Token | Type | Prefix | Key fields |
+|-------|------|--------|------------|
+| `compact`/`session`/`压缩`/`保存` | compact | KNW- | objective, files, decisions, plan, pending |
+| `template`/`tpl`/`模板` | template | TPL- | language, code block, usage, parameters |
+| `recipe`/`rcp`/`配方`/`步骤` | recipe | RCP- | prerequisites, steps, expected outcome, pitfalls |
+| `reference`/`ref`/`参考`/`引用` | reference | REF- | source URL, key points, scenarios, examples |
+| `decision`/`dcs`/`决策`/`adr` | decision | DCS- | context, alternatives table, rationale, consequences |
+| `tip`/`note`/`记录`/`快速` | tip | TIP- | content, tags |
+| `asset`/`ast`/`资产`/`契约` | asset | AST- | assetType, codePaths, category |
+| `blueprint`/`blp`/`蓝图` | blueprint | BLP- | codePaths, category |
+| `document`/`doc`/`文档` | document | DOC- | (general fallback) |
+| `insight`/`ins`/`洞察`/`经验` | insight | INS- | content, tags, phase (replaces former manage-learn) |
+| Short text + `--tag` | tip | TIP- | — |
+| No args | — | — | ask_question (10 options) |
+
+**Output**: `.workflow/knowhow/{PREFIX}-{YYYYMMDD}-{slug}.md` with YAML frontmatter (title, description, type, category, created, tags, source, lang, status)
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/knowhow.md' completely.
+
+**Description rule**: Every entry MUST have a `description` field in frontmatter — a one-line summary (under 120 chars) for search results. WikiIndexer uses priority chain: `description > content[:240]`. Use `--description` flag value if provided; otherwise auto-generate from content.
+
+**Tags language rule**: Tags must match content language. Chinese content → Chinese tags (如 `认证,令牌,刷新`). English content → English tags. Mixed → bilingual.
+
+**Type-specific content rules**:
+
+| Type | Content extraction |
+|------|-------------------|
+| compact | Extract from conversation: session ID, objective, execution plan (verbatim), working files (3-8), decisions, constraints, pending. Plan priority: workflow IMPL_PLAN.md > TodoWrite > user-stated > inferred. |
+| template | Ask for: language, code block, parameters (placeholders), usage context, dependencies |
+| recipe | Ask for: goal, prerequisites, numbered steps, expected outcome, common pitfalls |
+| reference | From --source URL or ask. Key points, applicable scenarios, quick examples. Offer WebFetch if URL provided. |
+| decision | Context, alternatives (table: alt/pros/cons/rejected-because), rationale, consequences. Status: proposed/accepted/superseded. |
+| tip | Content = everything after type token. Auto-detect context from recent files. |
+| asset | assetType (api-contract/data-model/prompt/config), codePaths, category for agent discovery |
+| blueprint | Architecture design with codePaths and category |
+</execution>
+
+<error_codes>
+| Code | Condition | Recovery |
+|------|-----------|----------|
+| E002 | Template: no code provided after prompt | Ask again or cancel |
+| E003 | Recipe: no steps provided after prompt | Ask again or cancel |
+| W001 | No active workflow session (compact) | Captures conversation only |
+| W002 | Plan detection found no explicit plan (compact) | Uses inferred plan |
+</error_codes>
+
+<success_criteria>
+- [ ] Type detected or selected, all type-specific fields populated
+- [ ] File written to .workflow/knowhow/ with correct prefix and YAML frontmatter
+- [ ] Confirmation displayed with ID, type, path
+</success_criteria>
+
+<completion>
+### Next-step routing
+
+| Condition | Suggestion |
+|-----------|-----------|
+| Entry captured | `/manage-knowhow list` to view library |
+| Want to connect entries | `/manage-wiki connect` |
+| Want to bridge to specs | `/spec-add <category>` with `--spec-category` |
+</completion>

package/.agy/skills/manage-knowledge-audit/SKILL.md

@@ -14,123 +14,123 @@ allowed-tools:
   - view_file
   - write_to_file
 ---
-<purpose>
-审查 spec/knowhow/artifact 存储，识别矛盾/失效/孤儿，通过 keep/deprecate/delete 三态清理。对称于 `manage-harvest`（写入入口）。
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/knowledge-audit.md
-</required_reading>
-
-<deferred_reading>
-- @~/.maestro/workflows/harvest.md (audit 检测的 artifact 是 harvest 的产物源)
-- @~/.maestro/workflows/specs-add.md (deprecate 操作所需的 `<spec-entry>` 变形)
-</deferred_reading>
-
-<context>
-Arguments: $ARGUMENTS
-
-**Scope（必选）：** `spec` | `knowhow` | `artifact` | `all`
-
-**删除策略**默认 `--interactive`（三态面板逐项决策）；非交互模式 `--mark`（仅打标）/ `--delete`（软删到 `.trash/`）/ `--purge`（物理擦除，仅 artifact 且需双重确认）。
-
-Flag 全集、scope 对应的扫描路径、Stage 步骤、检测算法定义在 workflow knowledge-audit.md。
-</context>
-
-<execution>
-Follow `~/.maestro/workflows/knowledge-audit.md` Stages 1-8 in order.
-
-### Phase Gates (MANDATORY, BLOCKING)
-
-**GATE 1: Load → Detect** (Stages 1-2 → Stage 4)
-- REQUIRED: Scope 解析通过，互斥标志校验完成。
-- REQUIRED: 三存储按 scope 加载完成。
-- REQUIRED: 加载已有冲突标记: `maestro spec conflict list` → 合并到 finding 池。
-- BLOCKED if scope 非法或存储不可读: E001/E002。
-
-**GATE 2: Detect → Decision** (Stage 4 → Stage 5)
-- REQUIRED: Finding 池按 P0/P1/P2 分级输出。
-- REQUIRED: 已标记 `contested` 的条目自动归入 P0 finding（来源: conflict-marker）。
-- REQUIRED: 未 harvest 的 artifact 删除前触发抢救确认（W002）。
-- BLOCKED if finding 为空: 无需淘汰，直接输出报告。
-
-**GATE 3: Decision → Mutate** (Stage 5 → Stage 6-7)
-- REQUIRED: Backup tarball 生成于 `.workflow/.trash/knowledge-audit-{timestamp}/`。
-- REQUIRED: 备份成功后方可执行变更。
-- REQUIRED: `--purge` 需双重确认（仅 artifact scope）。
-- BLOCKED if 备份失败: E005，禁止执行变更。
-
-### Execution Constraints
-
-- **Deprecate over delete**: 文本存储首选 `status="deprecated"`，保留历史。
-- **Purge 仅 artifact**: `--purge` 不作用于 spec/knowhow。
-- **Rescue before delete**: 未抽取 artifact 删除前强制提示先 `/manage-harvest`。
-
-### Conflict Resolution Integration
-
-四态决策（扩展自三态 keep/deprecate/delete）：
-
-| 动作 | 适用场景 | 执行 |
-|------|---------|------|
-| `keep` | 内容正确，无需变更 | 写 audit-log ignore 记录 |
-| `contest` | 矛盾真实存在，需进一步审查 | `maestro spec conflict mark <file> <line> --note "<evidence>"` |
-| `deprecate` | 内容过时或被取代 | 注入 `status="deprecated"` + `maestro spec conflict clear <file> <line>` |
-| `delete` | 内容明确错误 | 移除 entry + `maestro spec conflict clear <file> <line>` |
-
-**关键**: deprecate/delete 执行时，如果目标条目有 conflict-marker，必须同步调用 `maestro spec conflict clear` 清除标记，避免悬空冲突。
-
-### Code-as-Truth 校验（审查核心原则）
-
-**代码是唯一真理源。** Spec/knowhow 中的任何声明，必须与代码实际行为一致。
-
-当 detector 发现 spec 条目声称某行为/规则时：
-1. **代码校验**: grep/read 代码中相关实现，确认 spec 声明是否与代码一致
-2. **不一致处理**:
-   - 代码正确、spec 过时 → `deprecate` 或 `delete` spec 条目
-   - 代码正确、spec 不完整 → `contest` 并建议补充
-   - 代码有 bug、spec 正确 → `keep` spec，生成 issue 修代码
-3. **禁止**: 仅凭 spec 文本判断正确性。每个 finding 的 evidence 必须包含代码引用（文件:行号）
-</execution>
-
-<completion>
-### Next-step routing
-
-| Condition | Suggestion |
-|-----------|-----------|
-| 复审淘汰记录 | 查看 `audit-report-{date}.md` |
-| 抢救未抽取 artifact | `/manage-harvest <artifact-id>` |
-| 验证 spec 现状 | `/spec-load --role implement` |
-| 查看冲突标记 | `maestro spec conflict list` |
-| 清除已解决冲突 | `maestro spec conflict clear-all <file>` |
-| 周期巡检 | `--scope all --report` |
-</completion>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | `.workflow/` 未初始化 | 先跑 `/maestro-init` |
-| E002 | error | `--scope` 缺失或非法 | 提供 spec/knowhow/artifact/all |
-| E003 | error | `--purge` 与 `--dry-run` 同用 | 二选一 |
-| E004 | error | `--purge` 作用于非 artifact 范围 | purge 仅支持 artifact scope |
-| E005 | error | 备份失败（`.trash/` 写入异常） | 检查磁盘空间与权限，重试 |
-| W001 | warning | 检出冲突但用户选择 keep | 记入 report，不阻断 |
-| W002 | warning | 待删 artifact 无 harvest-log 记录 | 提示先跑 manage-harvest |
-| W003 | warning | 循环 supersedes 链 | 自动断环或交互选保留节点 |
-| W004 | warning | 检测耗时 >120s（大规模 spec 库） | 建议加 `--scope` 收敛或 `--since` 增量 |
-| W005 | warning | LLM detector 不可用 | 降级到正则+图算法子集，跳过 B/G 类语义场景 |
-</error_codes>
-
-<success_criteria>
-- [ ] Scope 正确解析，互斥标志校验通过
-- [ ] 三存储按 scope 加载完成，构建出统一 finding 池
-- [ ] Stage 3 时间线索引建立（mtime ↔ session/milestone 状态）
-- [ ] Stage 4 按 P0/P1/P2 输出 finding 列表
-- [ ] 如非 `--report`：用户对每项做出三态决策
-- [ ] 未 harvest 的 artifact 删除前触发抢救确认
-- [ ] Stage 6 backup tarball 生成于 `.workflow/.trash/`
-- [ ] `deprecate` 通过元数据注入完成（spec/knowhow 文件未被物理删除）
-- [ ] `delete` 移动至 `.trash/`，索引同步更新
-- [ ] `purge` 仅在双重确认通过后执行
-- [ ] `audit-report-{date}.md` + `audit-log.jsonl` 写入完成
-- [ ] 摘要展示三存储变更计数与下一步路由
-</success_criteria>
+<purpose>
+审查 spec/knowhow/artifact 存储，识别矛盾/失效/孤儿，通过 keep/deprecate/delete 三态清理。对称于 `manage-harvest`（写入入口）。
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/knowledge-audit.md
+</required_reading>
+
+<deferred_reading>
+- @~/.maestro/workflows/harvest.md (audit 检测的 artifact 是 harvest 的产物源)
+- @~/.maestro/workflows/specs-add.md (deprecate 操作所需的 `<spec-entry>` 变形)
+</deferred_reading>
+
+<context>
+Arguments: $ARGUMENTS
+
+**Scope（必选）：** `spec` | `knowhow` | `artifact` | `all`
+
+**删除策略**默认 `--interactive`（三态面板逐项决策）；非交互模式 `--mark`（仅打标）/ `--delete`（软删到 `.trash/`）/ `--purge`（物理擦除，仅 artifact 且需双重确认）。
+
+Flag 全集、scope 对应的扫描路径、Stage 步骤、检测算法定义在 workflow knowledge-audit.md。
+</context>
+
+<execution>
+Follow `~/.maestro/workflows/knowledge-audit.md` Stages 1-8 in order.
+
+### Phase Gates (MANDATORY, BLOCKING)
+
+**GATE 1: Load → Detect** (Stages 1-2 → Stage 4)
+- REQUIRED: Scope 解析通过，互斥标志校验完成。
+- REQUIRED: 三存储按 scope 加载完成。
+- REQUIRED: 加载已有冲突标记: `maestro spec conflict list` → 合并到 finding 池。
+- BLOCKED if scope 非法或存储不可读: E001/E002。
+
+**GATE 2: Detect → Decision** (Stage 4 → Stage 5)
+- REQUIRED: Finding 池按 P0/P1/P2 分级输出。
+- REQUIRED: 已标记 `contested` 的条目自动归入 P0 finding（来源: conflict-marker）。
+- REQUIRED: 未 harvest 的 artifact 删除前触发抢救确认（W002）。
+- BLOCKED if finding 为空: 无需淘汰，直接输出报告。
+
+**GATE 3: Decision → Mutate** (Stage 5 → Stage 6-7)
+- REQUIRED: Backup tarball 生成于 `.workflow/.trash/knowledge-audit-{timestamp}/`。
+- REQUIRED: 备份成功后方可执行变更。
+- REQUIRED: `--purge` 需双重确认（仅 artifact scope）。
+- BLOCKED if 备份失败: E005，禁止执行变更。
+
+### Execution Constraints
+
+- **Deprecate over delete**: 文本存储首选 `status="deprecated"`，保留历史。
+- **Purge 仅 artifact**: `--purge` 不作用于 spec/knowhow。
+- **Rescue before delete**: 未抽取 artifact 删除前强制提示先 `/manage-harvest`。
+
+### Conflict Resolution Integration
+
+四态决策（扩展自三态 keep/deprecate/delete）：
+
+| 动作 | 适用场景 | 执行 |
+|------|---------|------|
+| `keep` | 内容正确，无需变更 | 写 audit-log ignore 记录 |
+| `contest` | 矛盾真实存在，需进一步审查 | `maestro spec conflict mark <file> <line> --note "<evidence>"` |
+| `deprecate` | 内容过时或被取代 | 注入 `status="deprecated"` + `maestro spec conflict clear <file> <line>` |
+| `delete` | 内容明确错误 | 移除 entry + `maestro spec conflict clear <file> <line>` |
+
+**关键**: deprecate/delete 执行时，如果目标条目有 conflict-marker，必须同步调用 `maestro spec conflict clear` 清除标记，避免悬空冲突。
+
+### Code-as-Truth 校验（审查核心原则）
+
+**代码是唯一真理源。** Spec/knowhow 中的任何声明，必须与代码实际行为一致。
+
+当 detector 发现 spec 条目声称某行为/规则时：
+1. **代码校验**: grep/read 代码中相关实现，确认 spec 声明是否与代码一致
+2. **不一致处理**:
+   - 代码正确、spec 过时 → `deprecate` 或 `delete` spec 条目
+   - 代码正确、spec 不完整 → `contest` 并建议补充
+   - 代码有 bug、spec 正确 → `keep` spec，生成 issue 修代码
+3. **禁止**: 仅凭 spec 文本判断正确性。每个 finding 的 evidence 必须包含代码引用（文件:行号）
+</execution>
+
+<completion>
+### Next-step routing
+
+| Condition | Suggestion |
+|-----------|-----------|
+| 复审淘汰记录 | 查看 `audit-report-{date}.md` |
+| 抢救未抽取 artifact | `/manage-harvest <artifact-id>` |
+| 验证 spec 现状 | `/spec-load --role implement` |
+| 查看冲突标记 | `maestro spec conflict list` |
+| 清除已解决冲突 | `maestro spec conflict clear-all <file>` |
+| 周期巡检 | `--scope all --report` |
+</completion>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | `.workflow/` 未初始化 | 先跑 `/maestro-init` |
+| E002 | error | `--scope` 缺失或非法 | 提供 spec/knowhow/artifact/all |
+| E003 | error | `--purge` 与 `--dry-run` 同用 | 二选一 |
+| E004 | error | `--purge` 作用于非 artifact 范围 | purge 仅支持 artifact scope |
+| E005 | error | 备份失败（`.trash/` 写入异常） | 检查磁盘空间与权限，重试 |
+| W001 | warning | 检出冲突但用户选择 keep | 记入 report，不阻断 |
+| W002 | warning | 待删 artifact 无 harvest-log 记录 | 提示先跑 manage-harvest |
+| W003 | warning | 循环 supersedes 链 | 自动断环或交互选保留节点 |
+| W004 | warning | 检测耗时 >120s（大规模 spec 库） | 建议加 `--scope` 收敛或 `--since` 增量 |
+| W005 | warning | LLM detector 不可用 | 降级到正则+图算法子集，跳过 B/G 类语义场景 |
+</error_codes>
+
+<success_criteria>
+- [ ] Scope 正确解析，互斥标志校验通过
+- [ ] 三存储按 scope 加载完成，构建出统一 finding 池
+- [ ] Stage 3 时间线索引建立（mtime ↔ session/milestone 状态）
+- [ ] Stage 4 按 P0/P1/P2 输出 finding 列表
+- [ ] 如非 `--report`：用户对每项做出三态决策
+- [ ] 未 harvest 的 artifact 删除前触发抢救确认
+- [ ] Stage 6 backup tarball 生成于 `.workflow/.trash/`
+- [ ] `deprecate` 通过元数据注入完成（spec/knowhow 文件未被物理删除）
+- [ ] `delete` 移动至 `.trash/`，索引同步更新
+- [ ] `purge` 仅在双重确认通过后执行
+- [ ] `audit-report-{date}.md` + `audit-log.jsonl` 写入完成
+- [ ] 摘要展示三存储变更计数与下一步路由
+</success_criteria>

package/.agy/skills/manage-status/SKILL.md

@@ -7,55 +7,55 @@ allowed-tools:
   - run_command
   - view_file
 ---
-<purpose>
-Project dashboard: artifact progress, task counts, active work, next-step suggestions.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/status.md
-</required_reading>
-
-<context>
-$ARGUMENTS (no arguments required)
-
-**State files read:**
-- `.workflow/state.json` -- project-level state machine + artifact registry
-- `.workflow/roadmap.md` -- milestone and phase structure
-- `.workflow/scratch/*/plan.json` -- plan metadata (via artifact registry paths)
-- `.workflow/scratch/*/.task/TASK-*.json` -- individual task statuses
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/status.md' completely.
-
-Next-step decision table defined in workflow status.md Step 5.
-</execution>
-
-<error_codes>
-| Code | Severity | Description | Stage |
-|------|----------|-------------|-------|
-| E001 | fatal | `.workflow/` not initialized -- run `/maestro-init` first | parse_input |
-| E002 | fatal | `state.json` missing or corrupt -- project state unrecoverable | parse_input |
-</error_codes>
-
-<success_criteria>
-- [ ] Project state loaded from `state.json`
-- [ ] Roadmap parsed with milestone/phase structure
-- [ ] Per-phase progress calculated (task counts, completion %)
-- [ ] Dashboard rendered with progress bars and status table
-- [ ] Active work section shows current phase details
-- [ ] Next steps suggested based on current state analysis
-- [ ] Wiki health score displayed (or graceful unavailable message)
-</success_criteria>
-
-<completion>
-### Next-step routing
-
-| Condition | Suggestion |
-|-----------|-----------|
-| Phase needs analysis | `/maestro-analyze {phase}` |
-| Phase needs planning | `/maestro-plan {phase}` |
-| Phase needs execution | `/maestro-execute {phase}` |
-| Milestone ready for audit | `/maestro-milestone-audit` |
-| Issues need triage | `/manage-issue list` |
-</completion>
+<purpose>
+Project dashboard: artifact progress, task counts, active work, next-step suggestions.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/status.md
+</required_reading>
+
+<context>
+$ARGUMENTS (no arguments required)
+
+**State files read:**
+- `.workflow/state.json` -- project-level state machine + artifact registry
+- `.workflow/roadmap.md` -- milestone and phase structure
+- `.workflow/scratch/*/plan.json` -- plan metadata (via artifact registry paths)
+- `.workflow/scratch/*/.task/TASK-*.json` -- individual task statuses
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/status.md' completely.
+
+Next-step decision table defined in workflow status.md Step 5.
+</execution>
+
+<error_codes>
+| Code | Severity | Description | Stage |
+|------|----------|-------------|-------|
+| E001 | fatal | `.workflow/` not initialized -- run `/maestro-init` first | parse_input |
+| E002 | fatal | `state.json` missing or corrupt -- project state unrecoverable | parse_input |
+</error_codes>
+
+<success_criteria>
+- [ ] Project state loaded from `state.json`
+- [ ] Roadmap parsed with milestone/phase structure
+- [ ] Per-phase progress calculated (task counts, completion %)
+- [ ] Dashboard rendered with progress bars and status table
+- [ ] Active work section shows current phase details
+- [ ] Next steps suggested based on current state analysis
+- [ ] Wiki health score displayed (or graceful unavailable message)
+</success_criteria>
+
+<completion>
+### Next-step routing
+
+| Condition | Suggestion |
+|-----------|-----------|
+| Phase needs analysis | `/maestro-analyze {phase}` |
+| Phase needs planning | `/maestro-plan {phase}` |
+| Phase needs execution | `/maestro-execute {phase}` |
+| Milestone ready for audit | `/maestro-milestone-audit` |
+| Issues need triage | `/manage-issue list` |
+</completion>