specweave 0.10.0 → 0.11.0

package/plugins/specweave/skills/SKILLS-INDEX.md

@@ -2,9 +2,9 @@
 
 **Purpose**: Quick reference for all available skills. Read this file BEFORE starting any task.
 
-**Last Updated**: 2025-11-03T04:18:05.042Z (auto-generated, do not edit manually)
+**Last Updated**: 2025-11-10 (manually updated to include plugin-installer and plugin-expert)
 
-**Total Skills**: 12
+**Total Skills**: 14
 
 ---
 
@@ -37,6 +37,26 @@ Step 4: Execute → Follow the increment planning workflow
 
 ### Framework Core
 
+#### 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.
+
+**Activates for**: preview docs, documentation UI, Docusaurus, React, Next.js, frontend, UI component, K8s, Kubernetes, deploy, TensorFlow, ML model, Stripe, billing, E2E testing, Figma, diagram, architecture diagram
+
+**Location**: `.claude/skills/plugin-installer/SKILL.md`
+
+---
+
+#### plugin-expert
+
+**Description**: Expert knowledge of Claude Code's plugin system, marketplace management, and installation commands. Activates for plugin installation, marketplace setup, plugin troubleshooting, plugin commands. Keywords plugin install, plugin marketplace, claude code plugins, plugin management, plugin errors, marketplace add, plugin list.
+
+**Activates for**: plugin installation, marketplace setup, plugin troubleshooting, plugin commands, plugin install, plugin marketplace
+
+**Location**: `.claude/skills/plugin-expert/SKILL.md`
+
+---
+
 #### context-loader
 
 **Description**: Explains how SpecWeave achieves context efficiency through Claude's native progressive disclosure mechanism and sub-agent parallelization. Skills load only when relevant, sub-agents isolate context. Activates when users ask about context loading, token usage, or how SpecWeave scales. Keywords: context loading, progressive disclosure, token efficiency, sub-agents, context management.
@@ -182,6 +202,7 @@ Step 4: Execute → Follow the increment planning workflow
 
 | Your Task | Relevant Skill | Keywords |
 |-----------|---------------|----------|
+| "Preview internal docs" | `plugin-installer` | "preview docs", "Docusaurus", "documentation UI" |
 | "Plan a new feature" | `increment-planner` | "feature planning", "create increment" |
 | "Sync to JIRA" | `jira-sync` | "JIRA sync", "create JIRA issue" |
 | "Create diagram" | `diagrams-architect` | "architecture diagram", "C4 diagram" |

package/plugins/specweave/skills/increment-planner/SKILL.md

@@ -522,99 +522,24 @@ created: YYYY-MM-DD
 - Measurable acceptance criteria
 - Prioritized user stories (P1/P2/P3)
 
-### Step 6: Detect Required Plugins & Check PM Tool (INTELLIGENT AUTO-LOADING + PM SYNC)
-
-**Purpose**: Analyze spec content to identify required SpecWeave plugins AND check if external PM tool sync is configured.
-
-**⚠️ CRITICAL**: For ALL plugin installations, consult the `plugin-expert` skill for correct syntax. NEVER use `@marketplace` suffix!
-
-**Why This Matters**:
-1. SpecWeave's plugin system enables context efficiency (70%+ reduction) by loading only relevant capabilities
-2. PM tool integration enables automatic sync of increment progress to external systems (GitHub Issues, Jira, Azure DevOps)
-
-**Detection Algorithm**:
-
-1. **Scan spec.md for keywords**:
-   ```
-   Keywords → Plugin Mapping:
-   - "GitHub", "issue", "pull request", "PR" → specweave-github
-   - "Jira", "ticket", "epic" → specweave-jira
-   - "Azure DevOps", "ADO", "work item" → specweave-ado
-   - "Kubernetes", "K8s", "Helm", "kubectl" → specweave-kubernetes
-   - "Figma", "design system", "design tokens" → specweave-figma
-   - "Stripe", "PayPal", "billing", "subscriptions" → specweave-payments
-   - "React", "Next.js", "Vue", "Angular" → specweave-frontend
-   - "Express", "Fastify", "NestJS", "FastAPI" → specweave-backend
-   - "TensorFlow", "PyTorch", "ML", "training" → specweave-ml
-   - "Prometheus", "Grafana", "monitoring" → specweave-infrastructure
-   - "Playwright", "E2E", "browser tests" → specweave-testing
-   - "Mermaid", "C4", "diagrams", "architecture diagrams" → specweave-diagrams
-   ```
-
-2. **Check External PM Tool Configuration** (NEW v0.8.0):
-   - Read `.specweave/config.json`
-   - If `externalPM.enabled = true` and `externalPM.tool` is set:
-     - Check if corresponding plugin installed (specweave-github, specweave-jira, or specweave-ado)
-     - Prepare to auto-create external issue/work item after increment creation
-   - If `externalPM.enabled = false` or not configured:
-     - Skip PM tool sync (local-only mode)
-
-3. **Check if plugins are already installed**:
-   - For Claude Code: Check if plugin available via `/plugin list --installed`
-   - Skip already-installed plugins
-
-4. **🚨 AUTOMATIC PLUGIN INSTALLATION** (if plugins detected):
-
-   **IMPORTANT**: When you detect required plugins, you MUST:
-   - ✅ Proactively offer to install them (not just suggest)
-   - ✅ Explain WHY each plugin is needed (based on detected keywords)
-   - ✅ Show clear install commands
-   - ✅ Remind user that plugins provide expert AI agents and capabilities
-
-   **Output Format**:
-   ```
-   🔌 Detected plugin requirements from spec content:
+### Step 6: Check PM Tool Configuration (PM SYNC)
 
-   REQUIRED (will significantly improve implementation):
-   • specweave-github - GitHub Issues integration
-     Detected: "sync tasks to GitHub issues", "create pull requests"
-     Provides: GitHub sync, PR automation, issue tracking
-     → Without this: Manual GitHub sync required
+**Purpose**: Check if external PM tool sync is configured for automatic increment tracking.
 
-   • specweave-kubernetes - Kubernetes deployment
-     Detected: "deploy to production cluster", "kubectl apply"
-     Provides: K8s expert agent, Helm chart generation, deployment validation
-     → Without this: Manual K8s configuration, no validation
+**Why This Matters**: PM tool integration enables automatic sync of increment progress to external systems (GitHub Issues, Jira, Azure DevOps).
 
-   OPTIONAL (helpful but not critical):
-   • specweave-diagrams - Architecture diagrams
-     Detected: "system architecture", "component diagram"
-     Provides: Mermaid + C4 diagram generation
-     → Without this: Manual diagram creation
+**⚠️ NOTE**: All SpecWeave plugins (19+) are already installed during `specweave init`. No plugin detection or installation needed!
 
-   📦 Install recommended plugins:
-     /plugin install specweave-github
-     /plugin install specweave-kubernetes
+**Check External PM Tool Configuration**:
 
-   📦 Install optional plugins:
-     /plugin install specweave-diagrams
-
-   💡 Benefits:
-     • Plugins provide specialized AI agents (GitHub expert, K8s 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)
-   ```
-
-   **User Decision Points**:
-   - If user installs plugins → continue with full capabilities
-   - If user skips → continue but remind about limitations later
-   - NEVER block increment creation (plugins are enhancements, not requirements)
+1. **Read `.specweave/config.json`**:
+   - If `externalPM.enabled = true` and `externalPM.tool` is set:
+     - Corresponding plugin is already installed (specweave-github, specweave-jira, or specweave-ado)
+     - Prepare to auto-create external issue/work item after increment creation
+   - If `externalPM.enabled = false` or not configured:
+     - Skip PM tool sync (local-only mode)
 
-5. **Auto-Sync to PM Tool** (v0.8.0+):
+2. **Auto-Sync to PM Tool** (v0.8.0+):
 
    **🚨 CRITICAL: SpecWeave Repo Dog-Food Requirement**:
    - IF repo = "anton-abyzov/specweave"
@@ -683,10 +608,6 @@ Files:
 • plan.md (technical architecture)
 • tasks.md (implementation steps with embedded tests)
 
-🔌 Plugin Detection:
-   Detected: "user authentication", "JWT tokens", "session management"
-   → No additional plugins required
-
 🔗 External PM Tool Sync:
    Tool: GitHub Issues
    Plugin: specweave-github ✅ Installed
@@ -706,7 +627,7 @@ Next steps:
 ```
 
 **Integration with Existing Workflow**:
-- Plugin detection is a **suggestion step** (not blocking)
+- All plugins are already installed during `specweave init` (no detection needed)
 - PM tool sync is **automatic** if configured (zero manual intervention)
 - Increment creation continues regardless of PM tool status
 - This implements the "seamless integration" philosophy

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

@@ -0,0 +1,355 @@
+---
+name: plugin-installer
+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 - DEPRECATED
+
+**Status**: ⚠️ **DEPRECATED** - Do not use this skill
+
+**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.
+
+---
+
+## For Contributors: Why This Was Deprecated
+
+**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 - 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
+
+---
+
+## Plugin Detection Keywords Map
+
+**Use this map to detect which plugin is needed based on user's request keywords:**
+
+| 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** |
+| "K8s", "Kubernetes", "Helm", "kubectl", "deploy", "container", "pod", "service", "ingress" | `specweave-kubernetes` | `/plugin install specweave-kubernetes` |
+| **Machine Learning** |
+| "TensorFlow", "PyTorch", "ML model", "training", "machine learning", "neural network", "dataset" | `specweave-ml` | `/plugin install specweave-ml` |
+| **Payments** |
+| "Stripe", "PayPal", "billing", "subscription", "payment", "checkout", "PCI compliance" | `specweave-payments` | `/plugin install specweave-payments` |
+| **Testing** |
+| "Playwright", "E2E testing", "browser automation", "visual regression", "test automation" | `specweave-testing` | `/plugin install specweave-testing` |
+| **Figma/Design** |
+| "Figma", "design tokens", "design system", "prototype", "wireframe", "mockup" | `specweave-figma` | `/plugin install specweave-figma` |
+| **Backend Development** |
+| "Node.js backend", "Python backend", ".NET", "Express", "FastAPI", "Django", "REST API" | `specweave-backend` | `/plugin install specweave-backend` |
+| **Infrastructure** |
+| "Hetzner", "cloud infrastructure", "Prometheus", "Grafana", "monitoring", "alerting", "SLO" | `specweave-infrastructure` | `/plugin install specweave-infrastructure` |
+| **Architecture Diagrams** |
+| "Mermaid diagram", "C4 model", "architecture diagram", "sequence diagram", "ER diagram" | `specweave-diagrams` | `/plugin install specweave-diagrams` |
+| **Issue Trackers** (Usually auto-installed during init) |
+| "GitHub Issues", "sync GitHub", "create issue", "PR automation" | `specweave-github` | `/plugin install specweave-github` |
+| "Jira", "epic", "sprint", "story points", "Jira sync" | `specweave-jira` | `/plugin install specweave-jira` |
+| "ADO", "Azure DevOps", "work items", "boards", "ADO sync" | `specweave-ado` | `/plugin install specweave-ado` |
+
+---
+
+## Workflow: Just-in-Time Plugin Installation
+
+**CRITICAL**: Follow this workflow EVERY TIME you detect plugin keywords in user's request:
+
+### Step 1: Detect Plugin Requirement
+
+When user mentions keywords from the map above, **IMMEDIATELY** check if the required plugin is needed.
+
+**Example**:
+```
+User: "Can you preview the internal docs locally?"
+
+Keywords detected: "preview", "docs", "locally"
+→ Required plugin: specweave-docs-preview
+```
+
+### Step 2: Check if Plugin is Installed
+
+```bash
+# Check installed plugins
+/plugin list --installed
+```
+
+**Parse the output** to see if the required plugin is in the list.
+
+### Step 3: Auto-Install if Missing
+
+If the plugin is NOT installed:
+
+```bash
+# Install the plugin
+/plugin install <plugin-name>
+
+# Example:
+/plugin install specweave-docs-preview
+```
+
+### Step 4: Notify User (Clear and Friendly)
+
+**Good notification format**:
+
+```
+🔌 Detected need for <plugin-name> plugin
+
+📦 Installing <plugin-name>...
+   This plugin provides: <brief description>
+
+✅ Plugin installed successfully!
+   You can now: <list capabilities>
+
+Proceeding with your request...
+```
+
+**Example**:
+
+```
+🔌 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...
+```
+
+### Step 5: Proceed with User's Request
+
+**ONLY AFTER** the plugin is installed, proceed to use its features.
+
+---
+
+## Common Scenarios
+
+### Scenario 1: Documentation Preview
+
+**User Request**: "Show me the internal docs in a nice UI"
+
+**Workflow**:
+```
+1. Detect keywords: "docs", "UI"
+   → Required: specweave-docs-preview
+
+2. Check installed: /plugin list --installed
+   → Not found
+
+3. Install: /plugin install specweave-docs-preview
+
+4. Notify user:
+   🔌 Installing specweave-docs-preview for beautiful docs UI...
+   ✅ Installed!
+
+5. Launch: /specweave:docs preview
+```
+
+### Scenario 2: Kubernetes Deployment
+
+**User Request**: "Help me deploy this to Kubernetes"
+
+**Workflow**:
+```
+1. Detect keywords: "deploy", "Kubernetes"
+   → Required: specweave-kubernetes
+
+2. Check installed: /plugin list --installed
+   → Not found
+
+3. Install: /plugin install specweave-kubernetes
+
+4. Notify user:
+   🔌 Installing specweave-kubernetes for K8s deployment...
+   ✅ Installed! You can now generate manifests, Helm charts, and validate deployments.
+
+5. Proceed with K8s expert agent for deployment
+```
+
+### Scenario 3: React Component Development
+
+**User Request**: "Create a new React component for user profile"
+
+**Workflow**:
+```
+1. Detect keywords: "React", "component"
+   → Required: specweave-frontend
+
+2. Check installed: /plugin list --installed
+   → Not found
+
+3. Install: /plugin install specweave-frontend
+
+4. Notify user:
+   🔌 Installing specweave-frontend for React development...
+   ✅ Installed! You can now use frontend expert agent and design system integration.
+
+5. Proceed with component creation
+```
+
+### Scenario 4: Machine Learning Pipeline
+
+**User Request**: "Train a TensorFlow model for image classification"
+
+**Workflow**:
+```
+1. Detect keywords: "TensorFlow", "model", "training"
+   → Required: specweave-ml
+
+2. Check installed: /plugin list --installed
+   → Not found
+
+3. Install: /plugin install specweave-ml
+
+4. Notify user:
+   🔌 Installing specweave-ml for ML workflows...
+   ✅ Installed! You can now use ML expert agent for training pipelines and deployment.
+
+5. Proceed with ML pipeline setup
+```
+
+---
+
+## Error Handling
+
+### Plugin Installation Fails
+
+If `/plugin install` fails:
+
+```
+❌ Failed to install <plugin-name>
+
+Possible causes:
+1. Marketplace not registered
+   → Try: /plugin marketplace add anton-abyzov/specweave
+
+2. Network connectivity issues
+   → Check internet connection and retry
+
+3. Plugin doesn't exist
+   → Verify plugin name: /plugin list (shows all available plugins)
+
+Would you like to:
+a) Retry installation
+b) Proceed without the plugin (limited capabilities)
+c) Troubleshoot further
+```
+
+### Plugin Already Installed
+
+If plugin is already installed, skip installation and proceed:
+
+```
+✅ <plugin-name> is already installed
+   Proceeding with your request...
+```
+
+---
+
+## Integration with Other Skills
+
+**This skill should be consulted BEFORE other skills attempt to use plugin features.**
+
+### Example: increment-planner skill
+
+When increment-planner detects plugin requirements (Step 6), it should:
+
+1. **Detect plugins** (as it already does)
+2. **Consult plugin-installer skill** (NEW!)
+3. **Auto-install missing plugins** (via this skill)
+4. **Then proceed** with increment planning
+
+### Example: docs-preview skill (hypothetical)
+
+```markdown
+# BEFORE using Docusaurus features:
+
+1. Check if specweave-docs-preview is installed
+   → If not: Invoke plugin-installer skill
+   → Auto-install specweave-docs-preview
+
+2. Then launch Docusaurus server
+```
+
+---
+
+## Benefits of This Approach
+
+✅ **Zero friction**: Users don't need to manually install plugins
+✅ **Proactive**: Detects requirements automatically
+✅ **Clear UX**: Users see what's being installed and why
+✅ **Just-in-time**: Only installs plugins when actually needed
+✅ **Fail-safe**: Handles installation errors gracefully
+
+---
+
+## Testing This Skill
+
+**Test Case 1: Docs Preview**
+```
+User: "Show me the internal documentation in a browser"
+
+Expected:
+1. Detects "documentation", "browser" → specweave-docs-preview
+2. Checks installed
+3. Auto-installs if missing
+4. Launches preview
+```
+
+**Test Case 2: K8s Deployment**
+```
+User: "Deploy this application to Kubernetes cluster"
+
+Expected:
+1. Detects "Kubernetes" → specweave-kubernetes
+2. Checks installed
+3. Auto-installs if missing
+4. Proceeds with deployment
+```
+
+**Test Case 3: React Development**
+```
+User: "Add a React component for user settings"
+
+Expected:
+1. Detects "React", "component" → specweave-frontend
+2. Checks installed
+3. Auto-installs if missing
+4. Proceeds with component creation
+```
+
+---
+
+## References
+
+- **Plugin Expert Skill**: Consult for correct installation syntax
+- **Official Docs**: https://code.claude.com/docs/en/plugins
+- **SpecWeave Marketplace**: .claude-plugin/marketplace.json
+- **CLAUDE.md**: Plugin architecture and detection phases
+
+---
+
+**Key Principle**: ALWAYS install plugins BEFORE attempting to use their features. Never fail silently - always notify users of installation steps.
+
+**Last Updated**: 2025-11-10 (v0.10.0)

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)