pi-maestro-flow 0.2.0 → 0.3.1

package/skills/maestro-universal-workflow/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: maestro-universal-workflow
 description: "Dynamic adversarial workflow generator — scan library, match or generate, execute, persist Arguments: <intent> [--name <slug>] [--depth shallow|standard|deep] [--dry-run] [--from <script>] [--resume <runId>]"
-allowed-tools: Read Write Edit Bash Glob Grep Workflow AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep Workflow maestro
 ---
 
 <purpose>
 Dynamic workflow generator: scan library for matches or generate task-specific Workflow scripts
-on-the-fly with adversarial patterns. Scripts persist at `~/.maestro/workflows/dynamic/uwf-*.js`.
+on-the-fly with adversarial patterns. Scripts persist at `~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-*.js`.
 </purpose>
 
 <context>
@@ -23,10 +23,10 @@ Remaining         → intent
 ```
 
 **Library locations:**
-- Fixed scripts: `~/.maestro/workflows/swarm/wf-*.js`
-- Dynamic scripts: `~/.maestro/workflows/dynamic/uwf-*.js`
+- Fixed scripts: `~/.pi/agent/packages/pi-maestro-flow/workflows/swarm/wf-*.js`
+- Dynamic scripts: `~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-*.js`
 
-**Output boundary**: ALL file writes MUST target `~/.maestro/workflows/dynamic/` (generated scripts) and `.workflow/scratch/{YYYYMMDD}-uwf-*/` (execution results). Fixed scripts at `~/.maestro/workflows/swarm/` are read-only. NEVER modify source code or `.claude/commands/` files.
+**Output boundary**: ALL file writes MUST target `~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/` (generated scripts) and `.workflow/scratch/{YYYYMMDD}-uwf-*/` (execution results). Fixed scripts at `~/.pi/agent/packages/pi-maestro-flow/workflows/swarm/` are read-only. NEVER modify source code or `.claude/commands/` files.
 </context>
 
 <state_machine>
@@ -94,10 +94,10 @@ S_PERSIST:
 
 扫描两个目录，读取每个 `.js` 文件的 `meta` 块提取 `name`、`description`、`whenToUse`：
 
-1. **Fixed scripts**: 展开 `~/.maestro/workflows/swarm/wf-*.js` 为绝对路径
+1. **Fixed scripts**: 展开 `~/.pi/agent/packages/pi-maestro-flow/workflows/swarm/wf-*.js` 为绝对路径
    - Glob 查找所有匹配文件
    - 读取每个文件前 10 行，提取 `meta.name`、`meta.description`、`meta.whenToUse`
-2. **Dynamic scripts**: 展开 `~/.maestro/workflows/dynamic/uwf-*.js`
+2. **Dynamic scripts**: 展开 `~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-*.js`
    - 同上
 3. **匹配评分**：对每个脚本，评估其 description/whenToUse 与 intent 的语义相关度
 4. **输出**：
@@ -105,7 +105,7 @@ S_PERSIST:
    - 每个列出：name、description、scriptPath、匹配理由
    - 无匹配则直接跳 S_DESIGN
 
-若有匹配，用 AskUserQuestion 让用户选择：
+若有匹配，用 user prompt 让用户选择：
 - 选项 1-3: 使用现有脚本（附 preview 显示脚本 meta）
 - 最后选项: "生成全新脚本"
 
@@ -265,7 +265,7 @@ const path = 'C:/Users/project/src'  // 或直接不在脚本中硬编码路径
 
 ```
 Write({
-  file_path: expandPath('~/.maestro/workflows/dynamic/uwf-{slug}.js'),
+  file_path: expandPath('~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-{slug}.js'),
   content: generatedScript
 })
 ```
@@ -286,7 +286,7 @@ Bash({ command: 'node --check "path/to/uwf-{slug}.js"' })
 
 ### A_CONFIRM_EXECUTE
 
-Use `AskUserQuestion` to confirm before executing the generated or selected script:
+Use `user prompt` to confirm before executing the generated or selected script:
 
 ```
 question: "脚本已就绪，是否执行？"
@@ -307,7 +307,7 @@ User confirms → S_EXECUTE; user declines → S_PERSIST (save only); user cance
 
 ```
 Workflow({
-  scriptPath: expandPath('~/.maestro/workflows/dynamic/uwf-{slug}.js'),
+  scriptPath: expandPath('~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-{slug}.js'),
   args: taskSpecificArgs,   // 从 intent 推断
   resumeFromRunId: resumeId // 若有
 })
@@ -317,12 +317,12 @@ Workflow({
 
 ### A_PERSIST_SCRIPT
 
-脚本已在 A_GENERATE_SCRIPT Step 2 写入 `~/.maestro/workflows/dynamic/uwf-{slug}.js`。
+脚本已在 A_GENERATE_SCRIPT Step 2 写入 `~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-{slug}.js`。
 
 1. 确认文件存在（Glob 检查）
 2. 展示保存路径和使用方式：
    ```
-   Saved: ~/.maestro/workflows/dynamic/uwf-{slug}.js
+   Saved: ~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-{slug}.js
    Reuse: /maestro-universal-workflow --from uwf-{slug} "{new intent}"
    Resume: /maestro-universal-workflow --resume {runId}
    Via swarm: /maestro-swarm-workflow --script uwf-{slug}
@@ -522,7 +522,7 @@ Findings: ${digest}
 - BLOCKED if: task cannot be decomposed (E002).
 
 **GATE 4: Generate → Execute**
-- REQUIRED: Script written to `~/.maestro/workflows/dynamic/uwf-{slug}.js`.
+- REQUIRED: Script written to `~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-{slug}.js`.
 - REQUIRED: `node --check` syntax validation passed.
 - REQUIRED: User confirmation via AskUserQuestion (unless resuming).
 - BLOCKED if: syntax validation fails after 2 retries (E003).
@@ -617,6 +617,6 @@ universal-workflow 扫描时会同时检查 swarm/ 和 dynamic/ 目录，
 - [ ] `node --check` syntax validation passed
 - [ ] User confirmation obtained before execution (unless --resume)
 - [ ] Workflow executed via scriptPath (not inline script string)
-- [ ] Script persisted to `~/.maestro/workflows/dynamic/uwf-{slug}.js`
+- [ ] Script persisted to `~/.pi/agent/packages/pi-maestro-flow/workflows/dynamic/uwf-{slug}.js`
 - [ ] Completion summary displayed with reuse/resume commands
 </success_criteria>

package/skills/maestro-update/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: maestro-update
 description: "Detect version, preview changes, apply workflow upgrades Arguments: [--dry-run] [--force] [--setup-only]"
-allowed-tools: Read Write Edit Bash Glob Grep AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep maestro
 ---
 
 <purpose>
 Detect current version, run schema migration to latest, then follow the version-specific upgrade workflow.
-Schema migrations are handled by `maestro update --migrate`; workflow docs (`~/.maestro/workflows/updates/`) handle setup.
+Schema migrations are handled by `maestro update --migrate`; workflow docs (`~/.pi/agent/packages/pi-maestro-flow/workflows/updates/`) handle setup.
 </purpose>
 
 <context>
@@ -19,7 +19,7 @@ $ARGUMENTS — optional flags.
 
 **Version source:** `.workflow/state.json` → `version` field
 
-**Workflow docs:** `~/.maestro/workflows/updates/`
+**Workflow docs:** `~/.pi/agent/packages/pi-maestro-flow/workflows/updates/`
 - `update-v{TO}-setup.md` — post-migration setup for version {TO}
 
 **Schema registry:** `maestro update --migrate` — handles all intermediate version bumps automatically
@@ -30,7 +30,7 @@ $ARGUMENTS — optional flags.
 <invariants>
 1. **Backup before migration** — a timestamped backup of `.workflow/state.json` MUST be created before any schema migration runs; NEVER execute migration without backup
 2. **Idempotent** — running update when already on latest version MUST be a no-op (display "up to date"); NEVER re-apply migrations
-3. **Confirmation before execute** — migration diff MUST be displayed and user MUST confirm via AskUserQuestion before execution (unless `--force`); NEVER silently apply schema changes
+3. **Confirmation before execute** — migration diff MUST be displayed and user MUST confirm via user prompt before execution (unless `--force`); NEVER silently apply schema changes
 4. **Migration diff always visible** — even with `--force`, the migration diff MUST be displayed for audit visibility; NEVER skip diff display
 5. **Restore path on failure** — if migration fails, the backup restore command MUST be displayed; NEVER leave user without recovery instructions
 6. **Sequential migration** — all intermediate version steps MUST be applied in order by the schema registry; NEVER skip intermediate versions
@@ -65,7 +65,7 @@ $ARGUMENTS — optional flags.
 ```
 
 IF `--setup-only`:
-  → Glob: ~/.maestro/workflows/updates/update-v{version}-setup.md
+  → Glob: ~/.pi/agent/packages/pi-maestro-flow/workflows/updates/update-v{version}-setup.md
   → IF exists: follow that document completely, then EXIT
   → IF not exists: display "No setup script for v{version}" → EXIT
 
@@ -76,8 +76,8 @@ IF `--setup-only`:
 2. Parse JSON output
 3. IF status = "up-to-date":
      Display "Already up to date (v{version})"
-     → Glob: ~/.maestro/workflows/updates/update-v{version}-setup.md
-     → IF exists: AskUserQuestion "Run setup for v{version}?" → load and follow
+     → Glob: ~/.pi/agent/packages/pi-maestro-flow/workflows/updates/update-v{version}-setup.md
+     → IF exists: user prompt "Run setup for v{version}?" → load and follow
      → EXIT
 
 4. Display target:
@@ -94,7 +94,7 @@ IF `--dry-run` → display info and EXIT.
    Show schema changes that will be applied.
 
 2. Confirm (unless --force):
-   AskUserQuestion: "Upgrade v{current} → v{target}?"
+   user prompt: "Upgrade v{current} → v{target}?"
    Options: [执行 / 取消]
 
 3. Create backup:
@@ -107,7 +107,7 @@ IF `--dry-run` → display info and EXIT.
 5. IF failed → display backup restore command → EXIT
 
 6. Load version-specific setup:
-   Read: ~/.maestro/workflows/updates/update-v{target}-setup.md
+   Read: ~/.pi/agent/packages/pi-maestro-flow/workflows/updates/update-v{target}-setup.md
    IF exists → follow completely (hooks, deps, knowledge system config)
 
 7. Display: "v{current} → v{target}: done"
@@ -132,7 +132,7 @@ Next steps:
 |------|----------|-----------|----------|
 | E001 | error | `.workflow/state.json` not found or unreadable | Run `/maestro-init` first |
 | E002 | error | Schema migration failed (npx tsx returned error) | Display backup restore command: `cp .workflow/state.json.backup-* .workflow/state.json` |
-| E003 | error | Version-specific setup doc failed to execute | Manual setup: read `~/.maestro/workflows/updates/update-v{target}-setup.md` |
+| E003 | error | Version-specific setup doc failed to execute | Manual setup: read `~/.pi/agent/packages/pi-maestro-flow/workflows/updates/update-v{target}-setup.md` |
 | W001 | warning | No version-specific setup doc found for target version | Proceed without setup; schema migration alone is sufficient |
 | W002 | warning | `--setup-only` but no setup script exists for current version | Display message and exit |
 </error_codes>

package/skills/manage-codebase-rebuild/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-codebase-rebuild
 description: "Rebuild all codebase documentation from scratch Arguments: [--focus <area>] [--force] [--skip-commit]"
-allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep teammate maestro
 ---
 
 <purpose>
@@ -9,7 +9,7 @@ Full rebuild of `.workflow/codebase/` docs: 4 parallel mapper agents → tech-st
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/codebase-rebuild.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/codebase-rebuild.md
 </required_reading>
 
 <context>
@@ -20,7 +20,7 @@ $ARGUMENTS -- optional flags.
 - `--force` -- Skip confirmation prompt and proceed directly
 - `--skip-commit` -- Do not auto-commit after rebuild
 
-**Confirmation gate:** Unless `--force` is set, prompt the user (AskUserQuestion) before executing git commit. Show the list of changed files and proposed commit message. If `--skip-commit` is set, skip the commit entirely.
+**Confirmation gate:** Unless `--force` is set, prompt the user (user prompt) before executing git commit. Show the list of changed files and proposed commit message. If `--skip-commit` is set, skip the commit entirely.
 
 **Mapper agent assignments (when `--focus` omitted):**
 | Agent | Focus | Output file |
@@ -49,7 +49,7 @@ $ARGUMENTS -- optional flags.
 </invariants>
 
 <execution>
-Follow '~/.maestro/workflows/codebase-rebuild.md' completely.
+Follow '~/.pi/agent/packages/pi-maestro-flow/workflows/codebase-rebuild.md' completely.
 
 **When `--focus <area>` is set:** pass the area string to each mapper agent as scoping context; only regenerate the docs relevant to that scope (leave others untouched unless missing).
 

package/skills/manage-drift-realign/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-drift-realign
 description: "Detect and realign .workflow/ artifact drift against code reality after refactoring Arguments: [--scope <roadmap|spec|codebase|state|issue|knowhow|project|all>] [--since YYYY-MM-DD|commit|HEAD~N] [--depth shallow|deep] [--dry-run] [--report] [--auto-archive] [--interactive]"
-allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep teammate maestro
 ---
 
 <purpose>
@@ -9,13 +9,13 @@ allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/drift-realign.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/drift-realign.md
 </required_reading>
 
 <deferred_reading>
-- ~/.maestro/workflows/knowledge-audit.md (交叉引用已有审计发现)
-- ~/.maestro/workflows/sync.md (codebase 文档严重漂移时自动触发)
-- ~/.maestro/workflows/codebase-rebuild.md (sync 不足时的回退方案)
+- ~/.pi/agent/packages/pi-maestro-flow/workflows/knowledge-audit.md (交叉引用已有审计发现)
+- ~/.pi/agent/packages/pi-maestro-flow/workflows/sync.md (codebase 文档严重漂移时自动触发)
+- ~/.pi/agent/packages/pi-maestro-flow/workflows/codebase-rebuild.md (sync 不足时的回退方案)
 </deferred_reading>
 
 <context>
@@ -65,7 +65,7 @@ Arguments: $ARGUMENTS
 </invariants>
 
 <execution>
-Follow `~/.maestro/workflows/drift-realign.md` Stages 1-9 in order.
+Follow `~/.pi/agent/packages/pi-maestro-flow/workflows/drift-realign.md` Stages 1-9 in order.
 
 ### Phase Gates (MANDATORY, BLOCKING)
 
@@ -100,7 +100,7 @@ Follow `~/.maestro/workflows/drift-realign.md` Stages 1-9 in order.
 
 ### Platform Inquiry（Stage 2a，交互式）
 
-当 `session_summary.by_platform` 包含多个平台且 session 总量 > 20 时，使用 AskUserQuestion 询问用户修改主要在哪个平台进行。用户选择后以 `--platform` 参数重新获取 timeline，缩小后续分析范围。
+当 `session_summary.by_platform` 包含多个平台且 session 总量 > 20 时，使用 user prompt 询问用户修改主要在哪个平台进行。用户选择后以 `--platform` 参数重新获取 timeline，缩小后续分析范围。
 
 ### Session 详情加载策略（Stage 2b）
 

package/skills/manage-harvest/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-harvest
 description: "Extract knowledge from artifacts into wiki/spec/issues Arguments: [<session-id|path>] [--to wiki|spec|issue|auto] [--source <type>] [--recent N] [--dry-run] [-y]"
-allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep teammate maestro
 ---
 
 <purpose>
@@ -9,12 +9,12 @@ Extract knowledge from workflow artifacts → route to wiki/spec/issue stores. W
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/harvest.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/harvest.md
 </required_reading>
 
 <deferred_reading>
-- @~/.maestro/workflows/issue.md (issues.jsonl schema for issue routing — read when creating issues in Stage 6c)
-- @~/.maestro/workflows/specs-add.md (spec entry format — read when routing to spec in Stage 6b)
+- ~/.pi/agent/packages/pi-maestro-flow/workflows/issue.md (issues.jsonl schema for issue routing — read when creating issues in Stage 6c)
+- ~/.pi/agent/packages/pi-maestro-flow/workflows/specs-add.md (spec entry format — read when routing to spec in Stage 6b)
 </deferred_reading>
 
 <context>
@@ -44,7 +44,7 @@ Additional flags, source registry (scan paths), and storage locations defined in
 </invariants>
 
 <execution>
-Follow '~/.maestro/workflows/harvest.md' Stages 1-8 in order.
+Follow '~/.pi/agent/packages/pi-maestro-flow/workflows/harvest.md' Stages 1-8 in order.
 
 ### Phase Gates (MANDATORY, BLOCKING)
 

package/skills/manage-issue/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-issue
 description: "Create, query, update, close, and link issues Arguments: <subcommand: create|list|status|update|close|link> [--title text] [--severity S] [--status S] [--resolution text]"
-allowed-tools: Read Write Edit Bash Glob Grep AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep maestro
 ---
 
 <purpose>
@@ -9,11 +9,11 @@ Issue lifecycle management: create, list, status, update, close, link. Stored in
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/issue.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/issue.md
 </required_reading>
 
 <deferred_reading>
-- [issue.json template](~/.maestro/templates/issue.json) — read when creating or updating issue records (create, update, close)
+- [issue.json template](~/.pi/agent/packages/pi-maestro-flow/templates/issue.json) — read when creating or updating issue records (create, update, close)
 </deferred_reading>
 
 <context>
@@ -45,7 +45,7 @@ $ARGUMENTS -- subcommand + options. Parse first token as subcommand.
 
 <execution>
 Parse subcommand from first token of $ARGUMENTS.
-Follow '~/.maestro/workflows/issue.md' completely.
+Follow '~/.pi/agent/packages/pi-maestro-flow/workflows/issue.md' completely.
 
 ### Phase Gates (MANDATORY, BLOCKING)
 

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

@@ -1,7 +1,7 @@
 ---
 name: manage-issue-discover
 description: "Discover issues via multi-perspective analysis Arguments: [multi-perspective | by-prompt <prompt>] [-y] [--scope <glob>] [--depth standard|deep]"
-allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep teammate maestro
 ---
 
 <purpose>
@@ -9,19 +9,19 @@ Automated issue discovery: multi-perspective (8 perspectives) or prompt-driven.
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/issue-discover.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/issue-discover.md
 </required_reading>
 
 <deferred_reading>
-- [issue.json template](~/.maestro/templates/issue.json) — read when creating issue records from findings (Step 6/11)
-- [search-tools](~/.maestro/templates/search-tools.md) — search tool priority, passed to agents via workflow
+- [issue.json template](~/.pi/agent/packages/pi-maestro-flow/templates/issue.json) — read when creating issue records from findings (Step 6/11)
+- [search-tools](~/.pi/agent/packages/pi-maestro-flow/templates/search-tools.md) — search tool priority, passed to agents via workflow
 </deferred_reading>
 
 <context>
 $ARGUMENTS -- optional. Parse first token to determine mode.
 
 **Modes:**
-- _(empty)_ -- interactive mode selection (AskUserQuestion)
+- _(empty)_ -- interactive mode selection (user prompt)
 - `multi-perspective` -- 8-perspective parallel agent scan
 - `by-prompt "..."` -- prompt-driven iterative agent exploration (CLI-planned)
 
@@ -52,11 +52,11 @@ $ARGUMENTS -- optional. Parse first token to determine mode.
 
 <execution>
 Determine mode from $ARGUMENTS:
-- No arguments or empty → interactive selection via AskUserQuestion
+- No arguments or empty → interactive selection via user prompt
 - First token is `multi-perspective` → multi-perspective mode
 - First token is `by-prompt` → prompt-driven mode, remaining tokens are the user prompt
 
-Follow '~/.maestro/workflows/issue-discover.md' completely.
+Follow '~/.pi/agent/packages/pi-maestro-flow/workflows/issue-discover.md' completely.
 
 ### Phase Gates (MANDATORY, BLOCKING)
 

package/skills/manage-kg-extractors/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-kg-extractors
 description: "Analyze codebase patterns and generate .workflow/kg/extractors.yaml for custom symbol extraction Arguments: [--scan-only] [--append] [--language <lang>] [--min-count <n>]"
-allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep teammate maestro
 ---
 
 <purpose>
@@ -89,7 +89,7 @@ Each agent returns: `[{pattern_type, regex_evidence, file_count, sample_matches:
 
 **GATE 2: Generation → Write** (Phase 2 → Phase 3)
 - REQUIRED: At least 1 pattern meets `--min-count` threshold.
-- REQUIRED: User confirmed pattern groups via AskUserQuestion.
+- REQUIRED: User confirmed pattern groups via user prompt.
 - BLOCKED if `--scan-only` is set — stop after summary.
 
 **GATE 3: Write → Validation** (Phase 3 → KG Index)
@@ -108,7 +108,7 @@ For each discovered pattern with ≥3 occurrences:
 ### Phase 3: Validate & write
 
 1. Show discovered patterns summary to user
-2. AskUserQuestion: confirm/edit/skip each pattern group
+2. user prompt: confirm/edit/skip each pattern group
 3. Write `.workflow/kg/extractors.yaml`
 4. Run `maestro kg index` to verify new symbols are extracted
 

package/skills/manage-knowhow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-knowhow
 description: "Manage knowhow entries (workflow and system) Arguments: <subcommand: list|search|view|edit|delete|prune> [query|id] [--store workflow|system|all] [--tag <tag>] [--type compact|tip]"
-allowed-tools: Read Write Edit Bash Glob Grep AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep maestro
 ---
 
 <purpose>
@@ -9,7 +9,7 @@ Manage knowhow across two stores: workflow (`.workflow/knowhow/`) and system mem
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/knowhow.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/knowhow.md
 </required_reading>
 
 <context>
@@ -38,7 +38,7 @@ Dual store architecture (paths, formats, index) defined in workflow knowhow.md.
 </context>
 
 <execution>
-Follow '~/.maestro/workflows/knowhow.md' Part A (KnowHow Management) completely.
+Follow '~/.pi/agent/packages/pi-maestro-flow/workflows/knowhow.md' Part A (KnowHow Management) completely.
 
 ### Phase Gates (MANDATORY, BLOCKING)
 

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

@@ -1,7 +1,7 @@
 ---
 name: manage-knowhow-capture
 description: "Capture reusable knowledge as templates, recipes, or tips Arguments: [<type>] [<description>] [--lang <lang>] [--source <url>] [--tag t1,t2]"
-allowed-tools: Read Write Edit Bash Glob Grep WebFetch AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep WebFetch maestro
 ---
 
 <purpose>
@@ -10,7 +10,7 @@ Auto-indexed by WikiIndexer (type=knowhow), searchable via `maestro search --typ
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/knowhow.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/knowhow.md
 </required_reading>
 
 <context>
@@ -50,12 +50,12 @@ $ARGUMENTS — type token + description + optional flags.
 </invariants>
 
 <execution>
-Follow '~/.maestro/workflows/knowhow.md' completely.
+Follow '~/.pi/agent/packages/pi-maestro-flow/workflows/knowhow.md' completely.
 
 ### Phase Gates (MANDATORY, BLOCKING)
 
 **GATE 1: Type Detection → Content Collection** (Type routing → Content extraction)
-- REQUIRED: Type detected from first token or selected via AskUserQuestion.
+- REQUIRED: Type detected from first token or selected via user prompt.
 - REQUIRED: Type maps to a valid prefix (KNW-/TPL-/RCP-/REF-/DCS-/TIP-/AST-/BLP-/DOC-/INS-).
 - BLOCKED if type unresolvable after interactive prompt.
 

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

@@ -1,7 +1,7 @@
 ---
 name: manage-knowledge-audit
 description: "Audit and prune knowledge across spec / knowhow / artifact stores Arguments: --scope <spec|knowhow|artifact|all> [--level P0|P1|P2] [--timeline T1..T6] [--since YYYY-MM-DD] [--milestone <name>] [--include-archive] [--interactive] [--mark|--delete|--purge] [--dry-run] [--report]"
-allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep teammate maestro
 ---
 
 <purpose>
@@ -9,12 +9,12 @@ allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/knowledge-audit.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/knowledge-audit.md
 </required_reading>
 
 <deferred_reading>
-- @~/.maestro/workflows/harvest.md (audit 检测的 artifact 是 harvest 的产物源)
-- @~/.maestro/workflows/specs-add.md (deprecate 操作所需的 `<spec-entry>` 变形)
+- ~/.pi/agent/packages/pi-maestro-flow/workflows/harvest.md (audit 检测的 artifact 是 harvest 的产物源)
+- ~/.pi/agent/packages/pi-maestro-flow/workflows/specs-add.md (deprecate 操作所需的 `<spec-entry>` 变形)
 </deferred_reading>
 
 <context>
@@ -43,7 +43,7 @@ Flag 全集、scope 对应的扫描路径、Stage 步骤、检测算法定义在
 </invariants>
 
 <execution>
-Follow `~/.maestro/workflows/knowledge-audit.md` Stages 1-8 in order.
+Follow `~/.pi/agent/packages/pi-maestro-flow/workflows/knowledge-audit.md` Stages 1-8 in order.
 
 ### Phase Gates (MANDATORY, BLOCKING)
 

package/skills/manage-status/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-status
 description: "Show project dashboard with progress and next steps Arguments: "
-allowed-tools: Read Bash Glob Grep
+allowed-tools: Read Bash Glob Grep maestro
 ---
 
 <purpose>
@@ -9,7 +9,7 @@ Project dashboard: artifact progress, task counts, active work, next-step sugges
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/status.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/status.md
 </required_reading>
 
 <context>
@@ -33,7 +33,7 @@ $ARGUMENTS (no arguments required)
 </invariants>
 
 <execution>
-Follow '~/.maestro/workflows/status.md' completely.
+Follow '~/.pi/agent/packages/pi-maestro-flow/workflows/status.md' completely.
 
 Next-step decision table defined in workflow status.md Step 5.
 

package/skills/manage-wiki/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: manage-wiki
 description: "Manage wiki graph — health, cleanup, search, stats Arguments: <subcommand: health|search|cleanup|stats|connect|digest> [query] [--fix] [--dry-run]"
-allowed-tools: Read Write Edit Bash Glob Grep AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep maestro
 ---
 
 <purpose>
@@ -9,7 +9,7 @@ Wiki graph management: health, search, cleanup, stats, connect, digest.
 </purpose>
 
 <required_reading>
-@~/.maestro/workflows/wiki-manage.md
+~/.pi/agent/packages/pi-maestro-flow/workflows/wiki-manage.md
 </required_reading>
 
 <context>
@@ -51,9 +51,9 @@ $ARGUMENTS — subcommand and optional flags.
 
 <execution>
 **Subcommand routing:**
-- `health|search|cleanup|stats` → Follow `~/.maestro/workflows/wiki-manage.md` completely.
-- `connect` → Follow `~/.maestro/workflows/wiki-connect.md` completely (Stages 1-6).
-- `digest` → Follow `~/.maestro/workflows/wiki-digest.md` completely (Stages 1-8).
+- `health|search|cleanup|stats` → Follow `~/.pi/agent/packages/pi-maestro-flow/workflows/wiki-manage.md` completely.
+- `connect` → Follow `~/.pi/agent/packages/pi-maestro-flow/workflows/wiki-connect.md` completely (Stages 1-6).
+- `digest` → Follow `~/.pi/agent/packages/pi-maestro-flow/workflows/wiki-digest.md` completely (Stages 1-8).
 
 ### Phase Gates (MANDATORY, BLOCKING)
 

package/skills/odyssey-debug/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: odyssey-debug
 description: "Long-running debug cycle — archaeology, diagnosis, fix, confirmation, generalization, discovery, and knowledge persistence Arguments: <issue> [--template <name>] [--skip-fix] [--skip-generalize] [--auto] [-y] [-c] [--heartbeat]"
-allowed-tools: Read Write Edit Bash Glob Grep Agent AskUserQuestion
+allowed-tools: Read Write Edit Bash Glob Grep teammate maestro
 ---
 
-<base>@~/.maestro/workflows/odyssey-base.md</base>
+<base>~/.pi/agent/packages/pi-maestro-flow/workflows/odyssey-base.md</base>
 
 <purpose>
 archaeology → explore → diagnose → fix & confirm → generalize → discover siblings → persist.
@@ -95,7 +95,7 @@ S_INTAKE → S_ARCHAEOLOGY → S_EXPLORE → S_DIAGNOSE → S_FIX → S_CONFIRM
 <transitions>
 S_INTAKE → S_INTAKE       : -c + session found → A_RESUME_SESSION
 S_INTAKE → S_ARCHAEOLOGY  : issue parsed → A_INTAKE
-S_INTAKE → S_INTAKE       : no issue, no session → AskUserQuestion
+S_INTAKE → S_INTAKE       : no issue, no session → user prompt
 
 S_ARCHAEOLOGY → S_EXPLORE     : complete
 S_EXPLORE     → S_DIAGNOSE    : complete
@@ -156,16 +156,16 @@ Write `explore.json` + evidence phase=explore. Update §3. Mark G2. Commit: `"od
 ### A_DIAGNOSE
 1. Hypotheses from evidence, ranked [HIGH]/[MEDIUM]/[LOW] → §4
 2. Test each → evidence phase=diagnosis
-3. Ambiguity → evidence phase=decision; Normal: AskUserQuestion | `-y`: defer
+3. Ambiguity → evidence phase=decision; Normal: user prompt | `-y`: defer
 4. Confirmed → `session.json.root_cause` + §5. Mark G1.
 
 Commit: `"odyssey-debug({slug}): DIAGNOSE — root cause confirmed"`
 
 ### A_ESCALATE_DIAGNOSIS
-`diagnosis_retries++`. < 3: `maestro delegate --role analyze`, new hypotheses, → S_DIAGNOSE. >= 3: Normal → AskUserQuestion | `-y` → INCONCLUSIVE → S_RECORD.
+`diagnosis_retries++`. < 3: `maestro delegate --role analyze`, new hypotheses, → S_DIAGNOSE. >= 3: Normal → user prompt | `-y` → INCONCLUSIVE → S_RECORD.
 
 ### A_FIX
-1. Present root cause + proposed fix. Normal: AskUserQuestion | `-y`: auto proceed
+1. Present root cause + proposed fix. Normal: user prompt | `-y`: auto proceed
 2. Implement fix, evidence phase=decision
 
 Commit: `"odyssey-debug({slug}): FIX — {summary}"`
@@ -238,7 +238,7 @@ Commit: `"odyssey-debug({slug}): GENERALIZE — pattern scan complete"`
    | risk + complex | Create issue |
    | safe | Skip with logged per-item reason |
 
-   Normal: AskUserQuestion per hit | `-y`: auto-fix bugs with fix_template, create issue for rest
+   Normal: user prompt per hit | `-y`: auto-fix bugs with fix_template, create issue for rest
 
 3. **Cross-phase loops:** `cross_phase_loops++` on fix/diagnose return. `loops >= max_loops` → must log per-item reasons.
 
@@ -254,12 +254,12 @@ Commit: `"odyssey-debug({slug}): DISCOVER — sibling triage complete"`
    - Architecture boundary violation → `/spec-add arch`
    - Reusable generalization pattern → `/spec-add coding`
 
-2. Mark G6 done. Pending decisions: Normal → AskUserQuestion | `-y` → skip (show deferred count).
+2. Mark G6 done. Pending decisions: Normal → user prompt | `-y` → skip (show deferred count).
 
 3. **Goal audit (hardened):**
    - `done` → confirmed
    - `skipped` → confirmed ONLY if corresponding `skip_when` flag is true
-   - **Hard rule:** G4 and G5 CANNOT be `skipped` unless `skip_generalize == true`. Pending without flag → `failed` (Normal: AskUserQuestion | `-y`: record `failed`)
+   - **Hard rule:** G4 and G5 CANNOT be `skipped` unless `skip_generalize == true`. Pending without flag → `failed` (Normal: user prompt | `-y`: record `failed`)
    - `phase_goals_all_done = true` only when all goals pass this audit
 
 4. `current_state = "COMPLETED"`, emit completion summary.
@@ -290,10 +290,10 @@ Commit: `"odyssey-debug({slug}): RECORD — summary and knowledge persistence"`
 
 | Decision Point | Normal | `-y` |
 |---------------|--------|------|
-| A_DIAGNOSE ambiguity | AskUserQuestion | deferred |
-| A_ESCALATE 3-strike | AskUserQuestion | INCONCLUSIVE |
-| A_FIX direction | AskUserQuestion | auto proceed |
-| A_DISCOVER hit routing | AskUserQuestion | auto-fix bugs with template, create issue for rest |
+| A_DIAGNOSE ambiguity | user prompt | deferred |
+| A_ESCALATE 3-strike | user prompt | INCONCLUSIVE |
+| A_FIX direction | user prompt | auto proceed |
+| A_DISCOVER hit routing | user prompt | auto-fix bugs with template, create issue for rest |
 
 ### Goal Prompt convergence rules