maestro-flow 0.3.4 → 0.3.6

package/.codex/skills/quality-sync/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-sync
+name: quality-sync
 description: Sync codebase docs after code changes -- traces git diff through component/feature/requirement layers
 argument-hint: "[--full] [--since <commit|HEAD~N>] [--dry-run]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep
@@ -10,11 +10,11 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep
 ## Usage
 
 ```bash
-$maestro-sync
-$maestro-sync "--since HEAD~5"
-$maestro-sync "--full"
-$maestro-sync "--dry-run"
-$maestro-sync "--since abc123 --dry-run"
+$quality-sync
+$quality-sync "--since HEAD~5"
+$quality-sync "--full"
+$quality-sync "--dry-run"
+$quality-sync "--since abc123 --dry-run"
 ```
 
 **Flags**:

package/.codex/skills/quality-test/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: maestro-test
+name: quality-test
 description: Conversational UAT with session persistence, auto-diagnosis, and gap-plan closure loop. Interactive testing flow with severity inference and parallel debug agents.
 argument-hint: "<phase> [--auto-fix] [--session ID]"
 allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, AskUserQuestion
@@ -14,10 +14,10 @@ No auto mode -- UAT is inherently interactive. `--auto-fix` only automates gap c
 ## Usage
 
 ```bash
-$maestro-test "3"                    # test phase 3
-$maestro-test "3 --smoke"            # smoke tests first, then UAT
-$maestro-test "3 --auto-fix"         # auto-trigger gap-fix loop on failures
-$maestro-test "--session 04-comments"  # resume specific session
+$quality-test "3"                    # test phase 3
+$quality-test "3 --smoke"            # smoke tests first, then UAT
+$quality-test "3 --auto-fix"         # auto-trigger gap-fix loop on failures
+$quality-test "--session 04-comments"  # resume specific session
 ```
 
 **Flags**: