maestro-flow 0.3.12 → 0.3.13

package/workflows/specs-remove.md

@@ -0,0 +1,115 @@
+# 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}
+```
+
+---
+
+## Error Codes
+
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | fatal | Entry ID required | Usage: `/spec-remove <entry-id>` |
+| E002 | fatal | `.workflow/specs/` not initialized | Run `/spec-setup` first |
+| E003 | fatal | Entry ID not found in wiki index | Check ID with `maestro wiki list --type spec` |
+| E004 | fatal | Entry is not a spec sub-node | Only `<spec-entry>` sub-nodes can be removed this way |
+| W001 | warning | Container file empty after removal | File kept but has no entries |

package/workflows/specs-setup.md

@@ -52,28 +52,7 @@ Framework detection (from dependency files):
   spring              --> Java Spring
 ```
 
-### Step 3: Write project-tech.json
-
-Output: `.workflow/project-tech.json`
-
-```json
-{
-  "detected_at": "{ISO timestamp}",
-  "languages": ["TypeScript", "..."],
-  "frameworks": ["Next.js", "..."],
-  "package_manager": "npm | yarn | pnpm | ...",
-  "build_system": "tsc | webpack | vite | ...",
-  "test_framework": "jest | vitest | pytest | ...",
-  "linter": "eslint | prettier | ...",
-  "architecture": {
-    "type": "monorepo | single-package | ...",
-    "entry_points": ["src/index.ts", "..."],
-    "key_directories": ["src/", "lib/", "..."]
-  }
-}
-```
-
-### Step 4: Detect Code Patterns
+### Step 3: Detect Code Patterns
 
 Scan source files for coding conventions:
 
@@ -85,9 +64,9 @@ Formatting:   Check for .prettierrc, .editorconfig, eslint config
 File naming:  kebab-case vs camelCase vs PascalCase for source files
 ```
 
-### Step 5: Generate Core Files (always created)
+### Step 4: Generate Core Files (always created)
 
-#### 5a: coding-conventions.md
+#### 4a: coding-conventions.md
 
 Output: `.workflow/specs/coding-conventions.md`
 
@@ -124,7 +103,7 @@ Auto-generated from project analysis. Update manually as patterns evolve.
 {empty section for spec-add entries}
 ```
 
-#### 5b: architecture-constraints.md
+#### 4b: architecture-constraints.md
 
 Output: `.workflow/specs/architecture-constraints.md`
 
@@ -156,7 +135,7 @@ Auto-generated from project structure. Update manually as architecture evolves.
 {empty section for spec-add entries}
 ```
 
-#### 5c: learnings.md
+#### 4c: learnings.md
 
 Output: `.workflow/specs/learnings.md`
 
@@ -175,9 +154,9 @@ Add entries with: `/spec-add learning <description>`
 {empty -- entries added via spec-add}
 ```
 
-### Step 6: Generate Optional Files (when signals detected)
+### Step 5: Generate Optional Files (when signals detected)
 
-#### 6a: quality-rules.md (when linter config or CI detected)
+#### 5a: quality-rules.md (when linter config or CI detected)
 
 Output: `.workflow/specs/quality-rules.md`
 
@@ -193,7 +172,7 @@ category: quality
 {empty -- entries added via spec-add}
 ```
 
-#### 6b: test-conventions.md (when test framework or test files detected)
+#### 5b: test-conventions.md (when test framework or test files detected)
 
 Scan existing test files for conventions (framework, naming, directory structure, patterns).
 
@@ -225,16 +204,15 @@ Auto-generated from project analysis. Update manually as patterns evolve.
 {empty section for spec-add entries}
 ```
 
-#### 6c: debug-notes.md and review-standards.md
+#### 5c: debug-notes.md and review-standards.md
 
 These are NOT created during setup. They are created on demand when `spec-add debug` or `spec-add review` is first used.
 
-### Step 7: Summary
+### Step 6: Summary
 
 Display what was created:
 ```
 Specs initialized:
-  .workflow/project-tech.json                    -- Tech stack analysis
   .workflow/specs/coding-conventions.md          (category: coding)
   .workflow/specs/architecture-constraints.md    (category: arch)
   .workflow/specs/learnings.md                   (category: learning)