pi-maestro-flow 0.2.0 → 0.3.0

package/skills/team-coordinate/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-coordinate
 description: "Universal team coordination skill with dynamic role generation. Uses team-worker agent architecture with role-spec files. Only coordinator is built-in -- all worker roles are generated at runtime as role-specs and spawned via team-worker agent. Beat/cadence model for orchestration. Triggers on \"Team Coordinate \"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Coordinate 
@@ -110,7 +110,7 @@ User provides task description
 When coordinator spawns workers, use `team-worker` agent with role-spec path:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: <team-name>,
@@ -147,7 +147,7 @@ Execute built-in Phase 1 (task discovery) -> role-spec Phase 2-4 -> built-in Pha
 When pipeline completes (all tasks done), coordinator presents an interactive choice:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Team pipeline complete. What would you like to do?",
     header: "Completion",
@@ -243,7 +243,7 @@ AskUserQuestion({
 Coordinator supports `resume` / `continue` for interrupted sessions:
 
 1. Scan `.workflow/.team/TC-*/team-session.json` for active/paused sessions
-2. Multiple matches -> AskUserQuestion for selection
+2. Multiple matches -> user prompt for selection
 3. Audit TaskList -> reconcile session state <-> task status
 4. Reset in_progress -> pending (interrupted tasks)
 5. Rebuild team and spawn needed workers only

package/skills/team-designer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-designer
 description: "Meta-skill for generating team skills following the v4 architecture pattern. Produces complete skill packages with SKILL.md router, coordinator, worker roles, specs, and templates. Triggers on \"team-designer\", \"design team\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Skill Designer

package/skills/team-executor/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-executor
 description: "Lightweight session execution skill. Resumes existing team-coordinate sessions for pure execution via team-worker agents. No analysis, no role generation -- only loads and executes. Session path required. Triggers on \"Team Executor\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Executor
@@ -107,7 +107,7 @@ Validate session
 When executor spawns workers, use `team-worker` agent with role-spec path:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: <team-name>,
@@ -139,7 +139,7 @@ Read role_spec file to load Phase 2-4 domain instructions.`
 When pipeline completes (all tasks done), executor presents an interactive choice:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Team pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-frontend/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-frontend
 description: "Unified team skill for frontend development. Pure router — all roles read this file. Beat model is coordinator-only in monitor.md. Built-in ui-ux-pro-max design intelligence. Triggers on \"team frontend\"."
-allowed-tools: Agent TaskCreate TaskList TaskGet TaskUpdate TeamCreate TeamDelete SendMessage AskUserQuestion Read Write Edit Bash Glob Grep WebFetch WebSearch mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep WebFetch WebSearch maestro
 ---
 
 # Team Frontend Development
@@ -66,7 +66,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "frontend",

package/skills/team-frontend-debug/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-frontend-debug
 description: "Frontend debugging team using Chrome DevTools MCP. Dual-mode — feature-list testing or bug-report debugging. Triggers on \"team-frontend-debug\", \"frontend debug\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg mcp__chrome-devtools__*
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__chrome-devtools__* maestro
 ---
 
 # Frontend Debug Team
@@ -113,7 +113,7 @@ All browser inspection operations use Chrome DevTools MCP. Reproducer and Verifi
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: <team-name>,
@@ -154,7 +154,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 When pipeline completes, coordinator presents:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-interactive-craft/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-interactive-craft
 description: "Unified team skill for interactive component crafting. Vanilla JS + CSS interactive components with zero dependencies. Research -> interaction design -> build -> a11y test. Uses team-worker agent architecture. Triggers on \"team interactive craft\", \"interactive component\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep TaskList TaskGet TaskUpdate TaskCreate TeamCreate TeamDelete SendMessage mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file maestro
 ---
 
 # Team Interactive Craft
@@ -67,7 +67,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker for <task-id>",
   team_name: "interactive-craft",

package/skills/team-issue/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-issue
 description: "Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on \"team issue\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Issue Resolution
@@ -67,7 +67,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "issue",
@@ -96,7 +96,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 **Parallel spawn** (Batch mode, N explorer or M implementer instances):
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   name: "<role>-<N>",
   team_name: "issue",

package/skills/team-lifecycle-v4/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-lifecycle-v4
 description: "Full lifecycle team skill — plan, develop, test, review in one coordinated session. Role-based architecture with coordinator-driven beat model. Triggers on \"team lifecycle v4\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Lifecycle v4
@@ -63,7 +63,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: <team-name>,
@@ -96,7 +96,7 @@ Supervisor is a **resident agent** (independent from team-worker). Spawned once
 ### Spawn (Phase 2 — once per session)
 
 ```
-Agent({
+teammate({
   subagent_type: "team-supervisor",
   description: "Spawn resident supervisor",
   team_name: <team-name>,
@@ -162,7 +162,7 @@ SendMessage({
 When pipeline completes, coordinator presents:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-motion-design/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-motion-design
 description: "Unified team skill for motion design. Animation token systems, scroll choreography, GPU-accelerated transforms, reduced-motion fallback. Uses team-worker agent architecture. Triggers on \"team motion design\", \"animation system\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep TaskList TaskGet TaskUpdate TaskCreate TeamCreate TeamDelete SendMessage mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__maestro__team_msg mcp__chrome-devtools__performance_start_trace mcp__chrome-devtools__performance_stop_trace mcp__chrome-devtools__performance_analyze_insight mcp__chrome-devtools__evaluate_script mcp__chrome-devtools__take_screenshot
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__chrome-devtools__performance_start_trace mcp__chrome-devtools__performance_stop_trace mcp__chrome-devtools__performance_analyze_insight mcp__chrome-devtools__evaluate_script mcp__chrome-devtools__take_screenshot maestro
 ---
 
 # Team Motion Design
@@ -66,7 +66,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker for <task-id>",
   team_name: "motion-design",

package/skills/team-perf-opt/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-perf-opt
 description: "Unified team skill for performance optimization. Coordinator orchestrates pipeline, workers are team-worker agents. Supports single/fan-out/independent parallel modes. Triggers on \"team perf-opt\"."
-allowed-tools: Agent TaskCreate TaskList TaskGet TaskUpdate TeamCreate TeamDelete SendMessage AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Performance Optimization
@@ -77,7 +77,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "perf-opt",
@@ -142,7 +142,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 When the pipeline completes:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Team pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-planex/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-planex
 description: "Unified team skill for plan-and-execute pipeline. Pure router — coordinator always. Beat model is coordinator-only in monitor.md. Triggers on \"team planex\"."
-allowed-tools: Agent TaskCreate TaskList TaskGet TaskUpdate TeamCreate TeamDelete SendMessage AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team PlanEx
@@ -65,7 +65,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "planex",

package/skills/team-quality-assurance/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-quality-assurance
 description: "Unified team skill for quality assurance. Full closed-loop QA combining issue discovery and software testing. Triggers on \"team quality-assurance\", \"team qa\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Quality Assurance
@@ -60,7 +60,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "quality-assurance",
@@ -101,7 +101,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 When pipeline completes, coordinator presents:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Quality Assurance pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-review/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-review
 description: "Unified team skill for code review. 3-role pipeline: scanner, reviewer, fixer. Triggers on team-review."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Review
@@ -58,7 +58,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "review",
@@ -101,7 +101,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 When pipeline completes, coordinator presents:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Review pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-roadmap-dev/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-roadmap-dev
 description: "Unified team skill for roadmap-driven development workflow. Coordinator discusses roadmap with user, then dispatches phased execution pipeline (plan -> execute -> verify). All roles invoke this skill with --role arg. Triggers on \"team roadmap-dev\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Roadmap Dev
@@ -72,7 +72,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "roadmap-dev",
@@ -138,7 +138,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 When the pipeline completes:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Roadmap Dev pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-swarm/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-swarm
 description: "Swarm intelligence team skill — ACO-driven multi-agent exploration with hybrid LLM coordinator + Python optimization controller. Coordinator generates swarm-config from user task, then runs K iterations of N parallel ants guided by pheromone state. Universal task space via config (nodes + scoring rule). Triggers on \"team swarm\", \"swarm intelligence\", \"蚁群\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Swarm
@@ -66,7 +66,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "swarm",
@@ -150,7 +150,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 When swarm converges, coordinator presents:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Swarm pipeline complete. What would you like to do?",
     header: "Completion",
@@ -171,7 +171,7 @@ AskUserQuestion({
 |----------|------------|
 | `aco.py` not found | Verify `<skill_root>/scripts/aco.py`; check Python install |
 | Python version < 3.10 | Use `python3` or report dependency error |
-| Config validation fails | AskUserQuestion to fix, regenerate, retry |
+| Config validation fails | user prompt to fix, regenerate, retry |
 | All ants fail in iteration | Halt, AskUserQuestion (retry / abort / refine config) |
 | Hallucination cluster (>50%) | Pause, AskUserQuestion (continue / refine scoring) |
 | Convergence never trips | `max_iterations` safety net always fires |

package/skills/team-tech-debt/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-tech-debt
 description: "Unified team skill for tech debt identification and remediation. Scans codebase for tech debt, assesses severity, plans and executes fixes with validation. Uses team-worker agent architecture with roles/ for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on \"team tech debt\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep TaskList TaskGet TaskUpdate TaskCreate TeamCreate TeamDelete SendMessage mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file maestro
 ---
 
 # Team Tech Debt
@@ -60,7 +60,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker for <task-id>",
   team_name: "tech-debt",

package/skills/team-testing/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-testing
 description: "Unified team skill for testing team. Progressive test coverage through Generator-Critic loops, shared memory, and dynamic layer selection. Triggers on \"team testing\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Testing
@@ -59,7 +59,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "testing",
@@ -99,7 +99,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 When pipeline completes, coordinator presents:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Testing pipeline complete. What would you like to do?",
     header: "Completion",

package/skills/team-ui-polish/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-ui-polish
 description: "Unified team skill for UI polish. Auto-discover and fix UI design issues using Impeccable design standards. Anti-AI-slop detection, color/typography/spacing quality, motion, interaction states, visual hierarchy. Uses team-worker agent architecture. Triggers on \"team ui polish\", \"ui polish\", \"design polish\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep TaskList TaskGet TaskUpdate TaskCreate TeamCreate TeamDelete SendMessage mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__maestro__team_msg mcp__chrome-devtools__evaluate_script mcp__chrome-devtools__take_screenshot mcp__chrome-devtools__navigate_page mcp__chrome-devtools__resize_page
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__chrome-devtools__evaluate_script mcp__chrome-devtools__take_screenshot mcp__chrome-devtools__navigate_page mcp__chrome-devtools__resize_page maestro
 ---
 
 # Team UI Polish
@@ -67,7 +67,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker for <task-id>",
   team_name: "ui-polish",

package/skills/team-uidesign/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-uidesign
 description: "Unified team skill for UI design team. Research -> design tokens -> audit -> implementation. Uses team-worker agent architecture with roles/ for domain logic. Coordinator orchestrates dual-track pipeline with GC loops and sync points. Triggers on \"team ui design\", \"ui design team\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep TaskList TaskGet TaskUpdate TaskCreate TeamCreate TeamDelete SendMessage mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file maestro
 ---
 
 # Team UI Design
@@ -66,7 +66,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker for <task-id>",
   team_name: "uidesign",

package/skills/team-ultra-analyze/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-ultra-analyze
 description: "Deep collaborative analysis team skill. Multi-role investigation with coordinator-driven synthesis. Triggers on \"team ultra-analyze\", \"team analyze\"."
-allowed-tools: TeamCreate TeamDelete SendMessage TaskCreate TaskUpdate TaskList TaskGet Agent AskUserQuestion Read Write Edit Bash Glob Grep mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Team Ultra Analyze
@@ -74,7 +74,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker",
   team_name: "ultra-analyze",
@@ -136,7 +136,7 @@ Execute built-in Phase 1 (task discovery, owner=<agent-name>) -> role Phase 2-4
 When pipeline completes, coordinator presents:
 
 ```
-AskUserQuestion({
+ask user ({
   questions: [{
     question: "Ultra-Analyze pipeline complete. What would you like to do?",
     header: "Completion",
@@ -154,7 +154,7 @@ AskUserQuestion({
 |--------|--------|
 | Archive & Clean | Update session status="completed" -> TeamDelete() -> output final summary |
 | Keep Active | Update session status="paused" -> output resume instructions |
-| Export Results | AskUserQuestion for target path -> copy deliverables -> Archive & Clean |
+| Export Results | user prompt for target path -> copy deliverables -> Archive & Clean |
 
 ## Specs Reference
 

package/skills/team-ux-improve/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-ux-improve
 description: "Unified team skill for UX improvement. Systematically discovers and fixes UI/UX interaction issues including unresponsive buttons, missing feedback, and state refresh problems. Uses team-worker agent architecture with roles/ for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on \"team ux improve\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep TaskList TaskGet TaskUpdate TaskCreate TeamCreate TeamDelete SendMessage mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__maestro__team_msg
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file maestro
 ---
 
 # Team UX Improve
@@ -75,7 +75,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker for <task-id>",
   team_name: "ux-improve",
@@ -144,7 +144,7 @@ Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5
 | Unknown command | Error with available command list |
 | Role not found | Error with role registry |
 | Project path invalid | Re-prompt user for valid path |
-| Framework detection fails | AskUserQuestion for framework selection |
+| Framework detection fails | user prompt for framework selection |
 | Session corruption | Attempt recovery, fallback to manual |
 | Fast-advance conflict | Coordinator reconciles on next callback |
 | No UI issues found | Complete with empty fix list, generate clean bill report |

package/skills/team-visual-a11y/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: team-visual-a11y
 description: "Unified team skill for visual accessibility QA. OKLCH color contrast, typography readability, focus management, WCAG AA/AAA audit at rendered level. Uses team-worker agent architecture. Triggers on \"team visual a11y\", \"accessibility audit\", \"visual a11y\"."
-allowed-tools: Agent AskUserQuestion Read Write Edit Bash Glob Grep TaskList TaskGet TaskUpdate TaskCreate TeamCreate TeamDelete SendMessage mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__maestro__team_msg mcp__chrome-devtools__evaluate_script mcp__chrome-devtools__take_screenshot mcp__chrome-devtools__emulate mcp__chrome-devtools__lighthouse_audit mcp__chrome-devtools__navigate_page mcp__chrome-devtools__resize_page
+allowed-tools: teammate Read Write Edit Bash Glob Grep mcp__maestro__read_file mcp__maestro__write_file mcp__maestro__edit_file mcp__chrome-devtools__evaluate_script mcp__chrome-devtools__take_screenshot mcp__chrome-devtools__emulate mcp__chrome-devtools__lighthouse_audit mcp__chrome-devtools__navigate_page mcp__chrome-devtools__resize_page maestro
 ---
 
 # Team Visual Accessibility
@@ -78,7 +78,7 @@ Parse `$ARGUMENTS`:
 Coordinator spawns workers using this template:
 
 ```
-Agent({
+teammate({
   subagent_type: "team-worker",
   description: "Spawn <role> worker for <task-id>",
   team_name: "visual-a11y",

package/skills/workflow-skill-designer/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: workflow-skill-designer
 description: "Meta-skill for designing orchestrator+phases structured workflow skills. Creates SKILL.md coordinator with progressive phase loading, TodoWrite patterns, and data flow. Triggers on \"design workflow skill\", \"create workflow skill\", \"workflow skill designer\"."
-allowed-tools: Agent AskUserQuestion TodoWrite Read Write Edit Bash Glob Grep
+allowed-tools: teammate Read Write Edit Bash Glob Grep maestro
 ---
 
 # Workflow Skill Designer
@@ -108,13 +108,13 @@ CONTEXT: [background/constraints]
 
 ### Pattern 6: Interactive Preference Collection (SKILL.md Responsibility)
 
-Workflow preferences (auto mode, force explore, etc.) MUST be collected via AskUserQuestion in SKILL.md **before** dispatching to phases. Phases reference these as `workflowPreferences.{key}` context variables.
+Workflow preferences (auto mode, force explore, etc.) MUST be collected via user prompt in SKILL.md **before** dispatching to phases. Phases reference these as `workflowPreferences.{key}` context variables.
 
 **Anti-Pattern**: Command-line flags (`--yes`, `-e`, `--explore`) parsed within phase files via `$ARGUMENTS.includes(...)`.
 
 ```javascript
 // CORRECT: In SKILL.md (before phase dispatch)
-const prefResponse = AskUserQuestion({
+const prefResponse = ask user ({
   questions: [
     { question: "是否跳过确认？", header: "Auto Mode", options: [
       { label: "Interactive (Recommended)", description: "交互模式" },
@@ -150,7 +150,7 @@ Phase files are internal execution documents. They MUST NOT contain:
 
 | Prohibited | Reason | Correct Location |
 |------------|--------|------------------|
-| Flag parsing (`$ARGUMENTS.includes(...)`) | Preferences collected in SKILL.md | SKILL.md via AskUserQuestion |
+| Flag parsing (`$ARGUMENTS.includes(...)`) | Preferences collected in SKILL.md | SKILL.md via user prompt |
 | Invocation syntax (`/skill-name "..."`) | Not user-facing docs | Removed or SKILL.md only |
 | Conversion provenance (`Source: Converted from...`) | Implementation detail | Removed |
 | Skill routing for inter-phase (`Skill(skill="...")`) | Use direct phase read | Direct `Read("phases/...")` |
@@ -357,7 +357,7 @@ What goes into SKILL.md vs what goes into phase files:
 ---
 name: {skill-name}
 description: {description}. Triggers on "{trigger1}", "{trigger2}".
-allowed-tools: {tools}
+allowed-tools: {tools} maestro
 ---
 
 # {Title}
@@ -375,8 +375,8 @@ allowed-tools: {tools}
 
 ## Interactive Preference Collection
 
-Collect workflow preferences via AskUserQuestion before dispatching to phases:
-{AskUserQuestion code with preference derivation → workflowPreferences}
+Collect workflow preferences via user prompt before dispatching to phases:
+{user prompt code with preference derivation → workflowPreferences}
 
 ## Auto Mode Defaults
 
@@ -491,6 +491,6 @@ When designing a new workflow skill, answer these questions:
 | What's the TodoWrite granularity? | TodoWrite Pattern | Some phases have sub-tasks, others are atomic |
 | Is there a planning notes pattern? | Post-Phase Updates | Accumulated state document across phases |
 | What's the error recovery? | Error Handling | Retry once then report, vs rollback |
-| Does it need preference collection? | Interactive Preference Collection | Collect via AskUserQuestion in SKILL.md, pass as workflowPreferences |
+| Does it need preference collection? | Interactive Preference Collection | Collect via user prompt in SKILL.md, pass as workflowPreferences |
 | Does phase N hand off to phase M? | Direct Phase Handoff (Pattern 7) | Read phase doc directly, not Skill() routing |
 | Will later phases run after long context? | Compact Recovery (Pattern 9) | Add sentinel + checkpoints, mark 🔄 in Phase Reference table |