specweave 0.10.1 → 0.12.0

package/.claude-plugin/marketplace.json

@@ -1,6 +1,6 @@
 {
   "name": "specweave",
-  "version": "0.6.1",
+  "version": "0.11.0",
   "description": "SpecWeave - Spec-Driven Development Framework. PM-led planning, intelligent model selection, living documentation, multi-tool support.",
   "owner": {
     "name": "Anton Abyzov",
@@ -12,7 +12,7 @@
       "description": "SpecWeave framework - increment lifecycle, living docs, PM-led planning",
       "source": "./plugins/specweave",
       "category": "development",
-      "version": "0.6.1",
+      "version": "0.11.0",
       "author": {
         "name": "Anton Abyzov",
         "email": "anton@spec-weave.com"
@@ -152,7 +152,7 @@
     },
     {
       "name": "specweave-docs-preview",
-      "description": "Documentation preview - Local Docusaurus server with auto-generated sidebar, hot reload, and beautiful UI. Auto-suggests after first increment. Keywords: docs, preview, documentation, browse docs",
+      "description": "Interactive documentation preview - Launch Docusaurus dev server with hot reload, auto-generated sidebar, Mermaid diagrams. Build static sites for deployment.",
       "source": "./plugins/specweave-docs-preview",
       "category": "productivity",
       "version": "1.0.0",

package/CLAUDE.md

@@ -681,10 +681,10 @@ my-project/
 - ✅ Strategy docs are project-level, not module-level
 - ✅ Living docs sync works best with one central location
 
-**Plugin Detection**:
-- ✅ Four-phase detection assumes one `.specweave/` folder
-- ✅ Auto-detection scans from root only
-- ✅ No ambiguity about where plugins are enabled
+**Plugin Installation**:
+- ✅ ALL plugins installed automatically during `specweave init`
+- ✅ No selective loading or detection needed
+- ✅ Full capabilities available immediately
 
 **Prevents Chaos**:
 - ❌ Nested folders cause: Which is the source of truth?
@@ -842,7 +842,7 @@ if (parentSpecweave) {
 - Domain expertise (ML, payments) = separate plugins
 - Core plugin = only increment lifecycle + living docs automation
 
-### Available Plugins (Opt-In)
+### Available Plugins (All Auto-Installed)
 
 **Implemented Plugins**:
 
@@ -891,20 +891,22 @@ if (parentSpecweave) {
 | **jira-sync** | 1 | 1 | 2 | JIRA project tracking |
 | **ado-sync** | 1 | 1 | 2 | Azure DevOps tracking |
 
-### Context Efficiency Examples
+### Context Efficiency
 
-**Before** - Monolithic approach:
-- Simple React app: Loads ALL 44 skills + 20 agents ≈ **50K tokens**
-- Backend API: Loads ALL 44 skills + 20 agents ≈ **50K tokens**
-- ML pipeline: Loads ALL 44 skills + 20 agents ≈ **50K tokens**
+**All plugins are installed, but only relevant skills activate based on context**. Claude Code's native skill system ensures:
+- Skills only activate when their description keywords match the conversation
+- Agents only load when explicitly invoked
+- Commands only appear when relevant
 
-**After** - Modular plugin architecture:
-- Simple React app: Core + frontend-stack + github ≈ **16K tokens** (68% reduction!)
-- Backend API: Core + nodejs-backend + github ≈ **15K tokens** (70% reduction!)
-- ML pipeline: Core + ml-ops + github ≈ **18K tokens** (64% reduction!)
-- SpecWeave itself: Core + github + diagrams ≈ **15K tokens** (70% reduction!)
+**Example**: Working on a React frontend:
+- ✅ `specweave-frontend` skills activate (React, Next.js, design systems)
+- ✅ `specweave-github` skills activate (if mentioning GitHub)
+- ❌ `specweave-ml` skills stay dormant (ML keywords not detected)
+- ❌ `specweave-payments` skills stay dormant (Stripe not mentioned)
 
-### How Plugins Are Loaded (Intelligent Auto-Loading)
+**Result**: Even with 19+ plugins installed, you only "pay" (in tokens) for what you're actively using in the conversation.
+
+### How Plugins Are Loaded (All Plugins Installed Upfront)
 
 **SpecWeave's plugin system is designed to be intelligent and non-intrusive:**
 
@@ -932,193 +934,62 @@ When you run `specweave init`:
    - Claude Code automatically discovers plugins from GitHub
    - No manual `/plugin marketplace add` needed!
 
-2. ✅ **Core Plugin Auto-Installation**
-   - Automatically runs: `claude plugin marketplace add` and `claude plugin install specweave`
+2. ✅ **ALL Plugins Auto-Installation** (Breaking Change: No Selective Loading!)
+   - Automatically installs ALL 19+ plugins from marketplace.json
    - Works via CLI during init (uses user's shell to access `claude` command)
-   - Slash commands available IMMEDIATELY - no manual install!
-   - Success message: "✔ SpecWeave core plugin installed automatically!"
+   - Installation process:
+     1. Removes existing marketplace (if present)
+     2. Re-adds marketplace from GitHub (always fresh)
+     3. Reads marketplace.json to get list of all plugins
+     4. Installs each plugin via `claude plugin install {name}`
+     5. Reports success/failure for each plugin
+   - All slash commands available IMMEDIATELY - no manual install needed!
+   - Success message: "✔ Installed: 19/19 plugins"
    - Graceful fallback: If CLI unavailable, shows manual install instructions
-
-3. ✅ **Issue Tracker Plugin Auto-Installation** (NEW! v0.8.18+)
-   - Detects GitHub/Jira/Azure DevOps from project structure
-   - Prompts for credentials (API tokens, PATs)
-   - **Automatically installs** corresponding plugin (specweave-github, specweave-jira, specweave-ado)
-   - Happens AFTER marketplace registration (ensures plugin installation succeeds)
-   - Shows detailed error messages if auto-install fails
-   - Example: Jira detected → credentials saved → `specweave-jira` plugin installed automatically
-
-4. ℹ️  **Optional Plugins Available**
-   - Suggested based on project type (frontend, backend, infrastructure)
-   - User can install later via `/plugin install specweave-{name}`
+   - **No selective loading**: Everything installed upfront for full capabilities
 
 **Key Architectural Change**:
 - ❌ Old: Copied `.claude-plugin/` + `plugins/` to every project (~2MB bloat)
 - ✅ New: Reference GitHub marketplace (~2KB settings.json, always up-to-date)
 
-#### Phase 2: Increment Planning (Intelligent Plugin Detection)
-
-When you create increments (e.g., `/specweave:increment "Add Stripe billing"`):
-
-1. **Spec Analysis** (v0.6.0+, Enhanced v0.8.18+)
-   - increment-planner skill scans spec.md content
-   - Detects keywords: "Stripe", "GitHub", "Kubernetes", "React", etc.
-   - Maps keywords → required plugins (see Step 6 in increment-planner/SKILL.md)
-
-2. **🚨 AUTOMATIC Plugin Recommendation** (Enhanced v0.8.18+)
-   ```
-   🔌 Detected plugin requirements from spec content:
-
-   REQUIRED (will significantly improve implementation):
-   • specweave-payments - Stripe integration
-     Detected: "billing", "Stripe", "subscriptions"
-     Provides: Stripe expert agent, payment flow validation, webhook handling
-     → Without this: Manual Stripe integration, no validation
-
-   📦 Install recommended plugins:
-     /plugin install specweave-payments
-
-   💡 Benefits:
-     • Plugins provide specialized AI agents (Stripe expert, etc.)
-     • Skills auto-activate based on context (zero manual invocation)
-     • 70%+ context reduction (only load what you need)
-     • Best practices built-in (from real-world experience)
-
-   Would you like me to wait while you install these plugins? (Recommended)
-   Or shall I continue without them? (Limited capabilities)
-   ```
-
-3. **User Decision**
-   - Install now → Plugin activates immediately (skills available during implementation)
-   - Install later → Skills won't be available until plugin installed (can add mid-work)
-   - Skip → Increment creation continues (not blocked, but capabilities limited)
-
-#### Phase 2.5: Just-in-Time Plugin Installation (NEW! v0.10.0+)
-
-**The Critical Gap**: Users request features that require plugins (e.g., "preview docs locally"), but those plugins aren't installed yet. Instead of failing silently or recommending manual installation, SpecWeave now **automatically installs plugins just-in-time**.
-
-**How it works** (via `plugin-installer` skill):
+#### Phase 2: Implementation (All Plugins Ready)
 
-1. **Automatic Detection**
-   - User requests a feature (e.g., "Show me the internal docs in a browser")
-   - `plugin-installer` skill detects keywords: "docs", "browser" → needs `specweave-docs-preview`
-   - Checks if plugin is installed: `/plugin list --installed`
-
-2. **Auto-Installation**
-   ```
-   🔌 Detected need for specweave-docs-preview plugin
-
-   📦 Installing specweave-docs-preview...
-      This plugin provides: Beautiful Docusaurus UI for browsing .specweave/docs/
-
-   ✅ Plugin installed successfully!
-      You can now:
-      • Browse documentation in beautiful UI
-      • Hot reload when editing markdown files
-      • Render Mermaid diagrams automatically
-
-   Proceeding to launch docs preview server...
-   ```
-
-3. **Seamless Execution**
-   - Plugin installed automatically (no manual intervention)
-   - Feature executes immediately
-   - User sees clear notification of what was installed and why
-
-**Supported Just-in-Time Plugins**:
-
-| User Keywords | Auto-Installed Plugin | Capabilities |
-|--------------|----------------------|--------------|
-| "preview docs", "documentation UI", "Docusaurus" | `specweave-docs-preview` | Beautiful docs UI, hot reload |
-| "React", "Next.js", "frontend", "UI component" | `specweave-frontend` | Frontend expert, design systems |
-| "K8s", "Kubernetes", "Helm", "deploy" | `specweave-kubernetes` | K8s expert, manifest generation |
-| "TensorFlow", "PyTorch", "ML model" | `specweave-ml` | ML pipelines, training, deployment |
-| "Stripe", "billing", "payment" | `specweave-payments` | Payment expert, Stripe integration |
-| "Playwright", "E2E testing", "browser automation" | `specweave-testing` | E2E testing infrastructure |
-| "Figma", "design tokens", "prototype" | `specweave-figma` | Design system integration |
-| "Mermaid", "C4 model", "architecture diagram" | `specweave-diagrams` | Diagram generation |
-
-**Key Benefits**:
-- ✅ **Zero friction**: No manual plugin installation needed
-- ✅ **Proactive**: Detects requirements automatically based on user request
-- ✅ **Clear UX**: Users understand what's being installed and why
-- ✅ **Fail-safe**: Handles installation errors gracefully with troubleshooting steps
-
-**See**: `plugins/specweave/skills/plugin-installer/SKILL.md` for complete keyword map and workflow
-
-#### Phase 3: Implementation (Auto-Activation)
-
-When plugins are installed:
+After `specweave init`, ALL plugins are already installed. No additional steps needed!
 
 1. **Skills Auto-Activate**
    - Based on description keywords (Claude Code native behavior)
    - No manual invocation needed
    - Example: Mention "GitHub" → github-sync skill activates
 
-2. **Context Efficiency**
-   - Only loaded plugins consume tokens
-   - 70%+ reduction vs. monolithic approach
-   - Real-time: Simple React app = 16K tokens (was 50K in v0.3.7)
-
-#### Phase 4: First Increment Completion (Documentation Preview)
+2. **All Capabilities Available**
+   - GitHub integration: `/specweave-github:sync`
+   - JIRA integration: `/specweave-jira:sync`
+   - Frontend tools: React, Next.js, design systems
+   - Backend tools: Node.js, Python, .NET
+   - Infrastructure: Kubernetes, Helm, monitoring
+   - ...and 19+ more plugins ready to use!
 
-After completing your first increment:
+### Plugin Management
 
-1. **🎉 Post-First-Increment Hook** (NEW! v0.8.18+)
-   - Automatically triggers when first increment is marked complete
-   - Suggests docs-preview plugin for beautiful documentation UI
-   - Shows clear benefits and install command
-
-2. **Suggestion Format**:
-   ```
-   🎉 Congratulations! You completed your first increment!
-
-   📚 Preview your documentation in a beautiful UI?
-
-   The specweave-docs-preview plugin can generate a Docusaurus site from
-   your .specweave/docs/ folder with:
-
-      ✓ Auto-generated sidebar from folder structure
-      ✓ Hot reload (edit markdown, see changes instantly)
-      ✓ Mermaid diagram rendering
-      ✓ Priority sorting (Strategy → Specs → Architecture → ...)
-
-   📦 Install with:
-      /plugin install specweave-docs-preview
-
-   🚀 Then launch:
-      /specweave:docs preview
-   ```
-
-3. **Benefits**:
-   - Beautiful, searchable documentation site (Docusaurus 3.x)
-   - Live preview with hot reload (see changes in real-time)
-   - Auto-generated navigation from folder structure
-   - Mermaid diagrams rendered automatically
-   - Share docs with stakeholders (export static site)
-
-### Manual Plugin Management
-
-All plugin management happens through Claude Code's native commands:
+**All 19+ plugins are automatically installed during `specweave init`**. You rarely need to manage plugins manually, but Claude Code's native commands are available if needed:
 
 ```bash
-# List installed plugins
+# List installed plugins (should show all 19+ SpecWeave plugins)
 /plugin list --installed
 
-# Install a specific plugin
-/plugin install specweave-kubernetes
-
-# Uninstall a plugin
+# Uninstall a plugin (not recommended - breaks functionality)
 /plugin uninstall specweave-kubernetes
 
-# List all available plugins from marketplace
-/plugin list specweave
+# Reinstall all plugins (if you uninstalled something by mistake)
+specweave init .  # Re-runs full installation
 ```
 
 **Key Insight**: SpecWeave uses **ONLY** Claude Code's native plugin system:
+- ALL plugins installed automatically during init (no manual selection)
 - Plugins install globally via `/plugin install specweave-{name}`
 - Work across ALL projects (like VS Code extensions)
 - Auto-activate based on skills' description keywords
-- Managed by Claude Code (updates, uninstall, etc.)
+- Managed by Claude Code (updates handled via `specweave init` re-run)
 
 ### Development vs Production Setup
 
@@ -2117,6 +1988,137 @@ ls -1 .specweave/increments/ | grep -E '^[0-9]{4}' | wc -l
 - ✅ **Compliance & auditing**: Complete audit trail of all product decisions
 - ✅ **Living documentation**: Specs stay up-to-date without manual intervention
 
+**Post-Increment-Planning Hook** (AUTOMATIC after `/specweave:increment`):
+
+**GitHub Issue Auto-Creation** (NEW in v0.8.20+):
+
+**The Critical Problem**: Without automatic GitHub issue creation, increments don't sync to GitHub automatically. This requires manual `/specweave-github:create-issue` calls, which are often forgotten.
+
+**The Solution**: The `post-increment-planning.sh` hook now auto-creates GitHub issues immediately after increment planning completes.
+
+**How It Works** (Automatic):
+1. **Hook Triggers**: After `/specweave:increment` completes planning (spec.md, plan.md, tasks.md created)
+2. **Auto-Create Check**: Checks if `config.sync.settings.autoCreateIssue` is enabled
+3. **GitHub CLI Available**: Verifies `gh` CLI is installed and authenticated
+4. **Issue Creation**:
+   - Extracts title from spec.md frontmatter (`title: "..."`)
+   - Extracts summary from "Quick Overview" section
+   - Generates task checklist from tasks.md (all tasks as GitHub checkboxes)
+   - Calls `gh issue create` with proper labels (`specweave`, `increment`)
+   - Parses output to get issue number
+5. **Metadata Update**: Creates/updates `.metadata.json` with GitHub issue number and URL
+6. **Result**: Increment is now linked to GitHub issue for bidirectional sync!
+
+**Configuration** (`.specweave/config.json`):
+```json
+{
+  "sync": {
+    "settings": {
+      "autoCreateIssue": true,  // ✅ Enable auto-creation!
+      "syncDirection": "bidirectional"
+    },
+    "activeProfile": "specweave-dev",
+    "profiles": {
+      "specweave-dev": {
+        "provider": "github",
+        "config": {
+          "owner": "anton-abyzov",
+          "repo": "specweave"
+        }
+      }
+    }
+  }
+}
+```
+
+**What Gets Created**:
+```markdown
+# [INC-0016] AI Self-Reflection System
+
+**Status**: Planning → Implementation
+**Priority**: P1
+**Increment**: 0016-self-reflection-system
+
+## Summary
+
+Add AI self-reflection capabilities inspired by Kimi model...
+
+## Tasks
+
+Progress: 0/30 tasks (0%)
+
+- [ ] T-001: Create Reflection Configuration Schema
+- [ ] T-002: Create Configuration Loader
+- [ ] T-003: Create Git Diff Analyzer
+... (all 30 tasks)
+
+## Links
+
+- **Spec**: `spec.md`
+- **Plan**: `plan.md`
+- **Tasks**: `tasks.md`
+
+---
+
+🤖 Auto-created by SpecWeave | Updates automatically on task completion
+```
+
+**Error Handling** (Robust):
+- ✅ **Missing files**: Graceful fallback if spec.md or tasks.md missing
+- ✅ **Title extraction**: Multiple fallbacks (frontmatter → heading → increment ID)
+- ✅ **Overview extraction**: Tries "Quick Overview", "Summary", or first paragraph
+- ✅ **Task count**: Extracts from frontmatter or counts tasks
+- ✅ **GitHub CLI failures**: Non-blocking (logs error, continues)
+- ✅ **Duplicate prevention**: Checks metadata.json for existing issue number
+- ✅ **Repository detection**: Auto-detects from git remote or config
+
+**Manual Override** (When Needed):
+```bash
+# Disable auto-create for one increment
+# Just don't set autoCreateIssue in config
+
+# Or create manually if auto-create failed
+/specweave-github:create-issue 0016
+
+# Check if issue was created
+cat .specweave/increments/0016-self-reflection-system/metadata.json
+# Should show: "github": {"issue": 30, "url": "..."}
+```
+
+**Why This Matters**:
+- ✅ **Zero manual work**: Issues auto-create on every increment
+- ✅ **Immediate tracking**: Increment linked to GitHub from start
+- ✅ **Bidirectional sync**: Task completion updates GitHub automatically
+- ✅ **Team visibility**: Stakeholders see progress in GitHub without asking
+- ✅ **Audit trail**: All increments tracked in one place
+- ✅ **DORA metrics**: Automatic deployment frequency tracking
+
+**Workflow Example**:
+```bash
+# 1. Create increment
+/specweave:increment "AI self-reflection system"
+
+# 2. Hook auto-fires:
+# 🔗 Checking GitHub issue auto-creation...
+#   📦 Auto-create enabled, checking for GitHub CLI...
+#   ✓ GitHub CLI found
+#   🚀 Creating GitHub issue for 0016-self-reflection-system...
+#   📝 Issue #30 created
+#   🔗 https://github.com/anton-abyzov/specweave/issues/30
+#   ✅ metadata.json updated
+
+# 3. Start work
+/specweave:do
+
+# 4. Complete tasks → GitHub updates automatically via post-task-completion hook!
+```
+
+**Requirements**:
+- GitHub CLI (`gh`) installed and authenticated (`gh auth login`)
+- Repository with GitHub remote configured
+- `autoCreateIssue: true` in config.json
+- Write permissions to repository
+
 ---
 
 ## Plugins
@@ -2129,10 +2131,10 @@ ls -1 .specweave/increments/ | grep -E '^[0-9]{4}' | wc -l
 
 ```
 SpecWeave = Collection of Claude Code Plugins
-├── specweave (auto-loaded) ← The "framework" IS a plugin
-├── specweave-github (opt-in)
-├── specweave-figma (opt-in)
-└── ...all other plugins (opt-in)
+├── specweave (auto-installed) ← The "framework" IS a plugin
+├── specweave-github (auto-installed)
+├── specweave-figma (auto-installed)
+└── ...all 19+ plugins (auto-installed)
 ```
 
 **What this means**:
@@ -2159,7 +2161,7 @@ SpecWeave = Collection of Claude Code Plugins
 **Discovery**:
 - Browse all plugins: `ls plugins/` or check [.claude-plugin/marketplace.json](/.claude-plugin/marketplace.json)
 - Live catalog: See `.claude-plugin/README.md` for current marketplace contents
-- Auto-detection during `specweave init` suggests relevant plugins
+- **All plugins automatically installed** during `specweave init` (no manual selection needed)
 
 **Plugin Structure** (all follow same pattern):
 ```
@@ -2171,8 +2173,8 @@ plugins/specweave-{name}/
 └── lib/                        # TypeScript utilities (optional)
 ```
 
-**Key Plugins** (for reference):
-- `specweave` - Framework essentials (always loaded)
+**Key Plugins** (for reference - all auto-installed):
+- `specweave` - Framework essentials
 - `specweave-github` - GitHub Issues integration
 - `specweave-{frontend|backend|infrastructure}` - Tech stack plugins
 
@@ -2687,112 +2689,6 @@ vim docs-site/docs/guides/getting-started.md
 cd docs-site && npm run build
 ```
 
-### Documentation Preview (specweave-docs-preview plugin)
-
-**Live preview of `.specweave/docs/` with Docusaurus** - Beautiful UI with hot reload, auto-generated sidebar, and Mermaid diagram support.
-
-**When to Use**:
-- ✅ After completing your first increment (auto-suggested)
-- ✅ Reviewing documentation in a beautiful UI instead of raw markdown
-- ✅ Sharing documentation with non-technical stakeholders
-- ✅ Preparing documentation for external publication
-
-**Installation** (auto-prompted after first increment):
-
-The `post-first-increment.sh` hook automatically prompts you after completing your first increment:
-
-```
-🎉 Congratulations! You completed your first increment!
-
-📚 Would you like to preview your documentation in a beautiful UI?
-
-Options:
-  1) Yes, install and launch now (recommended)
-  2) No thanks, I'll browse markdown files manually
-  3) Remind me later
-
-Your choice [1]:
-```
-
-**Manual Commands**:
-
-```bash
-# Launch preview (installs Docusaurus if needed)
-/specweave:docs preview
-
-# Specify port
-/specweave:docs preview --port 3001
-
-# Build static site for deployment
-/specweave:docs build
-
-# Output: .specweave/docs-site-internal/build/
-```
-
-**Features**:
-- ✅ **Auto-generated sidebar** from `.specweave/docs/internal/` folder structure
-- ✅ **Hot reload** - Edit markdown files and see changes instantly
-- ✅ **Mermaid diagrams** - Automatic rendering of diagrams
-- ✅ **Priority sorting** - Strategy → Specs → Architecture → Delivery → Operations → Governance
-- ✅ **Port auto-discovery** - Finds available port (3000-3010)
-- ✅ **Cross-platform** - Windows/macOS/Linux compatible
-
-**What Gets Indexed**:
-- `.specweave/docs/internal/strategy/` - Business rationale, PRDs
-- `.specweave/docs/internal/specs/` - Feature specifications
-- `.specweave/docs/internal/architecture/` - Technical design, ADRs
-- `.specweave/docs/internal/delivery/` - Build & release processes
-- `.specweave/docs/internal/operations/` - Runbooks, SLOs
-- `.specweave/docs/internal/governance/` - Policies, security
-
-**What Gets Excluded**:
-- ❌ `legacy/` folder (brownfield imports, temporary)
-- ❌ `node_modules/`, `.git/`
-- ❌ `.specweave/increments/` (implementation details, not strategic docs)
-
-**Configuration** (`.specweave/config.json`):
-
-```json
-{
-  "documentation": {
-    "preview": {
-      "enabled": true,
-      "autoInstall": true,
-      "port": 3000,
-      "openBrowser": true,
-      "theme": "default",
-      "excludeFolders": ["legacy", "node_modules"]
-    }
-  }
-}
-```
-
-**Requirements**:
-- Node.js 18+ (Docusaurus 3.0 requirement)
-- ~150 MB disk space for npm packages
-- ~30 seconds first-time install
-
-**Files Created** (gitignored):
-- `.specweave/docs-site-internal/` - Complete Docusaurus installation for internal docs
-  - `package.json` - Dependencies
-  - `docusaurus.config.js` - Configuration
-  - `sidebars.js` - Auto-generated sidebar
-  - `src/` - Landing page and custom CSS
-  - `node_modules/` - npm packages
-  - `build/` - Static site output (after build)
-
-**Note**: This is separate from `docs-site/` (public-facing docs at project root)
-
-**Implementation**:
-- Plugin: `plugins/specweave-docs-preview/`
-- TypeScript utilities: `src/utils/docs-preview/`
-- CLI commands: `src/cli/commands/docs-{preview,build,setup}.ts`
-- Hook: `plugins/specweave/hooks/post-first-increment.sh`
-
-**See Also**:
-- Plugin docs: `plugins/specweave-docs-preview/skills/docs-preview/SKILL.md`
-- Command docs: `plugins/specweave-docs-preview/commands/docs-preview.md`
-
 ### Translation Workflow (Multilingual Support)
 
 **SpecWeave supports multilingual development** via two-phase post-generation translation (Increment 0006).