specweave 0.7.1 → 0.8.2

package/plugins/specweave/commands/specweave-import-docs.md

@@ -0,0 +1,212 @@
+---
+name: specweave:import-docs
+description: Import brownfield documentation from Notion exports, Confluence, GitHub Wiki, or any markdown folder. Automatically classifies files as specs, modules, team docs, or legacy.
+---
+
+# Import Brownfield Documentation
+
+Import existing documentation from Notion exports, Confluence, GitHub Wiki, or any markdown folder.
+
+## What This Does
+
+1. **Analyzes markdown files** in source directory (recursively)
+2. **Classifies files** based on content:
+   - **Specs** - Contains "user story", "acceptance criteria", "feature"
+   - **Modules** - Contains "module", "component", "architecture"
+   - **Team** - Contains "onboarding", "convention", "workflow"
+   - **Legacy** - Everything else (no strong match)
+3. **Copies files** to appropriate destinations
+4. **Creates migration report** with classification details
+5. **Updates config** with import history
+
+## Usage
+
+```bash
+/specweave:import-docs <source-path> [options]
+```
+
+### Options
+
+- `--source=<type>` - Source type: `notion`, `confluence`, `wiki`, `custom` (required)
+- `--project=<id>` - Target project ID (default: active project)
+- `--preserve-structure` - Preserve original folder structure
+- `--dry-run` - Preview classification without importing
+
+## Examples
+
+### Example 1: Notion Export
+
+```bash
+# Export Notion workspace to /tmp/notion-export/
+# Then import:
+
+/specweave:import-docs /tmp/notion-export/ --source=notion
+
+# Result:
+# 📊 Analysis Results:
+#    Total files: 47
+#    - Specs: 12 files → specs/
+#    - Modules: 18 files → modules/
+#    - Team docs: 5 files → team/
+#    - Legacy: 12 files → legacy/notion/
+# ✅ Import complete!
+```
+
+### Example 2: Confluence Export
+
+```bash
+/specweave:import-docs /path/to/confluence/ --source=confluence --project=web-app
+
+# Imports to: projects/web-app/specs/, modules/, team/, legacy/confluence/
+```
+
+### Example 3: Dry Run (Preview)
+
+```bash
+/specweave:import-docs /tmp/docs/ --source=custom --dry-run
+
+# Shows classification without importing files
+# Use this to preview results before actual import
+```
+
+### Example 4: Preserve Structure
+
+```bash
+/specweave:import-docs /path/to/wiki/ --source=wiki --preserve-structure
+
+# Preserves original folder structure:
+# legacy/wiki/engineering/backend/auth.md
+# legacy/wiki/engineering/frontend/components.md
+```
+
+## Supported Sources
+
+### Notion
+- **Export Format**: Markdown & CSV
+- **Steps**:
+  1. In Notion: Settings → Export → Export all workspace content
+  2. Choose "Markdown & CSV" format
+  3. Download ZIP file
+  4. Extract to folder (e.g., `/tmp/notion-export/`)
+  5. Run import command
+
+### Confluence
+- **Export Format**: HTML or Markdown
+- **Steps**:
+  1. Space tools → Content Tools → Export
+  2. Choose HTML or Markdown
+  3. Extract exported files
+  4. Run import command
+
+### GitHub Wiki
+- **Export Format**: Git repository
+- **Steps**:
+  1. Clone wiki: `git clone https://github.com/user/repo.wiki.git`
+  2. Run import command on cloned directory
+
+### Custom (Any Markdown)
+- Any folder containing `.md` or `.markdown` files
+- Recursive search through subdirectories
+
+## Classification Algorithm
+
+Files are classified using keyword analysis:
+
+### Specs (70%+ confidence)
+- Keywords: "user story", "acceptance criteria", "feature", "requirement"
+- Patterns: "As a [user], I want [goal]", "Given-When-Then"
+- Example: Feature specs, PRDs, user stories
+
+### Modules (70%+ confidence)
+- Keywords: "module", "component", "service", "architecture"
+- Patterns: API docs, technical design, integration points
+- Example: Auth module, payment processing, ML pipeline
+
+### Team (70%+ confidence)
+- Keywords: "onboarding", "convention", "workflow", "pr process"
+- Patterns: Team processes, coding standards, deployment guides
+- Example: Onboarding guide, code review checklist
+
+### Legacy (<70% confidence)
+- No strong match to above categories
+- Uncertain classification
+- Requires manual review
+
+## Destination Folders
+
+Files are imported to:
+
+```
+.specweave/docs/internal/projects/{project}/
+├── specs/              ← Specs (spec keywords)
+├── modules/            ← Modules (module keywords)
+├── team/               ← Team docs (team keywords)
+└── legacy/{source}/    ← Legacy (uncertain classification)
+    ├── notion/
+    ├── confluence/
+    ├── wiki/
+    └── custom/
+```
+
+## Migration Report
+
+After import, a detailed report is generated:
+
+**Location**: `.specweave/docs/internal/projects/{project}/legacy/README.md`
+
+**Contents**:
+- Import summary (counts per category)
+- Classification analysis (with confidence scores)
+- List of imported files
+- Next steps and recommendations
+
+## Configuration Updates
+
+Import history is tracked in `.specweave/config.json`:
+
+```json
+{
+  "brownfield": {
+    "importHistory": [{
+      "source": "notion",
+      "workspace": "acme-corp",
+      "importedAt": "2025-11-06T10:30:00Z",
+      "project": "web-app",
+      "filesImported": 47,
+      "destination": ".specweave/docs/internal/projects/web-app/legacy/notion/"
+    }]
+  }
+}
+```
+
+## After Import
+
+1. **Review classification** - Check migration report
+2. **Move misclassified files** - Use file manager or git
+3. **Update spec numbers** - Rename to `spec-NNN-name.md`
+4. **Clean up legacy** - Delete obsolete content
+5. **Update references** - Fix broken links
+
+## When to Use
+
+- **Migrating from Notion** to SpecWeave
+- **Consolidating wikis** from GitHub, Confluence, etc.
+- **Onboarding brownfield projects** with existing documentation
+- **Merging multiple doc sources** into single SpecWeave instance
+
+## Limitations
+
+- Only markdown files (.md, .markdown) supported
+- No direct API integration (use exports)
+- Classification is heuristic (80%+ accuracy target)
+- Manual review recommended for low-confidence files
+
+## See Also
+
+- `/specweave:init-multiproject` - Set up multi-project mode first
+- [Brownfield Import Guide](https://docs.spec-weave.com/guides/brownfield-import)
+- [Migration Best Practices](https://docs.spec-weave.com/guides/migration-best-practices)
+
+---
+
+**Implementation**: `src/cli/commands/import-docs.ts`

package/plugins/specweave/commands/specweave-increment.md

@@ -1,5 +1,5 @@
 ---
-name: increment
+name: specweave:increment
 description: Plan new Product Increment - PM-led process (market research, spec, plan, auto-generate tasks). Auto-closes previous increment if PM gates pass.
 ---
 
@@ -199,11 +199,11 @@ if (activeCount >= limits.hardCap) {
 
   console.log(chalk.blue('\n💡 You MUST complete or pause existing work first:\n'));
   console.log(chalk.white('1️⃣  Complete an increment:'));
-  console.log(chalk.dim('   /done <id>\n'));
+  console.log(chalk.dim('   /specweave:done <id>\n'));
   console.log(chalk.white('2️⃣  Pause an increment:'));
-  console.log(chalk.dim('   /pause <id> --reason="..."\n'));
+  console.log(chalk.dim('   /specweave:pause <id> --reason="..."\n'));
   console.log(chalk.white('3️⃣  Check status:'));
-  console.log(chalk.dim('   /status\n'));
+  console.log(chalk.dim('   /specweave:status\n'));
 
   console.log(chalk.yellow('📝 Multiple hotfixes? Combine them into ONE increment!'));
   console.log(chalk.dim('   Example: 0009-security-fixes (SQL + XSS + CSRF)\n'));
@@ -267,7 +267,7 @@ if (activeCount >= limits.maxActiveIncrements) {
 
     if (choice === 'complete') {
       console.log(chalk.green('\n✅ Smart choice! Finish current work first.\n'));
-      console.log(chalk.dim('Use /do to continue work\n'));
+      console.log(chalk.dim('Use /specweave:do to continue work\n'));
       process.exit(0);
     } else if (choice === 'pause') {
       console.log(chalk.blue('\n⏸️  Pausing current increment...\n'));
@@ -311,13 +311,13 @@ Active increments:
 💡 You MUST complete or pause existing work first:
 
 1️⃣  Complete an increment:
-   /done <id>
+   /specweave:done <id>
 
 2️⃣  Pause an increment:
-   /pause <id> --reason="..."
+   /specweave:pause <id> --reason="..."
 
 3️⃣  Check status:
-   /status
+   /specweave:status
 
 📝 Multiple hotfixes? Combine them into ONE increment!
    Example: 0009-security-fixes (SQL + XSS + CSRF)
@@ -353,7 +353,7 @@ Choose an option: 1
 
 ✅ Smart choice! Finish current work first.
 
-Use /do to continue work
+Use /specweave:do to continue work
 ```
 
 **Example Output - Emergency Interrupt (hotfix)**:
@@ -610,7 +610,7 @@ This will:
 
 Next steps:
 1. Review the increment plan and strategic docs
-2. Start implementation: /do 0003
+2. Start implementation: /specweave:do 0003
 3. (Optional) Sync to GitHub: /sync-github
     ```
 

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

@@ -0,0 +1,146 @@
+---
+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`

package/plugins/specweave/commands/specweave-next.md

@@ -1,5 +1,5 @@
 ---
-name: next
+name: specweave:next
 description: Smart increment transition - auto-close current if ready, intelligently suggest next work (backlog or new feature)
 ---
 
@@ -12,7 +12,7 @@ You are helping the user complete their current increment and move to the next o
 ## Usage
 
 ```bash
-/next
+/specweave:next
 ```
 
 **No arguments needed** - the command intelligently handles the transition.
@@ -21,7 +21,7 @@ You are helping the user complete their current increment and move to the next o
 
 ## What This Does
 
-The `/next` command is your **workflow continuation** command. It:
+The `/specweave:next` command is your **workflow continuation** command. It:
 
 1. **Validates current increment** - Checks if work is complete
 2. **Auto-closes if ready** - PM validates and closes automatically
@@ -257,7 +257,7 @@ What would you like to do? [A/B/C]
       Example: /specweave inc "Admin dashboard"
 
    B. Check existing ideas → Look in .specweave/increments/_backlog/
-      If you have ideas saved, promote them with /inc
+      If you have ideas saved, promote them with /specweave:increment
 
    C. Review roadmap → See .specweave/docs/internal/strategy/roadmap.md
 
@@ -272,7 +272,7 @@ What would you like to do? [A/B/C]
 
 **User**:
 ```bash
-/next
+/specweave:next
 ```
 
 **Output**:
@@ -315,7 +315,7 @@ Next Action: Run `/specweave do 0002` to begin
 
 **User**:
 ```bash
-/next
+/specweave:next
 ```
 
 **Output**:
@@ -357,7 +357,7 @@ Next Action: Run `/specweave do 0001` to resume at T010
 
 **User**:
 ```bash
-/next
+/specweave:next
 ```
 
 **Output**:
@@ -397,7 +397,7 @@ Options:
 
 **User**:
 ```bash
-/next
+/specweave:next
 ```
 
 **Output**:
@@ -431,15 +431,15 @@ Your choice? [A/B/C] _
 
 | Command | Purpose | When to Use |
 |---------|---------|-------------|
-| `/specweave inc "feature"` | Create NEW increment with specific feature | Starting fresh work |
-| `/specweave do` | Execute tasks in increment | Implementing planned work |
-| `/specweave progress` | Check status (no action) | Quick status check |
-| `/done` | Explicitly close increment | Manual closure with validation |
-| `/next` ⭐ | **Smart transition** (close + suggest next) | **Natural workflow continuation** |
+| `/specweave:increment "feature"` | Create NEW increment with specific feature | Starting fresh work |
+| `/specweave:do` | Execute tasks in increment | Implementing planned work |
+| `/specweave:progress` | Check status (no action) | Quick status check |
+| `/specweave:done` | Explicitly close increment | Manual closure with validation |
+| `/specweave:next` ⭐ | **Smart transition** (close + suggest next) | **Natural workflow continuation** |
 
-**Why `/next` is special**:
+**Why `/specweave:next` is special**:
 - ✅ Combines validation + closure + suggestion in one command
-- ✅ No need to remember `/done` then `/inc` or `/specweave do`
+- ✅ No need to remember `/specweave:done` then `/specweave:increment` sequence
 - ✅ Intelligent suggestions (backlog, WIP, new work)
 - ✅ User stays in control (never forces actions)
 - ✅ Natural "what's next?" workflow
@@ -448,7 +448,7 @@ Your choice? [A/B/C] _
 
 ## Best Practices
 
-1. **Run `/next` when you feel done** - It validates completion and suggests next steps
+1. **Run `/specweave:next` when you feel done** - It validates completion and suggests next steps
 2. **Trust the PM validation** - If gates fail, there's unfinished work
 3. **Follow recommendations** - Backlog items are already planned
 4. **Keep WIP limit in mind** - Don't force multiple increments

package/plugins/specweave/commands/specweave-pause.md

@@ -1,5 +1,5 @@
 ---
-name: pause
+name: specweave:pause
 description: Pause an active increment (blocked by external dependency, deprioritized)
 usage: /specweave:pause <increment-id> --reason="<reason>"
 ---
@@ -29,7 +29,7 @@ Pause an active increment when:
    - `pausedReason`: User-provided reason
    - `pausedAt`: Current timestamp
 4. **Displays** confirmation message
-5. **Suggests** next actions (/resume to continue)
+5. **Suggests** next actions (`/specweave:resume` to continue)
 
 ---
 
@@ -37,17 +37,17 @@ Pause an active increment when:
 
 ### Pause with reason
 ```bash
-/pause 0006 --reason="Waiting for Stripe API keys"
+/specweave:pause 0006 --reason="Waiting for Stripe API keys"
 
 ✅ Increment 0006 paused
 📝 Reason: Waiting for Stripe API keys
 ⏸️  No longer counts toward active limit
-💡 Resume with: /resume 0006
+💡 Resume with: /specweave:resume 0006
 ```
 
 ### Pause without reason (prompts)
 ```bash
-/pause 0006
+/specweave:pause 0006
 
 ❓ Why are you pausing this increment?
    1. Blocked by external dependency
@@ -59,7 +59,7 @@ Pause an active increment when:
 
 ✅ Increment 0006 paused
 📝 Reason: Blocked by external dependency
-💡 Resume with: /resume 0006
+💡 Resume with: /specweave:resume 0006
 ```
 
 ---
@@ -68,7 +68,7 @@ Pause an active increment when:
 
 ### Already Paused
 ```bash
-/pause 0006 --reason="Different reason"
+/specweave:pause 0006 --reason="Different reason"
 
 ⚠️  Increment 0006 is already paused
    Previous reason: Waiting for Stripe API keys
@@ -82,7 +82,7 @@ Update reason? [Y/n]: y
 
 ### Cannot Pause Completed
 ```bash
-/pause 0005
+/specweave:pause 0005
 
 ❌ Cannot pause increment 0005
    Status: completed
@@ -91,19 +91,19 @@ Update reason? [Y/n]: y
 
 ### Cannot Pause Abandoned
 ```bash
-/pause 0008
+/specweave:pause 0008
 
 ❌ Cannot pause increment 0008
    Status: abandoned
-   Resume it first: /resume 0008
+   Resume it first: /specweave:resume 0008
 ```
 
 ### Increment Not Found
 ```bash
-/pause 9999
+/specweave:pause 9999
 
 ❌ Increment not found: 9999
-💡 Check available increments: /status
+💡 Check available increments: /specweave:status
 ```
 
 ---
@@ -165,10 +165,10 @@ active ──pause──> paused
 
 ## Warning: Stale Paused Increments
 
-Increments paused for **7+ days** trigger warnings in `/status`:
+Increments paused for **7+ days** trigger warnings in `/specweave:status`:
 
 ```bash
-/status
+/specweave:status
 
 ⏸️  Paused (1):
   🔄 0007-stripe-integration [feature]
@@ -177,13 +177,13 @@ Increments paused for **7+ days** trigger warnings in `/status`:
      ⚠️  STALE! Review or abandon?
 
 💡 Actions:
-   /resume 0007  # If unblocked
-   /abandon 0007 # If no longer needed
+   /specweave:resume 0007  # If unblocked
+   /specweave:abandon 0007 # If no longer needed
 ```
 
 ---
 
-**Command**: `/specweave:pause` (or `/pause`)
+**Command**: `/specweave:pause`
 **Plugin**: specweave (core)
 **Version**: v0.7.0+
 **Part of**: Increment 0007 - Smart Status Management

package/plugins/specweave/commands/specweave-progress.md

@@ -1,5 +1,5 @@
 ---
-name: progress
+name: specweave:progress
 description: Show current increment progress, task completion %, PM gate status, and next action
 ---
 
@@ -20,10 +20,10 @@ Shows:
 
 ```bash
 # Check current progress
-/progress
+/specweave:progress
 
 # Show progress for specific increment
-/progress 0001
+/specweave:progress 0001
 ```
 
 ---
@@ -211,9 +211,9 @@ fi
 
 ---
 
-## When to Use `/progress`
+## When to Use `/specweave:progress`
 
-Use `/progress` when you:
+Use `/specweave:progress` when you:
 - ✅ Come back after a break and need context
 - ✅ Want to see overall completion status
 - ✅ Need to know which task to work on next
@@ -225,12 +225,12 @@ Use `/progress` when you:
 **Typical workflow**:
 ```bash
 # Morning: Check what you were working on
-/progress
+/specweave:progress
 
 # Shows: "Active: 0002-payments, Task 5/10 (50%)"
-# Shows: "Next: /do 0002 to resume at T006"
+# Shows: "Next: /specweave:do 0002 to resume at T006"
 
-/do 0002
+/specweave:do 0002
 # Auto-resumes from T006
 ```
 
@@ -238,8 +238,8 @@ Use `/progress` when you:
 
 ## Pro Tips
 
-1. **No increment ID needed** - `/progress` automatically finds active increment
-2. **Smart resume** - `/do` picks up where you left off (no task ID needed)
+1. **No increment ID needed** - `/specweave:progress` automatically finds active increment
+2. **Smart resume** - `/specweave:do` picks up where you left off (no task ID needed)
 3. **WIP limits** - Keep 1-2 increments active max for focus
 4. **Completion %** - P1 tasks weighted higher (they're critical path)
 5. **Time tracking** - Warns if tasks are stuck (>2 hours inactive)