maestro-flow 0.5.1 → 0.5.3

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

@@ -1,111 +1,111 @@
----
-name: quality-sync
-description: Sync codebase docs by tracing git diff impact
-argument-hint: "[--full] [--since <commit|HEAD~N>] [--dry-run]"
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
----
-
-<purpose>
-Sync codebase documentation after code changes by tracing git diff through component, feature, and requirement layers. Updates `.workflow/codebase/` docs to reflect current source state.
-</purpose>
-
-<context>
-
-```bash
-$quality-sync
-$quality-sync "--since HEAD~5"
-$quality-sync "--full"
-$quality-sync "--dry-run"
-$quality-sync "--since abc123 --dry-run"
-```
-
-**Flags**:
-- `--full` -- Complete resync of all tracked files (ignores git diff)
-- `--since <commit|HEAD~N>` -- Diff since specific commit (default: last sync timestamp)
-- `--dry-run` -- Show what would be updated without writing
-
-</context>
-
-<execution>
-
-### Step 1: Validate
-
-Verify `.workflow/` directory exists — if missing, raise E001.
-
-### Step 2: Detect Changes
-
-If `--full`: skip diff, mark all tracked files as changed.
-
-Otherwise:
-1. Read last sync timestamp from `state.json` field `last_synced`
-2. If `--since` provided, use that as baseline
-3. Run `git diff --name-only {baseline} HEAD` to get changed files
-
-If no changes and not `--full`, report clean state (W001) and exit.
-
-### Step 3: Trace Impact Chain
-
-For each changed file, trace through `doc-index.json` impact layers:
-1. **File layer** -- Which doc entries reference this file directly
-2. **Component layer** -- Which components contain this file
-3. **Feature layer** -- Which features depend on affected components
-4. **Requirement layer** -- Which requirements trace to affected features
-
-Build the full set of affected documentation entries.
-
-### Step 4: Update Documentation
-
-If `--dry-run`: display affected entries and exit.
-
-For each affected entry:
-1. Re-read source files
-2. Regenerate the documentation section in `.workflow/codebase/`
-3. Update `doc-index.json` with new timestamp and content hash
-
-### Step 5: Update State
-
-Update `state.json`:
-- `last_synced: "{ISO timestamp}"`
-- `last_synced_commit: "{HEAD commit hash}"`
-
-Update affected `index.json` files in phase directories if task files were modified.
-
-### Step 6: Tech Stack Refresh (Conditional)
-
-If dependency manifests changed (`package.json`, `Cargo.toml`, `go.mod`, `pyproject.toml`, `pom.xml`):
-- Re-read manifest files
-- Update `project.md` Tech Stack section with current dependencies/versions
-- Update `doc-index.json` tech-registry entries
-
-### Step 7: Report & Routing
-
-Display summary: files changed, components affected, features affected, docs updated, tech stack refreshed (if applicable).
-
-**Next-step routing:**
-
-| Result | Next Step |
-|--------|-----------|
-| Docs refreshed successfully | `$manage-status` |
-| Major structural changes detected (new modules, removed dirs) | `$manage-codebase-rebuild` (full rebuild recommended) |
-| Dependency manifests changed significantly | Review `project.md` Tech Stack for accuracy |
-
-</execution>
-
-<error_codes>
-
-| Code | Severity | Description |
-|------|----------|-------------|
-| E001 | error | `.workflow/` not initialized -- run `Skill({ skill: "maestro-init" })` first |
-| W001 | warning | No changes detected since last sync |
-
-</error_codes>
-
-<success_criteria>
-- [ ] Changed files detected (or full resync triggered)
-- [ ] Impact chain traced through all layers (file → component → feature → requirement)
-- [ ] Documentation entries updated in `.workflow/codebase/`
-- [ ] `doc-index.json` reflects current file state with updated hashes
-- [ ] `state.json` updated with sync timestamp and commit hash
-- [ ] If dependency manifests changed: project.md Tech Stack section refreshed
-- [ ] Summary report with next-step routing displayed
-</success_criteria>
+---
+name: quality-sync
+description: Sync codebase docs by tracing git diff impact
+argument-hint: "[--full] [--since <commit|HEAD~N>] [--dry-run]"
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, request_user_input
+---
+
+<purpose>
+Sync codebase documentation after code changes by tracing git diff through component, feature, and requirement layers. Updates `.workflow/codebase/` docs to reflect current source state.
+</purpose>
+
+<context>
+
+```bash
+$quality-sync
+$quality-sync "--since HEAD~5"
+$quality-sync "--full"
+$quality-sync "--dry-run"
+$quality-sync "--since abc123 --dry-run"
+```
+
+**Flags**:
+- `--full` -- Complete resync of all tracked files (ignores git diff)
+- `--since <commit|HEAD~N>` -- Diff since specific commit (default: last sync timestamp)
+- `--dry-run` -- Show what would be updated without writing
+
+</context>
+
+<execution>
+
+### Step 1: Validate
+
+Verify `.workflow/` directory exists — if missing, raise E001.
+
+### Step 2: Detect Changes
+
+If `--full`: skip diff, mark all tracked files as changed.
+
+Otherwise:
+1. Read last sync timestamp from `state.json` field `last_synced`
+2. If `--since` provided, use that as baseline
+3. Run `git diff --name-only {baseline} HEAD` to get changed files
+
+If no changes and not `--full`, report clean state (W001) and exit.
+
+### Step 3: Trace Impact Chain
+
+For each changed file, trace through `doc-index.json` impact layers:
+1. **File layer** -- Which doc entries reference this file directly
+2. **Component layer** -- Which components contain this file
+3. **Feature layer** -- Which features depend on affected components
+4. **Requirement layer** -- Which requirements trace to affected features
+
+Build the full set of affected documentation entries.
+
+### Step 4: Update Documentation
+
+If `--dry-run`: display affected entries and exit.
+
+For each affected entry:
+1. Re-read source files
+2. Regenerate the documentation section in `.workflow/codebase/`
+3. Update `doc-index.json` with new timestamp and content hash
+
+### Step 5: Update State
+
+Update `state.json`:
+- `last_synced: "{ISO timestamp}"`
+- `last_synced_commit: "{HEAD commit hash}"`
+
+Update affected `index.json` files in phase directories if task files were modified.
+
+### Step 6: Tech Stack Refresh (Conditional)
+
+If dependency manifests changed (`package.json`, `Cargo.toml`, `go.mod`, `pyproject.toml`, `pom.xml`):
+- Re-read manifest files
+- Update `project.md` Tech Stack section with current dependencies/versions
+- Update `doc-index.json` tech-registry entries
+
+### Step 7: Report & Routing
+
+Display summary: files changed, components affected, features affected, docs updated, tech stack refreshed (if applicable).
+
+**Next-step routing:**
+
+| Result | Next Step |
+|--------|-----------|
+| Docs refreshed successfully | `$manage-status` |
+| Major structural changes detected (new modules, removed dirs) | `$manage-codebase-rebuild` (full rebuild recommended) |
+| Dependency manifests changed significantly | Review `project.md` Tech Stack for accuracy |
+
+</execution>
+
+<error_codes>
+
+| Code | Severity | Description |
+|------|----------|-------------|
+| E001 | error | `.workflow/` not initialized -- run `$maestro-init` first |
+| W001 | warning | No changes detected since last sync |
+
+</error_codes>
+
+<success_criteria>
+- [ ] Changed files detected (or full resync triggered)
+- [ ] Impact chain traced through all layers (file → component → feature → requirement)
+- [ ] Documentation entries updated in `.workflow/codebase/`
+- [ ] `doc-index.json` reflects current file state with updated hashes
+- [ ] `state.json` updated with sync timestamp and commit hash
+- [ ] If dependency manifests changed: project.md Tech Stack section refreshed
+- [ ] Summary report with next-step routing displayed
+</success_criteria>

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

@@ -2,7 +2,7 @@
 name: quality-test
 description: Use when implementation needs user acceptance testing with interactive verification and gap closure
 argument-hint: "<phase> [-y] [--smoke] [--auto-fix] [--session ID]"
-allowed-tools: spawn_agents_on_csv, Read, Write, Edit, Bash, Glob, Grep, AskUserQuestion
+allowed-tools: spawn_agents_on_csv, Read, Write, Edit, Bash, Glob, Grep, request_user_input
 ---
 
 <purpose>

package/.codex/skills/spec-add/SKILL.md

@@ -86,14 +86,14 @@ Append `<spec-entry>` closed-tag block to target file:
 
 ### Step 6: Confirm
 
-Display: category, target file, extracted keywords, and commands for verify (`/spec-load`) and remove (`/spec-remove`).
+Display: category, target file, extracted keywords, and commands for verify (`$spec-load`) and remove (`$spec-remove`).
 </execution>
 
 <error_codes>
 | Code | Severity | Description |
 |------|----------|-------------|
 | E001 | fatal | Category and content are both required |
-| E002 | fatal | `.workflow/specs/` not initialized -- run `Skill({ skill: "spec-setup" })` first |
+| E002 | fatal | `.workflow/specs/` not initialized -- run `$spec-setup` first |
 | E003 | fatal | Invalid category -- must be one of: coding, arch, quality, debug, test, review, learning, ui, bug, pattern, decision, rule, validation |
 </error_codes>
 

package/.codex/skills/spec-load/SKILL.md

@@ -59,7 +59,7 @@ Show matched entries grouped by filename and category, with `<spec-entry>` tags
 <error_codes>
 | Code | Severity | Description |
 |------|----------|-------------|
-| E001 | fatal | `.workflow/specs/` not initialized -- run `Skill({ skill: "spec-setup" })` first |
+| E001 | fatal | `.workflow/specs/` not initialized -- run `$spec-setup` first |
 | W001 | warning | No matching specs for keyword -- showing all in category |
 </error_codes>