specweave 0.28.17 → 0.28.19

package/plugins/specweave-ado/commands/specweave-ado-import-areas.md

@@ -0,0 +1,358 @@
+---
+name: specweave-ado:import-areas
+description: Import Azure DevOps area paths from a project and map them to SpecWeave projects. Creates 2-level directory structure with area path-based organization.
+---
+
+# Import ADO Area Paths Command
+
+You are an Azure DevOps integration expert. Help the user import area paths from an ADO project and map them to SpecWeave projects.
+
+## Command Usage
+
+```bash
+/specweave-ado:import-areas                         # Interactive mode (prompts for project)
+/specweave-ado:import-areas --project MyProduct     # Specific ADO project
+/specweave-ado:import-areas --dry-run               # Preview without creating directories
+/specweave-ado:import-areas --include-children      # Include child area paths
+```
+
+## Your Task
+
+When the user runs this command:
+
+### Step 1: Validate Prerequisites
+
+1. **Check ADO credentials** exist in `.env`:
+   - `AZURE_DEVOPS_PAT`
+   - `AZURE_DEVOPS_ORG`
+   - `AZURE_DEVOPS_PROJECT`
+
+2. **Check config.json** for existing area path mapping:
+   - If `sync.profiles.*.config.areaPathMapping` exists, warn user
+
+### Step 2: Get Project Name
+
+**If `--project` flag provided:**
+- Use the provided project name
+
+**If no flag (interactive mode):**
+```
+🔷 Azure DevOps Area Path Import
+
+Enter the ADO project name to import area paths from:
+> MyProduct
+
+Fetching area paths from project MyProduct...
+```
+
+### Step 3: Fetch and Display Area Paths
+
+```typescript
+import { fetchAreaPathsForProject } from '../lib/ado-board-resolver';
+
+const areaPaths = await fetchAreaPathsForProject(
+  process.env.AZURE_DEVOPS_ORG,
+  'MyProduct',
+  process.env.AZURE_DEVOPS_PAT
+);
+```
+
+**Display area paths:**
+```
+Found 6 area paths in project MyProduct:
+
+  1. ☑ MyProduct\Frontend (45 active items)
+  2. ☑ MyProduct\Backend (78 active items)
+  3. ☑ MyProduct\Mobile (23 active items)
+  4. ☑ MyProduct\DevOps (12 active items)
+  5. ☐ MyProduct\Archive (0 items) [deselected - archive]
+  6. ☐ MyProduct (root) [deselected - root level]
+
+Select area paths to import (Space to toggle, Enter to confirm)
+```
+
+### Step 4: Map Area Paths to SpecWeave Projects
+
+For each selected area path, prompt for SpecWeave project ID:
+
+```
+🏷️  Mapping area paths to SpecWeave projects:
+
+Area path "MyProduct\Frontend" → SpecWeave project ID: [fe]
+  → Include child area paths? [Y/n]: y
+  → Keywords for auto-classification (optional): frontend, ui, angular, css
+
+Area path "MyProduct\Backend" → SpecWeave project ID: [be]
+  → Include child area paths? [Y/n]: y
+  → Keywords for auto-classification (optional): api, server, database, c#
+
+Area path "MyProduct\Mobile" → SpecWeave project ID: [mobile]
+  → Include child area paths? [Y/n]: y
+  → Keywords for auto-classification (optional): ios, android, xamarin
+
+Area path "MyProduct\DevOps" → SpecWeave project ID: [devops]
+  → Include child area paths? [Y/n]: y
+  → Keywords for auto-classification (optional): infrastructure, ci, cd, terraform
+```
+
+**Project ID validation:**
+- Must be lowercase, alphanumeric with hyphens
+- Must not collide with existing project IDs
+- If collision detected, suggest prefixed version: `myproduct-fe` instead of `fe`
+
+### Step 5: Create Directory Structure
+
+Create 2-level directory structure:
+
+```
+.specweave/docs/internal/specs/
+└── ADO-myproduct/              ← Level 1: ADO project
+    ├── fe/                     ← Level 2: SpecWeave project
+    │   └── .gitkeep
+    ├── be/
+    │   └── .gitkeep
+    ├── mobile/
+    │   └── .gitkeep
+    └── devops/
+        └── .gitkeep
+```
+
+### Step 6: Update config.json
+
+Add area path mapping to config:
+
+```json
+{
+  "sync": {
+    "profiles": {
+      "ado-default": {
+        "provider": "ado",
+        "config": {
+          "organization": "myorg",
+          "areaPathMapping": {
+            "project": "MyProduct",
+            "mappings": [
+              {
+                "areaPath": "MyProduct\\Frontend",
+                "specweaveProject": "fe",
+                "includeChildren": true,
+                "keywords": ["frontend", "ui", "angular", "css"]
+              },
+              {
+                "areaPath": "MyProduct\\Backend",
+                "specweaveProject": "be",
+                "includeChildren": true,
+                "keywords": ["api", "server", "database", "c#"]
+              },
+              {
+                "areaPath": "MyProduct\\Mobile",
+                "specweaveProject": "mobile",
+                "includeChildren": true,
+                "keywords": ["ios", "android", "xamarin"]
+              },
+              {
+                "areaPath": "MyProduct\\DevOps",
+                "specweaveProject": "devops",
+                "includeChildren": true,
+                "keywords": ["infrastructure", "ci", "cd", "terraform"]
+              }
+            ]
+          }
+        }
+      }
+    }
+  },
+  "multiProject": {
+    "enabled": true,
+    "activeProject": "fe",
+    "projects": {
+      "fe": {
+        "name": "Frontend",
+        "externalTools": {
+          "ado": {
+            "areaPath": "MyProduct\\Frontend",
+            "project": "MyProduct"
+          }
+        }
+      },
+      "be": {
+        "name": "Backend",
+        "externalTools": {
+          "ado": {
+            "areaPath": "MyProduct\\Backend",
+            "project": "MyProduct"
+          }
+        }
+      },
+      "mobile": {
+        "name": "Mobile",
+        "externalTools": {
+          "ado": {
+            "areaPath": "MyProduct\\Mobile",
+            "project": "MyProduct"
+          }
+        }
+      },
+      "devops": {
+        "name": "DevOps",
+        "externalTools": {
+          "ado": {
+            "areaPath": "MyProduct\\DevOps",
+            "project": "MyProduct"
+          }
+        }
+      }
+    }
+  }
+}
+```
+
+### Step 7: Display Summary
+
+```
+✅ Azure DevOps Area Paths Import Complete!
+
+🔷 ADO Project: MyProduct
+📁 Created: .specweave/docs/internal/specs/ADO-myproduct/
+
+Area paths imported:
+  ✓ MyProduct\Frontend → fe (includes children)
+    Keywords: frontend, ui, angular, css
+  ✓ MyProduct\Backend → be (includes children)
+    Keywords: api, server, database, c#
+  ✓ MyProduct\Mobile → mobile (includes children)
+    Keywords: ios, android, xamarin
+  ✓ MyProduct\DevOps → devops (includes children)
+    Keywords: infrastructure, ci, cd, terraform
+
+💡 Next steps:
+  1. Use /specweave:switch-project fe to switch active project
+  2. Create increment: /specweave:increment "feature name"
+  3. User stories will auto-sync to the correct area path based on keywords
+
+📖 Documentation: .specweave/docs/internal/architecture/adr/0143-jira-ado-multi-level-project-mapping.md
+```
+
+## Examples
+
+### Example 1: Interactive Import
+```
+User: /specweave-ado:import-areas
+
+You:
+🔷 Azure DevOps Area Path Import
+
+Enter the ADO project name: MyProduct
+Fetching area paths...
+
+Found 4 area paths:
+  ☑ MyProduct\Frontend
+  ☑ MyProduct\Backend
+  ☑ MyProduct\Mobile
+  ☐ MyProduct (root) [deselected]
+
+Mapping to SpecWeave projects:
+  MyProduct\Frontend → fe
+  MyProduct\Backend → be
+  MyProduct\Mobile → mobile
+
+✅ Import complete! 3 area paths mapped.
+```
+
+### Example 2: Dry Run
+```
+User: /specweave-ado:import-areas --project MyProduct --dry-run
+
+You:
+🔷 Azure DevOps Area Path Import (DRY RUN)
+
+Would import from project: MyProduct
+
+Would create:
+  .specweave/docs/internal/specs/ADO-myproduct/
+  .specweave/docs/internal/specs/ADO-myproduct/fe/
+  .specweave/docs/internal/specs/ADO-myproduct/be/
+  .specweave/docs/internal/specs/ADO-myproduct/mobile/
+
+Would update config.json with area path mapping.
+
+No changes made (dry run).
+```
+
+### Example 3: Already Configured
+```
+User: /specweave-ado:import-areas
+
+You:
+⚠️  Area path mapping already exists for project MyProduct
+
+Current mappings:
+  MyProduct\Frontend → fe
+  MyProduct\Backend → be
+
+Do you want to:
+  1. Add more area paths
+  2. Replace existing mapping
+  3. Cancel
+
+> 1
+
+Fetching additional area paths...
+  ☐ MyProduct\Frontend (already mapped)
+  ☐ MyProduct\Backend (already mapped)
+  ☑ MyProduct\Mobile (new)
+  ☑ MyProduct\DevOps (new)
+
+Added:
+  MyProduct\Mobile → mobile
+  MyProduct\DevOps → devops
+
+✅ Updated! Now 4 area paths mapped.
+```
+
+## Error Handling
+
+**Missing credentials:**
+```
+❌ Azure DevOps credentials not found
+
+Please add to .env:
+  AZURE_DEVOPS_PAT=your_personal_access_token
+  AZURE_DEVOPS_ORG=your_organization
+  AZURE_DEVOPS_PROJECT=your_project
+
+Or run: specweave init . (to configure Azure DevOps)
+```
+
+**Project not found:**
+```
+❌ ADO project "INVALID" not found in organization "myorg"
+
+Available projects you have access to:
+  - MyProduct (My Product Development)
+  - Infrastructure (DevOps & Infrastructure)
+  - Legacy (Legacy Systems)
+
+Tip: Use /specweave-ado:import-areas --project MyProduct
+```
+
+**No area paths found:**
+```
+⚠️  No child area paths found in project MyProduct
+
+The project only has the root area path. This means:
+  1. Teams aren't using area paths for organization
+  2. You can create area paths in ADO Project Settings
+
+Suggestions:
+  - Use single-project mode (no area path mapping)
+  - Create area paths in ADO: Project Settings → Work → Areas
+  - Run this command again after creating area paths
+```
+
+## Related Commands
+
+- `/specweave-ado:import-projects` - Import multiple ADO projects
+- `/specweave-ado:sync` - Sync increments with ADO
+- `/specweave:switch-project` - Switch active SpecWeave project
+- `/specweave:init-multiproject` - Initialize multi-project mode

package/plugins/specweave-alternatives/skills/architecture-alternatives/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: architecture-alternatives
 description: Software architecture patterns and alternatives expert. Covers monolith vs microservices, serverless, event-driven, CQRS, hexagonal architecture, clean architecture, DDD, and architecture decision frameworks. Activates for architecture patterns, monolith, microservices, serverless, event-driven, CQRS, hexagonal architecture, clean architecture, DDD, architecture decisions, system design, scalability patterns.
+allowed-tools: Read, Grep, Glob
 ---
 
 # Architecture Alternatives Expert Skill

package/plugins/specweave-alternatives/skills/bmad-method/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: bmad-method
 description: BMAD (Best, Most Appropriate, Design) technology decision framework expert. Helps evaluate technology alternatives, analyze tradeoffs, calculate TCO, assess vendor lock-in, and make data-driven architecture decisions. Activates for technology choices, stack decisions, database selection, cloud provider comparison, framework evaluation, architecture decisions, BMAD, best practices, most appropriate, design decisions, technology tradeoffs.
+allowed-tools: Read, Grep, Glob
 ---
 
 # BMAD Method Expert Skill

package/plugins/specweave-core/skills/code-quality/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: code-quality
 description: Expert code quality engineering covering clean code principles, SOLID, DRY, KISS, YAGNI, code smells, refactoring patterns, static analysis, linting, code coverage, mutation testing, and software craftsmanship. Activates for code quality, clean code, SOLID principles, code smells, refactoring, technical debt, code review, linting, eslint, prettier, static analysis, code coverage.
+allowed-tools: Read, Grep, Glob
 ---
 
 # Code Quality Expert

package/plugins/specweave-core/skills/design-patterns/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: design-patterns
 description: Expert knowledge of Gang of Four (GoF) design patterns including creational (Singleton, Factory, Builder, Prototype), structural (Adapter, Decorator, Proxy, Facade), and behavioral (Strategy, Observer, Command, Template Method, Chain of Responsibility). Modern TypeScript/JavaScript implementations with real-world use cases. Activates for design patterns, factory pattern, singleton, strategy pattern, observer pattern, decorator pattern, adapter pattern, builder pattern, proxy pattern, facade pattern, template method.
+allowed-tools: Read, Grep, Glob
 ---
 
 # Design Patterns Expert

package/plugins/specweave-core/skills/software-architecture/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: software-architecture
 description: Expert software architecture covering architectural patterns (microservices, monolith, event-driven, CQRS), scalability, distributed systems, CAP theorem, database architecture, API design, system design, domain-driven design (DDD), hexagonal architecture, and architecture decision records (ADRs). Activates for software architecture, system design, microservices, monolith, event-driven, CQRS, scalability, distributed systems, CAP theorem, DDD, hexagonal architecture, ADR.
+allowed-tools: Read, Grep, Glob
 ---
 
 # Software Architecture Expert

package/plugins/specweave-github/commands/specweave-github-cleanup-duplicates.md

@@ -1,6 +1,6 @@
 ---
 name: specweave-github:cleanup-duplicates
-description: Clean up duplicate GitHub issues for an Epic. Finds issues with duplicate titles and closes all except the first created issue.
+description: Clean up duplicate GitHub issues for a Feature. Finds issues with duplicate titles and closes all except the first created issue.
 justification: |
   CRITICAL INCIDENT RESPONSE TOOL - DO NOT DELETE!
 
@@ -193,33 +193,37 @@ The original issue (#250) contains the same content and should be used for track
 
 ## Related Commands
 
-- `/specweave-github:sync-epic` - Sync Epic (now with duplicate detection!)
+- `/specweave-github:sync` - Sync Feature to GitHub (with duplicate detection)
 - `/specweave:validate` - Validate increment completeness
 - `gh issue list` - View all issues (GitHub CLI)
 
 ## Implementation
 
-**File**: `plugins/specweave-github/lib/github-epic-sync.ts`
+**File**: `plugins/specweave-github/lib/duplicate-detector.ts`
 
-**Method**: `cleanupDuplicates(epicId: string, dryRun: boolean)`
+**Class**: `DuplicateDetector`
 
-**Algorithm**:
-1. Search GitHub for all issues with Epic ID
+**Algorithm** (3-phase protection):
+1. **Detection**: Search GitHub for existing issues matching pattern
+2. **Verification**: Count check to detect duplicates after creation
+3. **Reflection**: Auto-close duplicates automatically
+
+For manual cleanup:
+1. Search GitHub for all issues with Feature ID
 2. Group by title (Map<string, number[]>)
 3. Filter groups with >1 issue (duplicates)
 4. For each duplicate group:
    - Keep first issue (lowest number)
    - Close others with gh CLI
-5. Update Epic README frontmatter
 
 ## Next Steps
 
 After cleanup:
 
 1. **Verify cleanup**: `gh issue list --search "[FS-031]"`
-2. **Check Epic README**: Verify frontmatter has correct issue numbers
-3. **Re-run sync**: `/specweave-github:sync-epic FS-031` (should show no duplicates)
-4. **Enable duplicate detection**: Already enabled in v0.18.0+
+2. **Check Feature FEATURE.md**: Verify frontmatter has correct issue numbers
+3. **Re-run sync**: `/specweave-github:sync` (should show no duplicates)
+4. **Duplicate detection**: Automatically enabled via DuplicateDetector
 
 ---
 

package/plugins/specweave-github/commands/specweave-github-sync.md

@@ -5,6 +5,63 @@ description: Synchronize SpecWeave increment with GitHub issue (Multi-Project Su
 
 # Sync Increment with GitHub Issue (Multi-Project)
 
+## ⚠️ CRITICAL: Sync Routing (Read First!)
+
+**Before executing ANY sync, you MUST determine the correct sync path:**
+
+### Step 0: Detect Project Structure
+
+```bash
+# Check for living docs structure
+if [ -d ".specweave/docs/internal/specs" ] && [ -n "$(ls -A .specweave/docs/internal/specs/*/FEATURE.md 2>/dev/null)" ]; then
+    echo "✅ Living docs found → Use Feature Sync"
+else
+    echo "⚠️ No living docs → Use Increment Sync (brownfield)"
+fi
+```
+
+### Sync Path Decision:
+
+| Structure | Command | Issue Format |
+|-----------|---------|--------------|
+| **Living docs exist** (`.specweave/docs/internal/specs/FS-XXX/`) | Use `github-feature-sync-cli.ts` | `[FS-XXX][US-YYY] Title` |
+| **Increment only** (brownfield, no living docs) | Use `github-increment-sync-cli.ts` | `[FS-XXX] Title` with ACs |
+
+### For Brownfield Projects (No Living Docs):
+
+Use the Increment Sync CLI directly:
+
+```bash
+# Set token
+export GITHUB_TOKEN=$(grep GITHUB_TOKEN .env | cut -d'=' -f2)
+
+# Run increment sync
+node dist/plugins/specweave-github/lib/github-increment-sync-cli.js <increment-id>
+
+# Example
+node dist/plugins/specweave-github/lib/github-increment-sync-cli.js 0002
+```
+
+This creates issues with:
+- ✅ Proper format: `[FS-002] Increment Title`
+- ✅ User Stories listed with checkbox headers
+- ✅ All ACs as checkable items
+- ✅ Links to increment files
+
+### For Projects with Living Docs:
+
+Use the Feature Sync CLI:
+
+```bash
+# Run feature sync
+node dist/plugins/specweave-github/lib/github-feature-sync-cli.js <feature-id>
+
+# Example
+node dist/plugins/specweave-github/lib/github-feature-sync-cli.js FS-062
+```
+
+---
+
 Synchronize the current state of a SpecWeave increment with its GitHub issue across multiple repositories. Supports multi-profile management, time range filtering, and rate limit protection.
 
 ## Usage

package/plugins/specweave-github/hooks/.specweave/logs/hooks-debug.log

@@ -1162,3 +1162,71 @@
 [Wed Nov 26 01:29:07 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
 [Wed Nov 26 01:29:07 EST 2025] [GitHub] 🔗 GitHub sync hook fired
 [Wed Nov 26 01:29:07 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 02:36:06 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:25:15 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:25:15 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:25:15 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:25:15 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:25:16 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:25:16 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:27:50 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:27:50 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:27:50 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:27:50 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:27:50 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:27:50 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:12 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:13 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:22 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:22 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:22 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:22 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:47:22 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:47:22 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:52:20 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:52:20 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:52:20 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:52:20 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 03:52:20 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 03:52:20 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:47:37 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:47:37 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:47:37 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:47:37 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:47:37 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:47:37 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:50:09 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:50:09 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:50:09 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:50:09 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:50:09 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:50:09 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:52:35 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:52:35 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:52:35 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:52:35 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync
+[Wed Nov 26 08:52:36 EST 2025] [GitHub] 🔗 GitHub sync hook fired
+[Wed Nov 26 08:52:36 EST 2025] [GitHub] ⚠️  sync-spec-content CLI not found at /Users/antonabyzov/Projects/github/specweave/plugins/specweave-github/hooks/dist/src/cli/commands/sync-spec-content.js, skipping sync

package/plugins/specweave-github/lib/github-feature-sync.ts

@@ -1,18 +1,13 @@
 /**
  * GitHub Feature Sync - Universal Hierarchy Implementation
  *
- * Architecture (CORRECT):
- * - Feature (FS-033) → GitHub Milestone (Container)
- * - User Story (US-001, US-002, etc.) → GitHub Issue (Trackable item)
- * - Tasks (T-001, T-002, etc.) → Checkboxes in User Story issue body
+ * Architecture:
+ * - Feature (FS-XXX) → GitHub Milestone (Container)
+ * - User Story (US-XXX) → GitHub Issue with format [FS-XXX][US-YYY] Title
+ * - Tasks (T-XXX) → Checkboxes in User Story issue body
  *
- * This implements the TRUE Universal Hierarchy architecture for GitHub.
- *
- * Key Differences from old github-epic-sync.ts:
- * - ❌ OLD: Feature/Increment → GitHub Issue (WRONG!)
- * - ✅ NEW: User Story → GitHub Issue (CORRECT!)
- * - ✅ Creates ONE issue PER user story file (not one per increment)
- * - ✅ Reads us-*.md files from specs/{project}/FS-XXX/
+ * This implements the Universal Hierarchy architecture for GitHub sync.
+ * Creates ONE issue PER user story file from specs/{project}/FS-XXX/us-*.md
  */
 
 import { readdir, readFile, writeFile } from 'fs/promises';