specweave 0.10.1 → 0.12.0

package/plugins/specweave/skills/plugin-installer/SKILL.md

@@ -1,21 +1,36 @@
 ---
 name: plugin-installer
-description: Proactive just-in-time plugin installation. Auto-detects when specialized plugins are needed (docs-preview, frontend, kubernetes, ML, payments, testing, etc.) and installs them automatically before use. Activates for preview docs, Docusaurus, React, Next.js, K8s, Kubernetes, Helm, TensorFlow, PyTorch, ML model, Stripe, billing, payment, Playwright, E2E testing, Figma, design system, ADO, Azure DevOps, infrastructure, Prometheus, Grafana, monitoring, Node.js, Python backend, REST API, cloud deployment, diagram, Mermaid, C4, architecture diagram.
+description: DEPRECATED - This skill is no longer needed. All plugins are now installed automatically during specweave init. This skill remains for backward compatibility but should NOT activate.
 ---
 
-# Plugin Installer - Proactive Just-in-Time Plugin Installation
+# Plugin Installer - DEPRECATED
 
-**Purpose**: Automatically detect when specialized SpecWeave plugins are needed and install them just-in-time, BEFORE attempting to use their features.
+**Status**: ⚠️ **DEPRECATED** - Do not use this skill
 
-**When to Activate**: Whenever user requests functionality that requires a specific plugin (e.g., "preview docs", "deploy to K8s", "add React component", "train ML model", etc.)
+**Reason**: As of v0.11.0+, ALL SpecWeave plugins (19+) are automatically installed during `specweave init`. There is no need for just-in-time plugin installation anymore.
+
+**What Changed**:
+- ❌ Old: Selective plugin loading with just-in-time installation
+- ✅ New: All plugins installed upfront during init
+
+**If you see this skill activating**, it means you're using an old SpecWeave installation. Run `specweave init` again to get all plugins installed automatically.
 
 ---
 
-## 🚨 CRITICAL: The Plugin Installation Gap
+## For Contributors: Why This Was Deprecated
 
-**The Problem**: Users request features that require plugins (e.g., "preview docs locally"), but those plugins are NOT installed. Claude tries to use plugin features anyway, which fails silently or produces incomplete results.
+**The Problem with Just-in-Time Installation**:
+- Added complexity to the workflow
+- Users had to wait for installations mid-work
+- Network issues could block work unexpectedly
+- Detection logic was fragile (keyword matching)
 
-**The Solution**: This skill proactively detects plugin requirements, checks if plugins are installed, and auto-installs them BEFORE attempting to use their features.
+**The Solution - Install Everything Upfront**:
+- All 19+ plugins installed during `specweave init`
+- Takes ~30 seconds upfront but saves time later
+- All capabilities available immediately
+- No network dependencies during work
+- Simpler, more predictable user experience
 
 ---
 
@@ -25,8 +40,6 @@ description: Proactive just-in-time plugin installation. Auto-detects when speci
 
 | User Keywords | Required Plugin | Installation Command |
 |--------------|----------------|---------------------|
-| **Documentation Preview** |
-| "preview docs", "browse docs locally", "documentation UI", "Docusaurus server", "local docs preview" | `specweave-docs-preview` | `/plugin install specweave-docs-preview` |
 | **Frontend Development** |
 | "React", "Next.js", "Vue", "Angular", "frontend", "UI component", "design system", "Tailwind" | `specweave-frontend` | `/plugin install specweave-frontend` |
 | **Kubernetes/DevOps** |
@@ -62,10 +75,10 @@ When user mentions keywords from the map above, **IMMEDIATELY** check if the req
 
 **Example**:
 ```
-User: "Can you preview the internal docs locally?"
+User: "Can you help me build a React component?"
 
-Keywords detected: "preview", "docs", "locally"
-→ Required plugin: specweave-docs-preview
+Keywords detected: "React", "component"
+→ Required plugin: specweave-frontend
 ```
 
 ### Step 2: Check if Plugin is Installed
@@ -86,7 +99,7 @@ If the plugin is NOT installed:
 /plugin install <plugin-name>
 
 # Example:
-/plugin install specweave-docs-preview
+/plugin install specweave-frontend
 ```
 
 ### Step 4: Notify User (Clear and Friendly)
@@ -108,9 +121,9 @@ Proceeding with your request...
 **Example**:
 
 ```
-🔌 Detected need for specweave-docs-preview plugin
+🔌 Detected need for specweave-frontend plugin
 
-📦 Installing specweave-docs-preview...
+📦 Installing specweave-frontend...
    This plugin provides: Beautiful Docusaurus UI for browsing .specweave/docs/
 
 ✅ Plugin installed successfully!
@@ -130,25 +143,25 @@ Proceeding to launch docs preview server...
 
 ## Common Scenarios
 
-### Scenario 1: Documentation Preview
+### Scenario 1: React Component Development
 
-**User Request**: "Show me the internal docs in a nice UI"
+**User Request**: "Build a React component with TypeScript"
 
 **Workflow**:
 ```
-1. Detect keywords: "docs", "UI"
-   → Required: specweave-docs-preview
+1. Detect keywords: "React", "component", "TypeScript"
+   → Required: specweave-frontend
 
 2. Check installed: /plugin list --installed
    → Not found
 
-3. Install: /plugin install specweave-docs-preview
+3. Install: /plugin install specweave-frontend
 
 4. Notify user:
-   🔌 Installing specweave-docs-preview for beautiful docs UI...
+   🔌 Installing specweave-frontend for React development...
    ✅ Installed!
 
-5. Launch: /specweave:docs preview
+5. Create component using frontend skills
 ```
 
 ### Scenario 2: Kubernetes Deployment
@@ -265,16 +278,16 @@ When increment-planner detects plugin requirements (Step 6), it should:
 3. **Auto-install missing plugins** (via this skill)
 4. **Then proceed** with increment planning
 
-### Example: docs-preview skill (hypothetical)
+### Example: frontend skill (hypothetical)
 
 ```markdown
-# BEFORE using Docusaurus features:
+# BEFORE using React features:
 
-1. Check if specweave-docs-preview is installed
+1. Check if specweave-frontend is installed
    → If not: Invoke plugin-installer skill
-   → Auto-install specweave-docs-preview
+   → Auto-install specweave-frontend
 
-2. Then launch Docusaurus server
+2. Then proceed with component creation
 ```
 
 ---
@@ -296,7 +309,7 @@ When increment-planner detects plugin requirements (Step 6), it should:
 User: "Show me the internal documentation in a browser"
 
 Expected:
-1. Detects "documentation", "browser" → specweave-docs-preview
+1. Detects "React", "component" → specweave-frontend
 2. Checks installed
 3. Auto-installs if missing
 4. Launches preview

package/plugins/specweave/skills/plugin-validator/SKILL.md

@@ -92,7 +92,6 @@ This skill ensures that your SpecWeave environment is properly configured with a
 - **specweave-backend-nodejs**: nodejs, express, fastify, nestjs, backend
 - **specweave-backend-python**: python, fastapi, django, flask
 - **specweave-backend-dotnet**: dotnet, .net, aspnet, c#
-- **specweave-docs-preview**: documentation, docs, preview, docusaurus
 - **specweave-e2e-testing**: playwright, e2e, end-to-end, browser
 
 ## Usage Examples

package/plugins/specweave/skills/project-kickstarter/SKILL.md

@@ -115,7 +115,7 @@ Let's start: [Ask 1 clarifying question if needed, otherwise proceed]"
 
 Once I have these details, I'll guide you through SpecWeave's increment planning process."
 
-[Wait for response, then route to increment-planner or spec-driven-brainstorming]
+[Wait for response, then route to the planning workflow]
 ```
 
 **Low Confidence:**
@@ -331,8 +331,8 @@ User message → specweave-detector (checks .specweave/ exists)
 **Calls:**
 - `specweave-detector` - Checks if .specweave/ directory exists (SpecWeave context)
 - `/specweave:inc` - For clear requirements (high confidence)
-- `spec-driven-brainstorming` - For unclear requirements (medium confidence)
-- `increment-planner` - Directly if enough detail provided
+- Spec-driven brainstorming - For unclear requirements (medium confidence)
+- Planning workflow - Directly if enough detail provided
 
 **Called By:**
 - Automatically when pattern detected in SpecWeave folder

package/plugins/specweave/skills/spec-generator/SKILL.md

@@ -350,9 +350,9 @@ spec_generator:
 
 ## Related Skills
 
-- **increment-planner**: Guides increment planning (uses Spec Generator internally)
-- **context-loader**: Loads relevant context for specification generation
-- **increment-quality-judge**: Validates generated specifications for completeness
+- **Planning workflow**: Guides increment planning (uses Spec Generator internally)
+- **Context loading**: Loads relevant context for specification generation
+- **Quality validation**: Validates generated specifications for completeness
 
 ---
 

package/plugins/specweave-ado/agents/ado-manager/AGENT.md

@@ -23,6 +23,8 @@ context: |
 - API authentication and rate limiting
 - Error handling and retry strategies
 
+**Default Behavior**: **Bidirectional sync** (two-way) - Synchronizes changes in both directions automatically
+
 ---
 
 ## 🚨 CRITICAL: Concept Mapping (MANDATORY)

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

@@ -1,49 +1,142 @@
 ---
 name: specweave-ado:sync
-description: Sync SpecWeave increment progress with Azure DevOps work item
+description: Bidirectional sync between SpecWeave increment and Azure DevOps work item (two-way sync by default)
 ---
 
 # Sync ADO Work Item Command
 
-**Usage**: `/specweave-ado:sync <increment-id>`
+**Usage**: `/specweave-ado:sync <increment-id> [options]`
 
-**Purpose**: Update ADO work item with current increment progress
+**Purpose**: Bidirectional synchronization between SpecWeave increment and Azure DevOps work item
+
+**Default**: Two-way sync (bidirectional)
 
 ---
 
-## Command Behavior
+## Options
+
+- `--direction <mode>`: Sync direction (default: `bidirectional`)
+  - `bidirectional`: SpecWeave ↔ ADO (default - recommended)
+  - `to-ado`: SpecWeave → ADO only (push progress)
+  - `from-ado`: ADO → SpecWeave only (pull updates)
+
+## Examples
+
+```bash
+# Bidirectional sync (default - two-way)
+/specweave-ado:sync 0005
+
+# Push only (one-way to ADO)
+/specweave-ado:sync 0005 --direction to-ado
+
+# Pull only (one-way from ADO)
+/specweave-ado:sync 0005 --direction from-ado
+```
+
+---
 
-When user runs this command, invoke `ado-manager` agent to:
+## Command Behavior
 
+When user runs this command, invoke `ado-manager` agent to perform bidirectional sync:
+
+### Phase 1: Pull FROM ADO (default behavior)
+1. Fetch work item state from ADO API
+2. Detect changes in ADO:
+   - State changes (New → Active → Resolved → Closed)
+   - Priority changes
+   - Iteration/sprint changes
+   - Comments from team members
+   - Field updates
+3. Apply ADO changes to SpecWeave increment:
+   - Update increment status to match ADO state
+   - Update priority in metadata
+   - Import team comments to increment notes
+   - Update iteration tracking
+
+### Phase 2: Push TO ADO (default behavior)
 1. Read tasks.md from increment
 2. Calculate completion percentage
 3. Identify recently completed tasks
 4. Format progress update comment
 5. POST comment to ADO work item
 6. Update work item state if needed (New → Active → Resolved)
+7. Update custom fields (completion %, current task, etc.)
 
 **Agent Invocation**:
 ```
 Use Task tool with subagent_type: "ado-manager"
 
-Prompt: "Sync progress for increment 0005-payment-integration to ADO.
+Prompt: "Bidirectional sync for increment 0005-payment-integration with ADO.
 
-Steps:
+Phase 1 - Pull FROM ADO:
+1. Fetch work item #12345 from ADO API
+2. Detect changes: state, priority, iteration, comments
+3. Apply ADO changes to increment metadata
+4. Import team comments to increment notes
+
+Phase 2 - Push TO ADO:
 1. Read .specweave/increments/0005/tasks.md
 2. Calculate: X/Y tasks complete (Z%)
 3. Identify: Recently completed tasks
 4. Format comment with progress update
 5. Load work item ID from increment-metadata.json
 6. POST comment to ADO API
-7. Display: Sync confirmation"
+7. Update work item state/fields
+
+Display: Bidirectional sync summary"
 ```
 
 ---
 
 ## Example Output
 
+### Bidirectional Sync (Default)
+
+```
+🔄 Bidirectional sync for increment 0005...
+
+✓ Azure DevOps work item: #12345
+✓ Sync direction: bidirectional (two-way)
+
+Detecting changes (both directions)...
+
+FROM ADO:
+✓ Work item state changed: Active → Resolved
+✓ Iteration updated: Sprint 23 → Sprint 24
+✓ Priority changed: 2 → 1
+✓ 3 new comments from team
+
+FROM SpecWeave:
+✓ 2 new tasks completed (T-005, T-006)
+✓ Progress: 40% → 60% (6/10 tasks)
+✓ Current task: T-007
+
+Syncing TO ADO...
+✓ Posted progress comment (ID: 98765)
+✓ Updated completion: 60%
+✓ Updated current task field: T-007
+
+Syncing FROM ADO...
+✓ Updated increment status: active → completed
+✓ Updated priority: P2 → P1
+✓ Updated iteration tracking: Sprint 24
+✓ Imported 3 team comments to increment notes
+
+✅ Bidirectional Sync Complete!
+
+   SpecWeave ↔ ADO synchronized
+   • Pushed: Progress (60%), 2 task updates
+   • Pulled: State (Resolved), priority (P1), iteration, 3 comments
+
+ADO Work Item: https://dev.azure.com/myorg/MyProject/_workitems/edit/12345
+Last synced: just now
+Next sync: Automatic (hook-based) or manual when ready
+```
+
+### One-Way Sync (to-ado)
+
 ```
-✅ Synced to ADO Epic #12345
+✅ Pushed to ADO Work Item #12345
 
 Progress: 60% complete (6/10 tasks)
 

package/plugins/specweave-ado/skills/ado-sync/SKILL.md

@@ -1,16 +1,20 @@
 ---
 name: ado-sync
-description: Bidirectional synchronization between SpecWeave increments and Azure DevOps work items. Creates work items from increments, tracks progress via comments, updates increment status from work item state, and closes work items when increments complete. Activates for: Azure DevOps, ADO, work items, project management, sync to ADO, ADO integration, TFS integration.
+description: Bidirectional synchronization between SpecWeave increments and Azure DevOps work items (two-way sync by default). Creates work items from increments, tracks progress via comments, updates increment status from work item state, syncs changes in both directions automatically. Activates for: Azure DevOps, ADO, work items, project management, sync to ADO, ADO integration, TFS integration, bidirectional ADO sync.
 ---
 
 # Azure DevOps Sync Skill
 
 **Purpose**: Seamlessly sync SpecWeave increments with Azure DevOps work items for unified project tracking.
 
+**Default Behavior**: **Bidirectional (two-way) sync** - Changes in either system are automatically synchronized
+
 **Capabilities**:
+- Bidirectional sync: SpecWeave ↔ ADO (default)
 - Create ADO work items from increments
-- Sync task progress → ADO comments  
-- Update increment status from ADO state
+- Sync task progress → ADO comments
+- Update increment status ← ADO state changes
+- Pull ADO comments and field updates → SpecWeave
 - Close work items when increments complete
 - Support for Epics, Features, User Stories
 

package/plugins/specweave-docs-preview/.claude-plugin/plugin.json

@@ -0,0 +1,21 @@
+{
+  "name": "specweave-docs-preview",
+  "description": "Interactive documentation preview with Docusaurus. Launch local dev server to view living documentation in beautiful UI with hot reload, auto-generated sidebar, and Mermaid diagrams. Build static sites for deployment.",
+  "version": "1.0.0",
+  "author": {
+    "name": "SpecWeave Team",
+    "url": "https://spec-weave.com"
+  },
+  "homepage": "https://spec-weave.com",
+  "repository": "https://github.com/anton-abyzov/specweave",
+  "license": "MIT",
+  "keywords": [
+    "docusaurus",
+    "documentation",
+    "preview",
+    "docs-server",
+    "hot-reload",
+    "static-site",
+    "specweave"
+  ]
+}