maestro-flow 0.5.36 → 0.5.38

package/.codex/skills/manage-issue/SKILL.md

@@ -1,88 +1,88 @@
----
-name: manage-issue
-description: Create, query, update, close, and link issues
-argument-hint: "<create|list|status|update|close|link> [options]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
----
-
-<purpose>
-Issue CRUD operations: create, list, status, update, close, and link issues to tasks.
-All data stored in `.workflow/issues/issues.jsonl` with auto-created directory on first use.
-
-**Closed-loop workflow**: issue → `$maestro-analyze --gaps <ISS-ID>` (root cause analysis) → `$maestro-plan --gaps` (solution planning) → `$maestro-execute` (implementation). For automated issue discovery, use `$manage-issue-discover`.
-</purpose>
-
-<required_reading>
-Read `~/.maestro/workflows/issue.md` before executing any subcommand. This file defines the issue.json schema, ID format, field validation rules, and JSONL storage conventions.
-</required_reading>
-
-<context>
-$ARGUMENTS — subcommand followed by options.
-
-```bash
-$manage-issue "create --title 'Auth token expiry bug' --severity high --source manual"
-$manage-issue "list --status open --severity high"
-$manage-issue "status ISS-20260318-001"
-$manage-issue "update ISS-20260318-001 --priority critical --tags auth,security"
-$manage-issue "close ISS-20260318-001 --resolution fixed"
-$manage-issue "link ISS-20260318-001 --task TASK-003"
-```
-
-**Subcommands**: `create`, `list`, `status`, `update`, `close`, `link`.
-</context>
-
-<execution>
-
-### Step 1: Parse Subcommand
-
-Extract first token as subcommand. Valid: `create`, `list`, `status`, `update`, `close`, `link`.
-If missing or invalid, display usage and prompt user (E_NO_SUBCOMMAND, E_INVALID_SUBCOMMAND).
-
-### Step 2: Ensure Storage
-
-If `.workflow/issues/` does not exist, auto-create the directory and write an empty `issues.jsonl` file. Log as E_ISSUES_DIR_MISSING (warning, non-blocking).
-
-### Step 3: Execute Subcommand
-
-**create**: Read `~/.maestro/templates/issue.json` for schema. Generate ID `ISS-{YYYYMMDD}-{NNN}`. If required fields are missing, prompt via `request_user_input`:
-```json
-{ "questions": [{ "id": "issue_title", "header": "New Issue", "question": "What is the issue title?" }, { "id": "issue_severity", "header": "Issue Severity", "question": "What severity level?", "options": [{ "label": "high (Recommended)", "description": "Production-impacting or blocking" }, { "label": "medium", "description": "Degraded functionality" }, { "label": "low", "description": "Minor or cosmetic" }] }] }
-```
-Append JSON line to `issues.jsonl`.
-
-**list**: Read `issues.jsonl`, filter by `--status`, `--phase`, `--severity`, `--source`. Display as table:
-```
-ID              | Severity | Status | Title
-ISS-20260318-001 | high     | open   | Auth token expiry bug
-```
-
-**status**: Find issue by ID in `issues.jsonl`. Display all fields in detail format.
-
-**update**: Find issue by ID, merge provided fields, rewrite the line in `issues.jsonl`. Track `updated_at` timestamp.
-
-**close**: Find issue by ID, set status to `closed`, add `resolution` and `closed_at`. Move line from `issues.jsonl` to `issue-history.jsonl`.
-
-**link**: Bidirectional cross-reference between issue and task:
-1. Find issue by ID in `issues.jsonl`, add task ID to issue's `linked_tasks[]` array, rewrite the line
-2. Read task JSON at `.workflow/.task/{TASK-ID}.json` (or `.task/{TASK-ID}.json`). Edit the task's `linked_issues` field — append the issue ID to the array. If `linked_issues` field does not exist, create it as `[ISS-ID]`
-3. Both writes must succeed for the link to be considered complete
-</execution>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E_NO_SUBCOMMAND | error | No subcommand provided -- display valid subcommands |
-| E_INVALID_SUBCOMMAND | error | Unrecognized subcommand |
-| E_ISSUES_DIR_MISSING | warning | `.workflow/issues/` not found — auto-create directory and empty issues.jsonl |
-</error_codes>
-
-<success_criteria>
-- [ ] Subcommand parsed and validated
-- [ ] Storage directory and files auto-created on first use
-- [ ] create: generates unique ISS-id, prompts for required fields, appends to JSONL
-- [ ] list: filters by status/phase/severity/source, renders table
-- [ ] status: displays full detail for given ISS-id
-- [ ] update: merges fields, tracks updated_at timestamp
-- [ ] close: sets status closed, moves to history file
-- [ ] link: bidirectional cross-reference between issue and task
-</success_criteria>
+---
+name: manage-issue
+description: Create, query, update, close, and link issues
+argument-hint: "<create|list|status|update|close|link> [options]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
+---
+
+<purpose>
+Issue CRUD operations: create, list, status, update, close, and link issues to tasks.
+All data stored in `.workflow/issues/issues.jsonl` with auto-created directory on first use.
+
+**Closed-loop workflow**: issue → `$maestro-analyze --gaps <ISS-ID>` (root cause analysis) → `$maestro-plan --gaps` (solution planning) → `$maestro-execute` (implementation). For automated issue discovery, use `$manage-issue-discover`.
+</purpose>
+
+<required_reading>
+Read `~/.maestro/workflows/issue.md` before executing any subcommand. This file defines the issue.json schema, ID format, field validation rules, and JSONL storage conventions.
+</required_reading>
+
+<context>
+$ARGUMENTS — subcommand followed by options.
+
+```bash
+$manage-issue "create --title 'Auth token expiry bug' --severity high --source manual"
+$manage-issue "list --status open --severity high"
+$manage-issue "status ISS-20260318-001"
+$manage-issue "update ISS-20260318-001 --priority critical --tags auth,security"
+$manage-issue "close ISS-20260318-001 --resolution fixed"
+$manage-issue "link ISS-20260318-001 --task TASK-003"
+```
+
+**Subcommands**: `create`, `list`, `status`, `update`, `close`, `link`.
+</context>
+
+<execution>
+
+### Step 1: Parse Subcommand
+
+Extract first token as subcommand. Valid: `create`, `list`, `status`, `update`, `close`, `link`.
+If missing or invalid, display usage and prompt user (E_NO_SUBCOMMAND, E_INVALID_SUBCOMMAND).
+
+### Step 2: Ensure Storage
+
+If `.workflow/issues/` does not exist, auto-create the directory and write an empty `issues.jsonl` file. Log as E_ISSUES_DIR_MISSING (warning, non-blocking).
+
+### Step 3: Execute Subcommand
+
+**create**: Read `~/.maestro/templates/issue.json` for schema. Generate ID `ISS-{YYYYMMDD}-{NNN}`. If required fields are missing, prompt via `request_user_input`:
+```json
+{ "questions": [{ "id": "issue_title", "header": "New Issue", "question": "What is the issue title?" }, { "id": "issue_severity", "header": "Issue Severity", "question": "What severity level?", "options": [{ "label": "high (Recommended)", "description": "Production-impacting or blocking" }, { "label": "medium", "description": "Degraded functionality" }, { "label": "low", "description": "Minor or cosmetic" }] }] }
+```
+Append JSON line to `issues.jsonl`.
+
+**list**: Read `issues.jsonl`, filter by `--status`, `--phase`, `--severity`, `--source`. Display as table:
+```
+ID              | Severity | Status | Title
+ISS-20260318-001 | high     | open   | Auth token expiry bug
+```
+
+**status**: Find issue by ID in `issues.jsonl`. Display all fields in detail format.
+
+**update**: Find issue by ID, merge provided fields, rewrite the line in `issues.jsonl`. Track `updated_at` timestamp.
+
+**close**: Find issue by ID, set status to `closed`, add `resolution` and `closed_at`. Move line from `issues.jsonl` to `issue-history.jsonl`.
+
+**link**: Bidirectional cross-reference between issue and task:
+1. Find issue by ID in `issues.jsonl`, add task ID to issue's `linked_tasks[]` array, rewrite the line
+2. Read task JSON at `.workflow/.task/{TASK-ID}.json` (or `.task/{TASK-ID}.json`). Edit the task's `linked_issues` field — append the issue ID to the array. If `linked_issues` field does not exist, create it as `[ISS-ID]`
+3. Both writes must succeed for the link to be considered complete
+</execution>
+
+<error_codes>
+| Code | Severity | Description |
+|------|----------|-------------|
+| E_NO_SUBCOMMAND | error | No subcommand provided -- display valid subcommands |
+| E_INVALID_SUBCOMMAND | error | Unrecognized subcommand |
+| E_ISSUES_DIR_MISSING | warning | `.workflow/issues/` not found — auto-create directory and empty issues.jsonl |
+</error_codes>
+
+<success_criteria>
+- [ ] Subcommand parsed and validated
+- [ ] Storage directory and files auto-created on first use
+- [ ] create: generates unique ISS-id, prompts for required fields, appends to JSONL
+- [ ] list: filters by status/phase/severity/source, renders table
+- [ ] status: displays full detail for given ISS-id
+- [ ] update: merges fields, tracks updated_at timestamp
+- [ ] close: sets status closed, moves to history file
+- [ ] link: bidirectional cross-reference between issue and task
+</success_criteria>

package/.codex/skills/manage-issue-discover/SKILL.md

@@ -227,7 +227,7 @@ Initialize `discovery-state.json`:
 4. Store dimensions in `{discoveryDir}/exploration-plan.json`
 5. Generate N dimension rows (wave 1) + 1 dedup row (wave 2)
 
-**Specs loading**: `specs_content = maestro spec load --category coding` -- pass to agents for severity calibration.
+**Specs loading**: `specs_content = maestro load --type spec --category coding` -- pass to agents for severity calibration.
 
 **User validation**: Display perspective/dimension breakdown (skip if AUTO_YES).
 

package/.codex/skills/manage-learn/SKILL.md

@@ -1,137 +1,137 @@
----
-name: manage-learn
-description: Capture and search learning insights and tips
-argument-hint: "[\"<insight text>\"|list|search <query>|show <INS-id>] [--category pattern|antipattern|decision|tool|gotcha|technique] [--tag t1,t2] [--phase N] [--confidence high|medium|low]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
----
-
-<purpose>
-Pure file-operation CRUD skill for the workflow knowhow library. No agent spawning, no CLI calls, no LLM inference — just parse-infer-append-confirm. Complements `quality-retrospective`: where retrospective extracts insights in bulk from completed phases, `manage-learn` captures one timeless insight at a time during active work. Both write to the same `.workflow/specs/learnings.md` store, disambiguated by `source` and `lens` fields.
-
-```
-Parse Mode  →  Bootstrap Store  →  Execute Mode  →  Confirm
-(capture /       (on first use)     (Bash/Read/      (INS-id
-  list /          Bash+Write)        Write/Grep)      + hints)
-  search /
-  show)
-```
-</purpose>
-
-<context>
-$ARGUMENTS — mode token followed by options.
-
-```bash
-$manage-learn "Always read state.json before planning to detect current phase"
-$manage-learn "list --limit 10 --category antipattern"
-$manage-learn "search context propagation"
-$manage-learn "show INS-a3f7b2c1"
-$manage-learn "\"Zod v4 breaks z.object().strict() API\" --category gotcha --tag zod,typescript"
-```
-
-**Flags** (capture mode):
-- `--category <name>` — `pattern|antipattern|decision|tool|gotcha|technique`. Default: inferred from text keywords.
-- `--tag t1,t2` — Comma-separated tags. Always adds `manual` implicitly.
-- `--phase <N>` — Override auto-detected current phase. `--phase 0` forces no phase link.
-- `--confidence high|medium|low` — Default: medium.
-
-**Flags** (list/search mode):
-- `--tag t1,t2` — Filter by tag
-- `--category <name>` — Filter by category
-- `--phase <N>` — Filter by phase
-- `--lens <name>` — Filter by retrospective lens (technical|process|quality|decision)
-- `--limit <N>` — Row limit (default 20)
-
-**Storage**:
-- `.workflow/specs/learnings.md` — append-only store (shared with `quality-retrospective`)
-- Index auto-maintained by WikiIndexer (no manual index file needed)
-</context>
-
-<invariants>
-1. **No LLM or CLI calls**: This skill is pure file I/O — parse, infer, append, confirm. No `exec_command`, no `spawn_agent`.
-2. **Bootstrap on demand**: Create `.workflow/knowhow/` structure on first use; do not require it to exist.
-3. **Append-only learnings.md**: Never rewrite or delete existing entries.
-4. **Stable INS-ids**: `INS-{8hex}` from `hash(insightText + timestamp)` — same text at different times gets different ids.
-5. **Source field**: Always `"manual"` for captures from this skill; `"retrospective"` is reserved for `quality-retrospective`.
-6. **Phase auto-link**: Read `state.json` automatically; `--phase 0` is the only way to force null.
-7. **Keyword inference is approximate**: When in doubt, default to `pattern` category rather than prompting user.
-</invariants>
-
-<execution>
-
-### Step 1: Parse Mode and Validate Arguments
-
-Parse the first non-flag token from `$ARGUMENTS`:
-
-| First token | Mode |
-|-------------|------|
-| `list` | list |
-| `search` followed by query | search |
-| `show` followed by INS-id | show |
-| Empty | Prompt with `functions.request_user_input` |
-| Any other text (quoted or not) | capture |
-
-Validate `--category` if provided (allowed: pattern, antipattern, decision, tool, gotcha, technique). E002 if unknown.
-
-### Step 2: Bootstrap Learning Store (on first use)
-
-Verify `.workflow/` exists (E001 if not). If `.workflow/specs/learnings.md` missing: create `.workflow/specs/` directory and empty `learnings.md` with header.
-
-### Step 3: Execute Mode
-
-#### Capture Mode
-
-1. **Infer category** from keywords (no LLM):
-
-| Keywords | Category |
-|----------|----------|
-| always, should, prefer, best practice | pattern |
-| never, avoid, don't, pitfall, breaks | antipattern |
-| decided, chose, tradeoff, because | decision |
-| tool, library, framework, package | tool |
-| gotcha, surprising, unexpected | gotcha |
-| technique, approach, method | technique |
-
-2. **Auto-link phase** from `state.json` artifact registry. `--phase 0` forces null.
-3. **Generate INS-id**: `INS-{8 hex}` from `hash(insightText + timestamp)`.
-4. **Build row** with fields: id, title (first 80 chars), summary, source="manual", lens=null, category, tags (includes "manual"), phase, phase_slug, confidence, routed_to=null, created_at.
-5. **Append** entry to `.workflow/specs/learnings.md` (append-only, never rewrite).
-6. WikiIndexer auto-indexes the new entry (no manual index update needed).
-
-#### List Mode
-
-Read `learnings.md` entries, apply filters (`--tag`, `--category`, `--phase`, `--lens`), sort newest-first, display up to `--limit` rows (default 20) as table.
-
-#### Search Mode
-
-Grep `learnings.md` for query. Rank by field weight: title (3) > tags (2) > summary (1). Display top matches.
-
-#### Show Mode
-
-Validate `INS-[0-9a-f]{8}` format. Find matching row, display full record. Show linked artifact if `routed_to` is set.
-
-### Step 4: Display Confirmation
-
-Capture mode: display ID, category, phase, confidence, tags, and next-step commands (`$manage-learn "list"`, `$manage-learn "search ..."`).
-</execution>
-
-<error_codes>
-| Code | Severity | Description | Stage |
-|------|----------|-------------|-------|
-| E001 | error | `.workflow/` not initialized — run `$maestro-init` first | parse_input |
-| E002 | error | Unknown `--category` value | parse_input |
-| E003 | error | `show` mode requires INS-id argument | show |
-| E004 | error | INS-id not found in learnings.md | show |
-| W001 | warning | Auto-phase detection: no matching artifact directory found; phase set to null | capture |
-| W002 | warning | Entry count differs from `learnings.md`; offer to rebuild index | list/search |
-</error_codes>
-
-<success_criteria>
-- [ ] Mode parsed correctly (capture, list, search, show)
-- [ ] Learning store bootstrapped on first use
-- [ ] Capture: category inferred from keywords, phase auto-linked, INS-id generated
-- [ ] Capture: entry appended to .workflow/specs/learnings.md (append-only)
-- [ ] List: filters applied, newest-first, respects --limit
-- [ ] Search: grep with weighted ranking across title/tags/summary
-- [ ] Show: full record displayed for valid INS-id
-- [ ] No LLM or CLI calls — pure file I/O only
-</success_criteria>
+---
+name: manage-learn
+description: Capture and search learning insights and tips
+argument-hint: "[\"<insight text>\"|list|search <query>|show <INS-id>] [--category pattern|antipattern|decision|tool|gotcha|technique] [--tag t1,t2] [--phase N] [--confidence high|medium|low]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+<purpose>
+Pure file-operation CRUD skill for the workflow knowhow library. No agent spawning, no CLI calls, no LLM inference — just parse-infer-append-confirm. Complements `quality-retrospective`: where retrospective extracts insights in bulk from completed phases, `manage-learn` captures one timeless insight at a time during active work. Both write to the same `.workflow/specs/learnings.md` store, disambiguated by `source` and `lens` fields.
+
+```
+Parse Mode  →  Bootstrap Store  →  Execute Mode  →  Confirm
+(capture /       (on first use)     (Bash/Read/      (INS-id
+  list /          Bash+Write)        Write/Grep)      + hints)
+  search /
+  show)
+```
+</purpose>
+
+<context>
+$ARGUMENTS — mode token followed by options.
+
+```bash
+$manage-learn "Always read state.json before planning to detect current phase"
+$manage-learn "list --limit 10 --category antipattern"
+$manage-learn "search context propagation"
+$manage-learn "show INS-a3f7b2c1"
+$manage-learn "\"Zod v4 breaks z.object().strict() API\" --category gotcha --tag zod,typescript"
+```
+
+**Flags** (capture mode):
+- `--category <name>` — `pattern|antipattern|decision|tool|gotcha|technique`. Default: inferred from text keywords.
+- `--tag t1,t2` — Comma-separated tags. Always adds `manual` implicitly.
+- `--phase <N>` — Override auto-detected current phase. `--phase 0` forces no phase link.
+- `--confidence high|medium|low` — Default: medium.
+
+**Flags** (list/search mode):
+- `--tag t1,t2` — Filter by tag
+- `--category <name>` — Filter by category
+- `--phase <N>` — Filter by phase
+- `--lens <name>` — Filter by retrospective lens (technical|process|quality|decision)
+- `--limit <N>` — Row limit (default 20)
+
+**Storage**:
+- `.workflow/specs/learnings.md` — append-only store (shared with `quality-retrospective`)
+- Index auto-maintained by WikiIndexer (no manual index file needed)
+</context>
+
+<invariants>
+1. **No LLM or CLI calls**: This skill is pure file I/O — parse, infer, append, confirm. No `exec_command`, no `spawn_agent`.
+2. **Bootstrap on demand**: Create `.workflow/knowhow/` structure on first use; do not require it to exist.
+3. **Append-only learnings.md**: Never rewrite or delete existing entries.
+4. **Stable INS-ids**: `INS-{8hex}` from `hash(insightText + timestamp)` — same text at different times gets different ids.
+5. **Source field**: Always `"manual"` for captures from this skill; `"retrospective"` is reserved for `quality-retrospective`.
+6. **Phase auto-link**: Read `state.json` automatically; `--phase 0` is the only way to force null.
+7. **Keyword inference is approximate**: When in doubt, default to `pattern` category rather than prompting user.
+</invariants>
+
+<execution>
+
+### Step 1: Parse Mode and Validate Arguments
+
+Parse the first non-flag token from `$ARGUMENTS`:
+
+| First token | Mode |
+|-------------|------|
+| `list` | list |
+| `search` followed by query | search |
+| `show` followed by INS-id | show |
+| Empty | Prompt with `functions.request_user_input` |
+| Any other text (quoted or not) | capture |
+
+Validate `--category` if provided (allowed: pattern, antipattern, decision, tool, gotcha, technique). E002 if unknown.
+
+### Step 2: Bootstrap Learning Store (on first use)
+
+Verify `.workflow/` exists (E001 if not). If `.workflow/specs/learnings.md` missing: create `.workflow/specs/` directory and empty `learnings.md` with header.
+
+### Step 3: Execute Mode
+
+#### Capture Mode
+
+1. **Infer category** from keywords (no LLM):
+
+| Keywords | Category |
+|----------|----------|
+| always, should, prefer, best practice | pattern |
+| never, avoid, don't, pitfall, breaks | antipattern |
+| decided, chose, tradeoff, because | decision |
+| tool, library, framework, package | tool |
+| gotcha, surprising, unexpected | gotcha |
+| technique, approach, method | technique |
+
+2. **Auto-link phase** from `state.json` artifact registry. `--phase 0` forces null.
+3. **Generate INS-id**: `INS-{8 hex}` from `hash(insightText + timestamp)`.
+4. **Build row** with fields: id, title (first 80 chars), summary, source="manual", lens=null, category, tags (includes "manual"), phase, phase_slug, confidence, routed_to=null, created_at.
+5. **Append** entry to `.workflow/specs/learnings.md` (append-only, never rewrite).
+6. WikiIndexer auto-indexes the new entry (no manual index update needed).
+
+#### List Mode
+
+Read `learnings.md` entries, apply filters (`--tag`, `--category`, `--phase`, `--lens`), sort newest-first, display up to `--limit` rows (default 20) as table.
+
+#### Search Mode
+
+Grep `learnings.md` for query. Rank by field weight: title (3) > tags (2) > summary (1). Display top matches.
+
+#### Show Mode
+
+Validate `INS-[0-9a-f]{8}` format. Find matching row, display full record. Show linked artifact if `routed_to` is set.
+
+### Step 4: Display Confirmation
+
+Capture mode: display ID, category, phase, confidence, tags, and next-step commands (`$manage-learn "list"`, `$manage-learn "search ..."`).
+</execution>
+
+<error_codes>
+| Code | Severity | Description | Stage |
+|------|----------|-------------|-------|
+| E001 | error | `.workflow/` not initialized — run `$maestro-init` first | parse_input |
+| E002 | error | Unknown `--category` value | parse_input |
+| E003 | error | `show` mode requires INS-id argument | show |
+| E004 | error | INS-id not found in learnings.md | show |
+| W001 | warning | Auto-phase detection: no matching artifact directory found; phase set to null | capture |
+| W002 | warning | Entry count differs from `learnings.md`; offer to rebuild index | list/search |
+</error_codes>
+
+<success_criteria>
+- [ ] Mode parsed correctly (capture, list, search, show)
+- [ ] Learning store bootstrapped on first use
+- [ ] Capture: category inferred from keywords, phase auto-linked, INS-id generated
+- [ ] Capture: entry appended to .workflow/specs/learnings.md (append-only)
+- [ ] List: filters applied, newest-first, respects --limit
+- [ ] Search: grep with weighted ranking across title/tags/summary
+- [ ] Show: full record displayed for valid INS-id
+- [ ] No LLM or CLI calls — pure file I/O only
+</success_criteria>

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

@@ -1,75 +1,75 @@
----
-name: manage-status
-description: Show project dashboard with progress and next steps
-argument-hint: ""
-allowed-tools: Read, Bash, Glob, Grep
----
-
-<purpose>
-Display project dashboard with phase progress, active tasks, and suggested next steps. Reads `.workflow/` state files and renders a formatted project overview. No arguments required.
-</purpose>
-
-<context>
-$ARGUMENTS — none required.
-
-```bash
-$manage-status
-```
-
-Reads from:
-- `.workflow/state.json` — project-level state machine
-- `.workflow/roadmap.md` — milestone and phase structure
-- `.workflow/scratch/*/index.json` — per-phase metadata and progress (resolved via state.json artifact registry)
-- `.workflow/scratch/*/.task/TASK-*.json` — individual task statuses (resolved via state.json artifact registry)
-- `.workflow/wiki-index.json` — unified wiki graph index (entry counts, health)
-</context>
-
-<execution>
-
-### Step 1: Validate Project
-
-Verify `.workflow/` exists (E001) and `state.json` is present (E002).
-
-### Step 2: Load State Files
-
-Read: `state.json`, `roadmap.md`, per-phase `scratch/*/index.json`, task files `scratch/*/.task/TASK-*.json` (all resolved via artifact registry).
-
-### Step 3: Calculate Progress
-
-For each phase directory found:
-1. Count total tasks, completed, failed, blocked, pending
-2. Calculate completion percentage
-3. Determine phase status from index.json
-
-### Step 4: Render Dashboard
-
-Display sections: **Milestones & Phases** (per-phase status, progress bars, completion %), **Active Work** (in-progress and blocked tasks), **Knowledge Graph** (wiki entry counts by type, health score, orphans), **Next Steps** (state-based suggestion).
-
-### Step 5: Suggest Next Steps
-
-Use this decision table to suggest the next action:
-
-| Current State | Suggestion |
-|---------------|------------|
-| No phases planned | `$maestro-brainstorm` or `$maestro-plan` |
-| Phase planned, not executed | `$maestro-execute "<N>"` |
-| Phase executed, not reviewed | `$quality-review "<N>"` |
-| Phase reviewed PASS/WARN | `$quality-test "<N>"` |
-| UAT passed | `$maestro-milestone-audit` |
-| All milestone phases done | `$maestro-milestone-audit` |
-</execution>
-
-<error_codes>
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | fatal | `.workflow/` not initialized -- run `$maestro-init` first |
-| E002 | fatal | `state.json` missing or corrupt |
-</error_codes>
-
-<success_criteria>
-- [ ] `.workflow/` and `state.json` validated
-- [ ] All state sources loaded (state.json, roadmap, phase indexes, task files)
-- [ ] Progress calculated per phase (total, completed, failed, blocked, pending, percentage)
-- [ ] Dashboard rendered with milestones, phases, active work, and next steps
-- [ ] Next step suggestion matches current project state via decision table
-</success_criteria>
+---
+name: manage-status
+description: Show project dashboard with progress and next steps
+argument-hint: ""
+allowed-tools: Read, Bash, Glob, Grep
+---
+
+<purpose>
+Display project dashboard with phase progress, active tasks, and suggested next steps. Reads `.workflow/` state files and renders a formatted project overview. No arguments required.
+</purpose>
+
+<context>
+$ARGUMENTS — none required.
+
+```bash
+$manage-status
+```
+
+Reads from:
+- `.workflow/state.json` — project-level state machine
+- `.workflow/roadmap.md` — milestone and phase structure
+- `.workflow/scratch/*/index.json` — per-phase metadata and progress (resolved via state.json artifact registry)
+- `.workflow/scratch/*/.task/TASK-*.json` — individual task statuses (resolved via state.json artifact registry)
+- `.workflow/wiki-index.json` — unified wiki graph index (entry counts, health)
+</context>
+
+<execution>
+
+### Step 1: Validate Project
+
+Verify `.workflow/` exists (E001) and `state.json` is present (E002).
+
+### Step 2: Load State Files
+
+Read: `state.json`, `roadmap.md`, per-phase `scratch/*/index.json`, task files `scratch/*/.task/TASK-*.json` (all resolved via artifact registry).
+
+### Step 3: Calculate Progress
+
+For each phase directory found:
+1. Count total tasks, completed, failed, blocked, pending
+2. Calculate completion percentage
+3. Determine phase status from index.json
+
+### Step 4: Render Dashboard
+
+Display sections: **Milestones & Phases** (per-phase status, progress bars, completion %), **Active Work** (in-progress and blocked tasks), **Knowledge Graph** (wiki entry counts by type, health score, orphans), **Next Steps** (state-based suggestion).
+
+### Step 5: Suggest Next Steps
+
+Use this decision table to suggest the next action:
+
+| Current State | Suggestion |
+|---------------|------------|
+| No phases planned | `$maestro-brainstorm` or `$maestro-plan` |
+| Phase planned, not executed | `$maestro-execute "<N>"` |
+| Phase executed, not reviewed | `$quality-review "<N>"` |
+| Phase reviewed PASS/WARN | `$quality-test "<N>"` |
+| UAT passed | `$maestro-milestone-audit` |
+| All milestone phases done | `$maestro-milestone-audit` |
+</execution>
+
+<error_codes>
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | fatal | `.workflow/` not initialized -- run `$maestro-init` first |
+| E002 | fatal | `state.json` missing or corrupt |
+</error_codes>
+
+<success_criteria>
+- [ ] `.workflow/` and `state.json` validated
+- [ ] All state sources loaded (state.json, roadmap, phase indexes, task files)
+- [ ] Progress calculated per phase (total, completed, failed, blocked, pending, percentage)
+- [ ] Dashboard rendered with milestones, phases, active work, and next steps
+- [ ] Next step suggestion matches current project state via decision table
+</success_criteria>

package/.codex/skills/odyssey-debug/SKILL.md

@@ -119,8 +119,8 @@ When `flags[skip_when] == true` → auto set `status: "skipped"`, `completion_co
 |------|------|------|
 | Codebase docs | Read `.workflow/codebase/ARCHITECTURE.md` | 模块边界 |
 | Wiki search | `maestro search "<issue keywords>" --json` | 先前调查（top 5） |
-| Specs + tools | `maestro spec load --category debug --keyword "<symptom>"` | 已知 issue/workaround |
-| Role knowledge | `maestro search --category debug` → 选相关 → `maestro wiki load <id>` | 领域知识 |
+| Specs + tools | `maestro load --type spec --category debug --keyword "<symptom>"` | 已知 issue/workaround |
+| Role knowledge | `maestro search --category debug` → 选相关 → `maestro load --type knowhow --id <id>` | 领域知识 |
 | Prior sessions | `Glob(".workflow/scratch/*-debug-odyssey-*")` | 相关会话 |
 
 ### Knowledge Persistence（S_RECORD 中写入产出文件）

package/.codex/skills/odyssey-improve/SKILL.md

@@ -130,9 +130,9 @@ Lifecycle: `pending -> done | skipped | failed` (all set `completion_confirmed`)
 |-------|---------|---------|
 | Codebase docs | Read `.workflow/codebase/ARCHITECTURE.md` | Module boundaries |
 | Wiki search | `maestro search "<target keywords>" --json` | Prior investigations (top 5) |
-| Specs | `maestro spec load --category coding --keyword "<target>"` | Coding conventions |
-| Debug specs | `maestro spec load --category debug` | Known issues, workarounds |
-| Role knowledge | `maestro search --category arch` -> select -> `maestro wiki load <id>` | Domain knowledge |
+| Specs | `maestro load --type spec --category coding --keyword "<target>"` | Coding conventions |
+| Debug specs | `maestro load --type spec --category debug` | Known issues, workarounds |
+| Role knowledge | `maestro search --category arch` -> select -> `maestro load --type knowhow --id <id>` | Domain knowledge |
 | Prior sessions | `Glob(".workflow/scratch/*-improve-odyssey-*")` | Related sessions |
 
 ### Knowledge Persistence (two-step model)