specweave 0.33.4 → 0.33.6

package/src/templates/AGENTS.md.template

@@ -22,7 +22,7 @@
 
 **Initial Increment**: `0001-project-setup` (`.specweave/increments/0001-project-setup/`)
 
-1. **Start Fresh**: Delete it, run `/specweave:increment "your-feature"`
+1. **Start Fresh**: Delete it, run `/sw:increment "your-feature"`
 2. **Customize**: Edit spec.md in the increment folder
 
 ---
@@ -32,16 +32,17 @@
 ```
 1. NEVER pollute project root with .md files
 2. Increment IDs unique (0001-9999)
-3. ONLY 3 files in increment root: spec.md, plan.md, tasks.md
+3. ONLY 4 files in increment root: metadata.json, spec.md, plan.md, tasks.md
 4. All reports/scripts/logs → increment subfolders
-5. Read context-manifest.yaml first (70%+ token savings)
+5. metadata.json MUST exist BEFORE spec.md can be created
 6. tasks.md + spec.md = SOURCE OF TRUTH (update after every task!)
 ```
 
 **File Organization**:
 ```
 .specweave/increments/0001-feature/
-├── spec.md, plan.md, tasks.md    # ONLY these in root
+├── metadata.json                  # REQUIRED - create FIRST
+├── spec.md, plan.md, tasks.md    # Core increment docs
 ├── reports/                       # SESSION-*.md, analysis, etc.
 ├── scripts/                       # Helper scripts
 └── logs/                          # Execution logs
@@ -55,21 +56,21 @@
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave:increment "name"` | Plan new feature (PM-led) |
-| `/specweave:do` | Execute tasks from active increment |
-| `/specweave:done 0001` | Close increment (validates gates) |
-| `/specweave:progress` | Show task completion status |
-| `/specweave:validate 0001` | Quality check before closing |
-| `/specweave:sync-tasks` | Sync tasks.md with reality |
-| `/specweave:sync-docs update` | Sync to living docs |
+| `/sw:increment "name"` | Plan new feature (PM-led) |
+| `/sw:do` | Execute tasks from active increment |
+| `/sw:done 0001` | Close increment (validates gates) |
+| `/sw:progress` | Show task completion status |
+| `/sw:validate 0001` | Quality check before closing |
+| `/sw:sync-tasks` | Sync tasks.md with reality |
+| `/sw:sync-docs update` | Sync to living docs |
 
 ### Plugin Commands (when installed)
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave-github:sync 0001` | Sync increment to GitHub issue |
-| `/specweave-jira:sync 0001` | Sync to Jira |
-| `/specweave-ado:sync 0001` | Sync to Azure DevOps |
+| `/sw-github:sync 0001` | Sync increment to GitHub issue |
+| `/sw-jira:sync 0001` | Sync to Jira |
+| `/sw-ado:sync 0001` | Sync to Azure DevOps |
 
 ---
 
@@ -84,7 +85,7 @@ SpecWeave v0.28+ introduces powerful automation that **works differently** in no
 | Feature | Claude Code | Non-Claude Tools |
 |---------|-------------|------------------|
 | **Living Docs Builder** | Auto-runs after init | Use `specweave jobs --follow` to monitor |
-| **Bidirectional Sync** | Pull sync on session start | Run `/specweave:sync-pull` manually |
+| **Bidirectional Sync** | Pull sync on session start | Run `/sw:sync-pull` manually |
 | **Background Jobs** | Automatic with hooks | Monitor with `specweave jobs` CLI |
 | **EDA Hooks** | Auto-detect task completion | Manually update tasks.md + spec.md |
 
@@ -183,9 +184,9 @@ This gives you the SAME experience as Claude Code with MCP, but deterministic an
 # Change: - [ ] AC-US1-01 → - [x] AC-US1-01
 
 # Step 3: Sync to external tools (if configured)
-/specweave:sync-tasks
-/specweave-github:sync <increment-id>   # If GitHub enabled
-/specweave-jira:sync <increment-id>     # If Jira enabled
+/sw:sync-tasks
+/sw-github:sync <increment-id>   # If GitHub enabled
+/sw-jira:sync <increment-id>     # If Jira enabled
 ```
 
 #### 2. After User Story Completion (all ACs satisfied)
@@ -194,25 +195,25 @@ This gives you the SAME experience as Claude Code with MCP, but deterministic an
 # When ALL acceptance criteria for a user story are [x] checked:
 
 # Step 1: Sync to living docs
-/specweave:sync-docs update
+/sw:sync-docs update
 
 # Step 2: Update GitHub/Jira issue status
-/specweave-github:sync <increment-id>
+/sw-github:sync <increment-id>
 ```
 
 #### 3. After Increment Completion
 ```bash
 # Claude hook: PostIncrementDone
-# When running /specweave:done:
+# When running /sw:done:
 
 # Step 1: Validate all tasks complete
-/specweave:validate <increment-id>
+/sw:validate <increment-id>
 
 # Step 2: Sync living docs
-/specweave:sync-docs update
+/sw:sync-docs update
 
 # Step 3: Close external issues
-/specweave-github:close-issue <increment-id>
+/sw-github:close-issue <increment-id>
 ```
 
 #### 4. After Writing to spec.md or tasks.md
@@ -221,10 +222,10 @@ This gives you the SAME experience as Claude Code with MCP, but deterministic an
 # After any edit to spec.md or tasks.md:
 
 # Sync status line cache
-/specweave:sync-tasks
+/sw:sync-tasks
 
 # If external tools configured, sync progress
-/specweave-github:sync <increment-id>
+/sw-github:sync <increment-id>
 ```
 
 #### 5. Bidirectional Sync - PULL from External Tools (NEW in v0.28)
@@ -233,7 +234,7 @@ This gives you the SAME experience as Claude Code with MCP, but deterministic an
 # For non-Claude tools, run manually to catch external changes:
 
 # Pull changes from external tools (status, priority, assignee)
-/specweave:sync-pull
+/sw:sync-pull
 
 # This does:
 # 1. Query ADO/JIRA/GitHub for items changed since last sync
@@ -291,7 +292,7 @@ In non-Claude tools, commands are markdown workflows:
 
 ```bash
 # Find and read command file
-cat plugins/specweave/commands/specweave-increment.md
+cat plugins/specweave/commands/increment.md
 # Follow the workflow steps manually
 ```
 
@@ -303,9 +304,9 @@ cat plugins/specweave/commands/specweave-increment.md
 ├─────────────────────────────────────────────────────────────┤
 │ 1. Update tasks.md: [ ] → [x]                               │
 │ 2. Update spec.md ACs if satisfied: [ ] → [x]               │
-│ 3. Run: /specweave:sync-tasks                               │
-│ 4. Run: /specweave-github:sync <id>  (if GitHub configured) │
-│ 5. If all ACs for US done: /specweave:sync-docs update      │
+│ 3. Run: /sw:sync-tasks                               │
+│ 4. Run: /sw-github:sync <id>  (if GitHub configured) │
+│ 5. If all ACs for US done: /sw:sync-docs update      │
 └─────────────────────────────────────────────────────────────┘
 ```
 
@@ -315,10 +316,10 @@ cat plugins/specweave/commands/specweave-increment.md
 ┌─────────────────────────────────────────────────────────────┐
 │ START OF EVERY SESSION (FOR NON-CLAUDE TOOLS)               │
 ├─────────────────────────────────────────────────────────────┤
-│ 1. Pull external changes: /specweave:sync-pull              │
+│ 1. Pull external changes: /sw:sync-pull              │
 │ 2. Check job status:      specweave jobs                    │
-│ 3. Check progress:        /specweave:progress               │
-│ 4. Continue work:         /specweave:do                     │
+│ 3. Check progress:        /sw:progress               │
+│ 4. Continue work:         /sw:do                     │
 └─────────────────────────────────────────────────────────────┘
 ```
 
@@ -352,12 +353,12 @@ cat plugins/specweave/commands/specweave-increment.md
 
 | Command | What It Does | When to Run |
 |---------|--------------|-------------|
-| `/specweave:sync-tasks` | Recalculates progress from tasks.md | After editing tasks.md |
-| `/specweave:sync-docs update` | Updates living docs from increment | After US complete |
-| `/specweave-github:sync <id>` | Syncs progress to GitHub issue | After each task |
-| `/specweave-github:close-issue <id>` | Closes GitHub issue | On increment done |
-| `/specweave-jira:sync <id>` | Syncs progress to Jira story | After each task |
-| `/specweave-ado:sync <id>` | Syncs to Azure DevOps work item | After each task |
+| `/sw:sync-tasks` | Recalculates progress from tasks.md | After editing tasks.md |
+| `/sw:sync-docs update` | Updates living docs from increment | After US complete |
+| `/sw-github:sync <id>` | Syncs progress to GitHub issue | After each task |
+| `/sw-github:close-issue <id>` | Closes GitHub issue | On increment done |
+| `/sw-jira:sync <id>` | Syncs progress to Jira story | After each task |
+| `/sw-ado:sync <id>` | Syncs to Azure DevOps work item | After each task |
 
 ### Complete Sync Flow (Non-Claude Tools)
 
@@ -378,19 +379,19 @@ TASK COMPLETED
      │
      ▼
 ┌─────────────────────────────┐
-│ 3. /specweave:sync-tasks    │
+│ 3. /sw:sync-tasks    │
 │    Updates progress cache   │
 └─────────────────────────────┘
      │
      ▼
 ┌─────────────────────────────┐
-│ 4. /specweave-github:sync   │
+│ 4. /sw-github:sync   │
 │    Updates GitHub issue     │
 └─────────────────────────────┘
      │
      ▼ (if all ACs for US done)
 ┌─────────────────────────────┐
-│ 5. /specweave:sync-docs     │
+│ 5. /sw:sync-docs     │
 │    Updates living docs      │
 └─────────────────────────────┘
 ```
@@ -410,26 +411,21 @@ TASK COMPLETED
 
 ## Context Loading {#context-loading}
 
-### Why Context Manifests Matter
+### Efficient Context Management
 
 ```
-Without manifest: Load all docs (50k tokens) → Crash risk
-With manifest:    Load relevant files (5k tokens) → 90% savings
+Read only what's needed for the current task:
+- Active increment: spec.md, tasks.md (always)
+- Supporting docs: only when referenced in tasks
+- Living docs: load per-US when implementing
 ```
 
-### Using context-manifest.yaml
+### Token-Efficient Approach
 
-```yaml
-# .specweave/increments/0001-feature/context-manifest.yaml
-spec_sections:
-  - .specweave/docs/internal/strategy/prd.md
-  - .specweave/docs/internal/architecture/hld.md
-documentation:
-  - .specweave/docs/internal/specs/default/relevant-spec.md
-max_context_tokens: 10000
-```
-
-**Rule**: Read context-manifest.yaml FIRST. Only load files listed there.
+1. Start with increment's `tasks.md` - contains current task list
+2. Reference `spec.md` for acceptance criteria
+3. Load living docs only when needed for context
+4. Avoid loading entire documentation trees
 
 ---
 
@@ -439,10 +435,10 @@ max_context_tokens: 10000
 .specweave/
 ├── increments/           # Feature increments (0001-9999)
 │   └── 0001-feature/
+│       ├── metadata.json # Increment metadata - REQUIRED
 │       ├── spec.md       # WHAT & WHY (user stories, ACs)
-│       ├── plan.md       # HOW (architecture, APIs)
-│       ├── tasks.md      # Task checklist with test plans
-│       └── context-manifest.yaml  # Files to load
+│       ├── plan.md       # HOW (architecture, APIs) - optional
+│       └── tasks.md      # Task checklist with test plans
 ├── docs/internal/
 │   ├── strategy/         # PRD, business requirements
 │   ├── specs/            # Living docs (extracted user stories)
@@ -521,10 +517,10 @@ AI: [Creates .specweave/increments/0001-auth/spec.md, plan.md, tasks.md]
 
 ### Creating Increment
 1. `mkdir -p .specweave/increments/0001-feature`
-2. Create `spec.md` (WHAT/WHY, user stories, ACs)
-3. Create `plan.md` (HOW, architecture, APIs)
+2. Create `metadata.json` (increment metadata) - **MUST be FIRST**
+3. Create `spec.md` (WHAT/WHY, user stories, ACs)
 4. Create `tasks.md` (task checklist with tests)
-5. Create `context-manifest.yaml` (selective loading)
+5. Optional: Create `plan.md` (HOW, architecture) for complex features
 
 ### Completing Tasks
 1. Implement the task
@@ -533,7 +529,7 @@ AI: [Creates .specweave/increments/0001-auth/spec.md, plan.md, tasks.md]
 4. Sync to external trackers if enabled
 
 ### Closing Increment
-1. Run `/specweave:done 0001`
+1. Run `/sw:done 0001`
 2. PM validates 3 gates (tasks, tests, docs)
 3. Living docs synced automatically
 4. GitHub issue closed (if enabled)
@@ -544,9 +540,9 @@ AI: [Creates .specweave/increments/0001-auth/spec.md, plan.md, tasks.md]
 
 | Command | Plugin |
 |---------|--------|
-| `/specweave-github:sync` | GitHub sync |
-| `/specweave-jira:sync` | Jira sync |
-| `/specweave-ado:sync` | Azure DevOps |
+| `/sw-github:sync` | GitHub sync |
+| `/sw-jira:sync` | Jira sync |
+| `/sw-ado:sync` | Azure DevOps |
 
 ---
 
@@ -559,7 +555,7 @@ AI: [Creates .specweave/increments/0001-auth/spec.md, plan.md, tasks.md]
 ```bash
 # Find and read the command file
 ls plugins/specweave/commands/
-cat plugins/specweave/commands/specweave-increment.md
+cat plugins/specweave/commands/increment.md
 # Follow the workflow steps manually
 ```
 
@@ -569,9 +565,9 @@ cat plugins/specweave/commands/specweave-increment.md
 
 **Solution** (run after EVERY task in non-Claude tools):
 ```bash
-/specweave:sync-tasks                  # Update tasks.md
-/specweave:sync-docs update            # Sync living docs
-/specweave-github:sync <increment-id>  # Sync to GitHub
+/sw:sync-tasks                  # Update tasks.md
+/sw:sync-docs update            # Sync living docs
+/sw-github:sync <increment-id>  # Sync to GitHub
 ```
 
 ### Root Folder Polluted
@@ -593,18 +589,18 @@ mv *.md .specweave/increments/$CURRENT/reports/
 **Status**: [ ] pending  →  **Status**: [x] completed
 ```
 
-Or run: `/specweave:sync-tasks`
+Or run: `/sw:sync-tasks`
 
 ### Context Explosion / Crashes
 
 **Symptoms**: Tool crashes 10-50s after start
 
-**Causes**: Loading too many files, no context manifest
+**Causes**: Loading too many files at once
 
 **Fix**:
-1. Create `context-manifest.yaml` in increment folder
-2. List only files needed for current task
-3. Never load entire `.specweave/docs/` folder
+1. Load only the active increment's spec.md and tasks.md
+2. Reference living docs only when needed for specific tasks
+3. Never load entire `.specweave/docs/` folder at once
 
 ### Skills/Agents Not Activating
 

package/src/templates/CLAUDE.md.template

@@ -43,21 +43,21 @@ Edit("spec.md", "- [ ] **AC-US1-01**", "- [x] **AC-US1-01**");
 ## Core Workflow
 
 ```
-/specweave:increment "feature" → /specweave:do → /specweave:progress → /specweave:done 0001
+/sw:increment "feature" → /sw:do → /sw:progress → /sw:done 0001
 ```
 
 | Command | Purpose |
 |---------|---------|
-| `/specweave:increment "X"` | Plan new feature |
-| `/specweave:do` | Execute implementation |
-| `/specweave:progress` | Check status |
-| `/specweave:validate 0001` | Quality check |
-| `/specweave:done 0001` | Close increment |
+| `/sw:increment "X"` | Plan new feature |
+| `/sw:do` | Execute implementation |
+| `/sw:progress` | Check status |
+| `/sw:validate 0001` | Quality check |
+| `/sw:done 0001` | Close increment |
 
 **Sync Commands** (if plugins installed):
-- `/specweave-github:sync` - Sync to GitHub Issues
-- `/specweave-jira:sync` - Sync to Jira
-- `/specweave-ado:sync` - Sync to Azure DevOps
+- `/sw-github:sync` - Sync to GitHub Issues
+- `/sw-jira:sync` - Sync to Jira
+- `/sw-ado:sync` - Sync to Azure DevOps
 
 ---
 
@@ -67,10 +67,10 @@ Edit("spec.md", "- [ ] **AC-US1-01**", "- [x] **AC-US1-01**");
 .specweave/
 ├── increments/              # Feature increments (####-name/)
 │   └── 0001-feature/
+│       ├── metadata.json    # Increment metadata - REQUIRED
 │       ├── spec.md          # WHAT & WHY
-│       ├── plan.md          # HOW
-│       ├── tasks.md         # Checklist with embedded tests
-│       └── context-manifest.yaml  # Selective loading
+│       ├── plan.md          # HOW (optional)
+│       └── tasks.md         # Checklist with embedded tests
 ├── docs/internal/
 │   ├── strategy/            # Business specs
 │   ├── specs/               # Living docs (post-completion)
@@ -96,12 +96,16 @@ Edit("spec.md", "- [ ] **AC-US1-01**", "- [x] **AC-US1-01**");
 
 ---
 
-## Context Loading (Token Savings)
+## Increment Files
 
-**ALWAYS read `context-manifest.yaml` first!** Load only files listed there.
-- Full specs: 50k tokens
-- Manifest files: 5k tokens
-- **Savings: 90%**
+**Required files** for every increment:
+1. `metadata.json` - Increment metadata (status, type, dates) - MUST create FIRST
+2. `spec.md` - User stories, acceptance criteria
+3. `tasks.md` - Implementation tasks with embedded tests
+
+**Optional**:
+- `plan.md` - Technical design (for complex features only)
+- `reports/` - Completion reports, analyses
 
 ---
 
@@ -180,8 +184,8 @@ After **EVERY task completion**, hooks automatically:
 | Skills not activating | Restart Claude Code |
 | Commands not found | Check plugin: `/plugin list --installed` |
 | Root polluted | Move files to increment folders |
-| Tasks out of sync | `/specweave:sync-tasks` |
-| Can't find increment | `/specweave:status` |
+| Tasks out of sync | `/sw:sync-tasks` |
+| Can't find increment | `/sw:status` |
 
 ---
 

package/dist/src/cli/commands/switch-project.d.ts

@@ -1,13 +0,0 @@
-/**
- * CLI Command: /specweave:switch-project
- *
- * Switch active project for increment planning
- */
-export declare function switchProject(projectRoot: string, projectId?: string): Promise<void>;
-/**
- * Get current active project
- *
- * @param projectRoot - Project root directory
- */
-export declare function getCurrentProject(projectRoot: string): Promise<void>;
-//# sourceMappingURL=switch-project.d.ts.map

package/dist/src/cli/commands/switch-project.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"switch-project.d.ts","sourceRoot":"","sources":["../../../../src/cli/commands/switch-project.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAYH,wBAAsB,aAAa,CACjC,WAAW,EAAE,MAAM,EACnB,SAAS,CAAC,EAAE,MAAM,GACjB,OAAO,CAAC,IAAI,CAAC,CAmDf;AAED;;;;GAIG;AACH,wBAAsB,iBAAiB,CAAC,WAAW,EAAE,MAAM,GAAG,OAAO,CAAC,IAAI,CAAC,CAkB1E"}

package/dist/src/cli/commands/switch-project.js

@@ -1,78 +0,0 @@
-/**
- * CLI Command: /specweave:switch-project
- *
- * Switch active project for increment planning
- */
-import { ProjectManager } from '../../core/project/project-manager.js';
-import { ConfigManager } from '../../core/config-manager.js';
-import { listProjects } from './init-multiproject.js';
-// NOTE: This CLI switch-project command is primarily user-facing output (console.log/console.error).
-// All console.* calls in this file are legitimate user-facing exceptions
-// as defined in CONTRIBUTING.md (project switching status, confirmations, errors).
-// Logger infrastructure available for future internal debug logs if needed.
-export async function switchProject(projectRoot, projectId) {
-    const projectManager = new ProjectManager(projectRoot);
-    const configManager = new ConfigManager(projectRoot);
-    const config = configManager.load();
-    // Check if multi-project mode is enabled
-    if (!config.multiProject?.enabled) {
-        console.error('\n❌ Multi-project mode not enabled');
-        console.error('   Run /specweave:init-multiproject first\n');
-        return;
-    }
-    // If no project ID provided, list projects and prompt
-    if (!projectId) {
-        await listProjects(projectRoot);
-        console.log('Usage: /specweave:switch-project <project-id>\n');
-        return;
-    }
-    try {
-        // Validate project exists
-        const project = projectManager.getProjectById(projectId);
-        if (!project) {
-            const allProjects = projectManager.getAllProjects();
-            const availableIds = allProjects.map(p => p.projectId).join(', ');
-            console.error(`\n❌ Project '${projectId}' not found`);
-            console.error(`   Available projects: ${availableIds}\n`);
-            return;
-        }
-        // Check if already active
-        const currentActive = projectManager.getActiveProject();
-        if (currentActive.projectId === projectId) {
-            console.log(`\nℹ️  Project '${project.projectName}' is already active\n`);
-            return;
-        }
-        // Switch project
-        await projectManager.switchProject(projectId);
-        console.log(`\n✅ Switched to project: ${project.projectName} (${projectId})`);
-        console.log('\nℹ️  Future increments will use:');
-        console.log(`   - ${projectManager.getSpecsPath(projectId).replace(projectRoot, '')}`);
-        console.log(`   - ${projectManager.getModulesPath(projectId).replace(projectRoot, '')}`);
-        console.log(`   - ${projectManager.getTeamPath(projectId).replace(projectRoot, '')}\n`);
-    }
-    catch (error) {
-        console.error(`\n❌ Failed to switch project: ${error instanceof Error ? error.message : String(error)}\n`);
-        throw error;
-    }
-}
-/**
- * Get current active project
- *
- * @param projectRoot - Project root directory
- */
-export async function getCurrentProject(projectRoot) {
-    const projectManager = new ProjectManager(projectRoot);
-    const project = projectManager.getActiveProject();
-    console.log('\n📋 Current Active Project:\n');
-    console.log(`  ID: ${project.projectId}`);
-    console.log(`  Name: ${project.projectName}`);
-    console.log(`  Path: ${project.projectPath}`);
-    if (project.techStack.length > 0) {
-        console.log(`  Tech Stack: ${project.techStack.join(', ')}`);
-    }
-    if (project.keywords.length > 0) {
-        console.log(`  Keywords: ${project.keywords.join(', ')}`);
-    }
-    console.log('');
-}
-//# sourceMappingURL=switch-project.js.map

package/dist/src/cli/commands/switch-project.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"switch-project.js","sourceRoot":"","sources":["../../../../src/cli/commands/switch-project.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAAE,cAAc,EAAE,MAAM,uCAAuC,CAAC;AACvE,OAAO,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAC7D,OAAO,EAAE,YAAY,EAAE,MAAM,wBAAwB,CAAC;AAGtD,qGAAqG;AACrG,yEAAyE;AACzE,mFAAmF;AACnF,4EAA4E;AAE5E,MAAM,CAAC,KAAK,UAAU,aAAa,CACjC,WAAmB,EACnB,SAAkB;IAElB,MAAM,cAAc,GAAG,IAAI,cAAc,CAAC,WAAW,CAAC,CAAC;IACvD,MAAM,aAAa,GAAG,IAAI,aAAa,CAAC,WAAW,CAAC,CAAC;IACrD,MAAM,MAAM,GAAG,aAAa,CAAC,IAAI,EAAE,CAAC;IAEpC,yCAAyC;IACzC,IAAI,CAAC,MAAM,CAAC,YAAY,EAAE,OAAO,EAAE,CAAC;QAClC,OAAO,CAAC,KAAK,CAAC,oCAAoC,CAAC,CAAC;QACpD,OAAO,CAAC,KAAK,CAAC,6CAA6C,CAAC,CAAC;QAC7D,OAAO;IACT,CAAC;IAED,sDAAsD;IACtD,IAAI,CAAC,SAAS,EAAE,CAAC;QACf,MAAM,YAAY,CAAC,WAAW,CAAC,CAAC;QAChC,OAAO,CAAC,GAAG,CAAC,iDAAiD,CAAC,CAAC;QAC/D,OAAO;IACT,CAAC;IAED,IAAI,CAAC;QACH,0BAA0B;QAC1B,MAAM,OAAO,GAAG,cAAc,CAAC,cAAc,CAAC,SAAS,CAAC,CAAC;QACzD,IAAI,CAAC,OAAO,EAAE,CAAC;YACb,MAAM,WAAW,GAAG,cAAc,CAAC,cAAc,EAAE,CAAC;YACpD,MAAM,YAAY,GAAG,WAAW,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,SAAS,CAAC,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;YAElE,OAAO,CAAC,KAAK,CAAC,gBAAgB,SAAS,aAAa,CAAC,CAAC;YACtD,OAAO,CAAC,KAAK,CAAC,0BAA0B,YAAY,IAAI,CAAC,CAAC;YAC1D,OAAO;QACT,CAAC;QAED,0BAA0B;QAC1B,MAAM,aAAa,GAAG,cAAc,CAAC,gBAAgB,EAAE,CAAC;QACxD,IAAI,aAAa,CAAC,SAAS,KAAK,SAAS,EAAE,CAAC;YAC1C,OAAO,CAAC,GAAG,CAAC,kBAAkB,OAAO,CAAC,WAAW,uBAAuB,CAAC,CAAC;YAC1E,OAAO;QACT,CAAC;QAED,iBAAiB;QACjB,MAAM,cAAc,CAAC,aAAa,CAAC,SAAS,CAAC,CAAC;QAE9C,OAAO,CAAC,GAAG,CAAC,4BAA4B,OAAO,CAAC,WAAW,KAAK,SAAS,GAAG,CAAC,CAAC;QAC9E,OAAO,CAAC,GAAG,CAAC,mCAAmC,CAAC,CAAC;QACjD,OAAO,CAAC,GAAG,CAAC,QAAQ,cAAc,CAAC,YAAY,CAAC,SAAS,CAAC,CAAC,OAAO,CAAC,WAAW,EAAE,EAAE,CAAC,EAAE,CAAC,CAAC;QACvF,OAAO,CAAC,GAAG,CAAC,QAAQ,cAAc,CAAC,cAAc,CAAC,SAAS,CAAC,CAAC,OAAO,CAAC,WAAW,EAAE,EAAE,CAAC,EAAE,CAAC,CAAC;QACzF,OAAO,CAAC,GAAG,CAAC,QAAQ,cAAc,CAAC,WAAW,CAAC,SAAS,CAAC,CAAC,OAAO,CAAC,WAAW,EAAE,EAAE,CAAC,IAAI,CAAC,CAAC;IAE1F,CAAC;IAAC,OAAO,KAAK,EAAE,CAAC;QACf,OAAO,CAAC,KAAK,CAAC,iCAAiC,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,MAAM,CAAC,KAAK,CAAC,IAAI,CAAC,CAAC;QAC3G,MAAM,KAAK,CAAC;IACd,CAAC;AACH,CAAC;AAED;;;;GAIG;AACH,MAAM,CAAC,KAAK,UAAU,iBAAiB,CAAC,WAAmB;IACzD,MAAM,cAAc,GAAG,IAAI,cAAc,CAAC,WAAW,CAAC,CAAC;IACvD,MAAM,OAAO,GAAG,cAAc,CAAC,gBAAgB,EAAE,CAAC;IAElD,OAAO,CAAC,GAAG,CAAC,gCAAgC,CAAC,CAAC;IAC9C,OAAO,CAAC,GAAG,CAAC,SAAS,OAAO,CAAC,SAAS,EAAE,CAAC,CAAC;IAC1C,OAAO,CAAC,GAAG,CAAC,WAAW,OAAO,CAAC,WAAW,EAAE,CAAC,CAAC;IAC9C,OAAO,CAAC,GAAG,CAAC,WAAW,OAAO,CAAC,WAAW,EAAE,CAAC,CAAC;IAE9C,IAAI,OAAO,CAAC,SAAS,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QACjC,OAAO,CAAC,GAAG,CAAC,iBAAiB,OAAO,CAAC,SAAS,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAC/D,CAAC;IAED,IAAI,OAAO,CAAC,QAAQ,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAChC,OAAO,CAAC,GAAG,CAAC,eAAe,OAAO,CAAC,QAAQ,CAAC,IAAI,CAAC,IAAI,CAAC,EAAE,CAAC,CAAC;IAC5D,CAAC;IAED,OAAO,CAAC,GAAG,CAAC,EAAE,CAAC,CAAC;AAClB,CAAC"}

package/plugins/specweave/commands/specweave-init-multiproject.md

@@ -1,146 +0,0 @@
----
-name: specweave:init-multiproject
-description: Initialize multi-project mode for SpecWeave. Enables organizing specs, modules, and team docs by project/team. Auto-migrates existing specs/ to projects/default/.
----
-
-# Initialize Multi-Project Mode
-
-Enable multi-project mode to organize documentation by project or team.
-
-## What This Does
-
-1. **Auto-migrates** existing `specs/` to `projects/default/specs/` (transparent, no behavior change)
-2. **Enables multi-project mode** in config (optional)
-3. **Creates additional projects** (optional, interactive prompts)
-4. **Sets up folder structure** for each project (specs/, modules/, team/, architecture/, legacy/)
-
-## Usage
-
-```bash
-/specweave:init-multiproject
-```
-
-## Interactive Prompts
-
-1. **Enable multi-project mode?** (yes/no)
-   - No: Stay in single-project mode (uses `projects/default/` but `multiProject.enabled = false`)
-   - Yes: Enable multi-project mode (allows multiple projects)
-
-2. **Create additional projects?** (yes/no, only if multi-project enabled)
-   - If yes, enter project details:
-     - Project ID (kebab-case, e.g., `web-app`)
-     - Project name (e.g., "Web Application")
-     - Description
-     - Tech stack (comma-separated)
-     - Team name
-
-## Examples
-
-### Example 1: Single Project (Default)
-
-```bash
-/specweave:init-multiproject
-
-# Prompts:
-# - Enable multi-project mode? → No
-
-# Result:
-# ✅ Auto-migrated to projects/default/
-# ℹ️  Still in single-project mode
-# ℹ️  All operations use projects/default/ automatically
-```
-
-### Example 2: Multi-Project (Enterprise)
-
-```bash
-/specweave:init-multiproject
-
-# Prompts:
-# - Enable multi-project mode? → Yes
-# - Create additional projects? → Yes
-#   - Project ID: web-app
-#   - Name: Web Application
-#   - Description: Customer-facing web app
-#   - Tech stack: React, TypeScript, Node.js
-#   - Team: Frontend Team
-#
-#   Create another project? → Yes
-#   - Project ID: platform-infra
-#   - Name: Platform Infrastructure
-#   - ...
-
-# Result:
-# ✅ Created projects/web-app/
-# ✅ Created projects/platform-infra/
-# ✅ Multi-project mode enabled
-# ℹ️  Use /specweave:switch-project to change active project
-```
-
-## Folder Structure Created
-
-For each project:
-
-```
-.specweave/docs/internal/projects/{project-id}/
-├── README.md              # Project overview
-├── specs/                 # Living docs specs (spec-001, spec-002, ...)
-├── modules/               # Module-level docs (auth, payments, etc.)
-├── team/                  # Team playbooks (onboarding, conventions)
-├── architecture/          # Project-specific architecture (optional)
-│   └── adr/               # Architecture Decision Records
-└── legacy/                # Brownfield imported docs
-```
-
-## When to Use
-
-### Single Project Mode
-- Small projects or startups
-- One team, one codebase
-- Simple organizational structure
-
-### Multi-Project Mode
-- Multiple teams or repos
-- Microservices architecture
-- Platform engineering managing multiple projects
-- Different tech stacks per team
-
-## Integration with External Sync
-
-Multi-project mode integrates with external sync (GitHub, JIRA, ADO):
-
-```json
-{
-  "multiProject": {
-    "projects": [{
-      "id": "web-app",
-      "syncProfiles": ["web-app-github", "web-app-jira"]
-    }]
-  }
-}
-```
-
-Each project can link to specific sync profiles for external tracking.
-
-## What Happens to Existing Specs?
-
-**Automatic Migration**:
-1. Existing `specs/` copied to `projects/default/specs/`
-2. Old `specs/` renamed to `specs.old/` (backup)
-3. Config updated with `multiProject` section
-4. **No behavior change** - all operations still work
-
-**Rollback** (if needed):
-```bash
-# Restore from backup
-npm run specweave:rollback-migration
-```
-
-## See Also
-
-- `/specweave:switch-project` - Change active project
-- `/specweave:import-docs` - Import brownfield docs
-- [Multi-Project Guide](https://docs.spec-weave.com/guides/multi-project-setup)
-
----
-
-**Implementation**: `src/cli/commands/init-multiproject.ts`