maestro-flow 0.5.2 → 0.5.31

package/workflows/specs-remove.md

@@ -1,104 +1,104 @@
-# Spec Remove Workflow
-
-Remove a `<spec-entry>` block from a specs container file. Symmetric with `specs-add.md`.
-
-Uses `maestro wiki remove-entry` for atomic removal — the entry is deleted from the markdown file and the unified wiki index is auto-updated by WikiIndexer.
-
----
-
-## Prerequisites
-
-- `.workflow/specs/` initialized (at least one specs file exists)
-- `maestro wiki` CLI available
-- Entry ID known (use `maestro wiki list --type spec` to discover)
-
----
-
-## Argument Shape
-
-```
-/spec-remove spec-learnings-003                → remove entry 003 from learnings.md
-/spec-remove spec-coding-conventions-001       → remove entry 001 from coding-conventions.md
-/spec-remove spec-quality-rules-005 -y         → remove without confirmation
-```
-
-| Flag | Effect |
-|------|--------|
-| `<entry-id>` | Required. The spec sub-node ID to remove |
-| `-y` / `--yes` | Skip confirmation prompt |
-
----
-
-## Stage 1: Parse Input
-
-1. Extract entry ID from arguments
-2. Validate non-empty (E001 if missing)
-3. Check `.workflow/specs/` exists (E002 if not)
-
----
-
-## Stage 2: Lookup Entry
-
-1. Run `maestro wiki get <entry-id> --json` to fetch entry metadata
-2. Validate entry exists (E003 if not found)
-3. Validate entry is a spec sub-node — must have:
-   - `type` = "spec"
-   - `parent` field set (sub-nodes have parent pointing to container)
-   - If not a sub-node, error E004
-4. Extract: title, category, keywords, container file path, body preview
-
----
-
-## Stage 3: Confirm Removal
-
-Display entry details for user confirmation:
-
-```
-== Spec Entry to Remove ==
-ID:        {entry-id}
-Title:     {title}
-Category:  {category}
-Keywords:  {keywords}
-Container: .workflow/specs/{filename}
-Preview:   {first 80 chars of body}
-
-Remove this entry? [y/N]
-```
-
-If `-y` flag: skip confirmation.
-If user declines: abort with "Cancelled."
-
----
-
-## Stage 4: Remove Entry
-
-Execute removal via wiki CLI:
-
-```bash
-maestro wiki remove-entry <entry-id>
-```
-
-This command:
-1. Reads the container file
-2. Locates the `<spec-entry>` block by index position
-3. Removes the block (including opening tag, body, closing tag)
-4. Writes the updated file
-5. WikiIndexer auto-updates `.workflow/wiki-index.json`
-
----
-
-## Stage 5: Verify & Report
-
-1. Verify entry no longer appears: `maestro wiki get <entry-id>` should return not-found
-2. Display confirmation:
-
-```
-== Entry Removed ==
-ID:        {entry-id}
-From:      .workflow/specs/{filename}
-Remaining: {remaining entry count} entries in {filename}
-
-To verify:  maestro wiki list --type spec --category {category}
-To re-add:  /spec-add {category} {content}
-```
-
+# Spec Remove Workflow
+
+Remove a `<spec-entry>` block from a specs container file. Symmetric with `specs-add.md`.
+
+Uses `maestro wiki remove-entry` for atomic removal — the entry is deleted from the markdown file and the unified wiki index is auto-updated by WikiIndexer.
+
+---
+
+## Prerequisites
+
+- `.workflow/specs/` initialized (at least one specs file exists)
+- `maestro wiki` CLI available
+- Entry ID known (use `maestro wiki list --type spec` to discover)
+
+---
+
+## Argument Shape
+
+```
+/spec-remove spec-learnings-003                → remove entry 003 from learnings.md
+/spec-remove spec-coding-conventions-001       → remove entry 001 from coding-conventions.md
+/spec-remove spec-quality-rules-005 -y         → remove without confirmation
+```
+
+| Flag | Effect |
+|------|--------|
+| `<entry-id>` | Required. The spec sub-node ID to remove |
+| `-y` / `--yes` | Skip confirmation prompt |
+
+---
+
+## Stage 1: Parse Input
+
+1. Extract entry ID from arguments
+2. Validate non-empty (E001 if missing)
+3. Check `.workflow/specs/` exists (E002 if not)
+
+---
+
+## Stage 2: Lookup Entry
+
+1. Run `maestro wiki get <entry-id> --json` to fetch entry metadata
+2. Validate entry exists (E003 if not found)
+3. Validate entry is a spec sub-node — must have:
+   - `type` = "spec"
+   - `parent` field set (sub-nodes have parent pointing to container)
+   - If not a sub-node, error E004
+4. Extract: title, category, keywords, container file path, body preview
+
+---
+
+## Stage 3: Confirm Removal
+
+Display entry details for user confirmation:
+
+```
+== Spec Entry to Remove ==
+ID:        {entry-id}
+Title:     {title}
+Category:  {category}
+Keywords:  {keywords}
+Container: .workflow/specs/{filename}
+Preview:   {first 80 chars of body}
+
+Remove this entry? [y/N]
+```
+
+If `-y` flag: skip confirmation.
+If user declines: abort with "Cancelled."
+
+---
+
+## Stage 4: Remove Entry
+
+Execute removal via wiki CLI:
+
+```bash
+maestro wiki remove-entry <entry-id>
+```
+
+This command:
+1. Reads the container file
+2. Locates the `<spec-entry>` block by index position
+3. Removes the block (including opening tag, body, closing tag)
+4. Writes the updated file
+5. WikiIndexer auto-updates `.workflow/wiki-index.json`
+
+---
+
+## Stage 5: Verify & Report
+
+1. Verify entry no longer appears: `maestro wiki get <entry-id>` should return not-found
+2. Display confirmation:
+
+```
+== Entry Removed ==
+ID:        {entry-id}
+From:      .workflow/specs/{filename}
+Remaining: {remaining entry count} entries in {filename}
+
+To verify:  maestro wiki list --type spec --category {category}
+To re-add:  /spec-add {category} {content}
+```
+

package/workflows/sync.md

@@ -1,11 +1,6 @@
 # Workflow: sync
 
-Change detection, impact chain traversal, and codebase documentation synchronization.
-
-## Trigger
-
-- Auto-triggered after `/workflow:execute` completes
-- Manual via `/workflow:sync [--since <ref>] [--dry-run]`
+Change detection, impact chain traversal, and codebase doc synchronization. Auto-triggered after execute, or manual via `/workflow:sync`.
 
 ## Arguments
 
@@ -15,11 +10,6 @@ Change detection, impact chain traversal, and codebase documentation synchroniza
 | `--since <ref>` | Git ref for diff baseline (commit hash, `HEAD~N`, branch) | `HEAD~1` |
 | `--dry-run` | Show impact analysis without writing changes | `false` |
 
-## Prerequisites
-
-- `.workflow/codebase/doc-index.json` must exist (run `/workflow:codebase rebuild` first if missing)
-- Git repository initialized with at least one commit
-
 ---
 
 ## Workflow Steps
@@ -45,19 +35,9 @@ No files changed → emit W001, exit
 ```
 Read .workflow/codebase/doc-index.json
 Extract: components[], features[], requirements[], architecture_decisions[]
-```
 
-**Degradation path — doc-index.json missing:**
-
-```
-If .workflow/codebase/doc-index.json does NOT exist:
-  1. Emit WARNING: "doc-index.json missing — sync cannot perform impact analysis."
-  2. Prompt user with two choices:
-     (a) Run `/manage-codebase-rebuild` to build doc-index, then re-run sync (recommended)
-     (b) Fall back to git-diff-only mode: skip Steps 3-5, emit raw changed-file
-         list from Step 2 as the sync output (no component/feature mapping)
-  3. If user picks (b): set DEGRADED_MODE = true and continue with git diff only.
-  4. If user picks (a) or no answer: exit with code E002.
+If missing: prompt → (a) run /manage-codebase-rebuild then re-run (recommended)
+             or    → (b) DEGRADED_MODE: git-diff-only, skip Steps 3-5
 ```
 
 ### Step 4: Impact Chain Traversal
@@ -73,47 +53,37 @@ Aggregate deduplicated: { files, components, features, requirements }
 ### Step 5: Update Doc Index (skip if --dry-run)
 
 ```
-Affected components → refresh last_updated, re-scan code_locations for exported symbols[]
-Affected features   → refresh last_updated, update status from component changes
+Affected components → refresh last_updated, re-scan code_locations for symbols[]
+Affected features   → refresh last_updated, update status
 Write updated doc-index.json
 ```
 
 ### Step 6: Regenerate Affected Docs (skip if --dry-run)
 
 ```
-Affected components → regenerate .workflow/codebase/tech-registry/{component-slug}.md
-  Template: name, id, type, code_locations, feature_ids, symbols list, timestamp
-
-Affected features → regenerate .workflow/codebase/feature-maps/{feature-slug}.md
-  Template: name, id, status, phase, component_ids, requirement_ids, component details, timestamp
+Components → regenerate .workflow/codebase/tech-registry/{component-slug}.md
+Features   → regenerate .workflow/codebase/feature-maps/{feature-slug}.md
 ```
 
 ### Step 7: Update State and Specs (skip if --dry-run)
 
 ```
-state.json → set last_sync timestamp, record change summary, update last_updated
+state.json → last_sync timestamp, change summary
 index.json → update affected phase indexes
-
-Spec updates: if patterns/conventions changed → append learnings to relevant spec files
-
-Dependency manifest check (package.json, go.mod, pyproject.toml, Cargo.toml,
-  requirements.txt, pom.xml, build.gradle, Gemfile):
-  If any changed AND .workflow/project.md exists → refresh Tech Stack section
+Dependency manifests changed + project.md exists → refresh Tech Stack section
 ```
 
 ### Step 8: Create Action Log
 
 ```
-hash = git rev-parse --short HEAD (or since-ref)
 Write .workflow/codebase/action-logs/{hash}.md:
-  Sections: date, baseline, files changed, components/features/requirements affected, impact counts
+  date, baseline, files changed, affected components/features/requirements, impact counts
 ```
 
 ### Step 9: Report
 
 ```
-Display: changed files count, affected components/features/requirements (with IDs),
-  specs updated, action log path. Note if --dry-run (no writes).
+Display: changed files, affected components/features/requirements, specs updated, action log path
 ```
 
 ---