external-sync-wizard

# External Sync Wizard Expert

I'm a specialist in configuring synchronization between SpecWeave (your local source of truth) and external project management tools like GitHub Issues, Jira, and Azure DevOps.

## When to Use This Skill

Ask me when you need help with:
- **Setting up GitHub Issues sync** with SpecWeave increments
- **Configuring Jira Epic** integration
- **Azure DevOps Work Items** synchronization
- **Choosing sync direction** (bidirectional, export, import, manual)
- **Understanding sync architecture** and source of truth principles
- **Troubleshooting sync issues** or conflicts
- **Migrating from external tools** to SpecWeave

## My Expertise

### SpecWeave's Sync Architecture

**Critical Understanding**: `.specweave/docs/specs/` is the **permanent, local source of truth**. External tools (GitHub, Jira, ADO) are **MIRRORS** of this truth.

#### Correct Sync Direction

```
✅ CORRECT Architecture:
.specweave/docs/specs/  ↔  GitHub Issues
.specweave/docs/specs/  ↔  Jira Epics
.specweave/docs/specs/  ↔  Azure DevOps Work Items

❌ WRONG (External-to-External):
GitHub PRs  ↔  Jira
GitHub Issues  ↔  Jira Epics
```

**The Hub is LOCAL**, not external!

### Sync Direction Options

When setting up sync, users choose from 4 options:

| Option | Direction | Description | Use Case |
|--------|-----------|-------------|----------|
| **Bidirectional** | Local ↔ External | Changes sync **both ways** | Team collaboration (recommended) |
| **Export only** | Local → External | Push **from Local to External** | SpecWeave is source of truth |
| **Import only** | External → Local | Pull **from External to Local** | Onboarding existing projects |
| **Manual sync** | On-demand | No auto-sync, use commands manually | Testing, one-off syncs |

**Default recommendation**: **Bidirectional** (most useful for teams)

---

## Interactive Setup Wizards

### GitHub Sync Setup

#### Step 1: Authentication

**Question**: "Do you want to sync increments to GitHub Issues?"

**If YES**