progress-sync

# Progress Sync Expert

I'm the comprehensive progress synchronization expert for SpecWeave. I help you understand and use the `/sw:sync-progress` command for end-to-end progress synchronization.

---

## ⚠️ CRITICAL: AUTO-CREATE IS MANDATORY

**When `/sw:sync-progress` is executed and no external issue exists, it MUST automatically create the issue using the Skill tool.**

The command MUST invoke:
- `Skill({ skill: "sw-github:create", args: "<increment-id>" })` for GitHub
- `Skill({ skill: "sw-jira:create", args: "<increment-id>" })` for JIRA
- `Skill({ skill: "sw-ado:create", args: "<increment-id>" })` for Azure DevOps

**DO NOT just report "No issues linked" - ACTUALLY CREATE THE ISSUE.**

---

## What is /sw:sync-progress?

**The TRUE "single button" to sync progress across all systems**:

```
tasks.md → spec.md ACs → living docs → AUTO-CREATE external issues → sync external tools (GitHub/JIRA/ADO)
```

**One command does EVERYTHING - including creating missing external issues!**
```bash
/sw:sync-progress
```

**No more "No GitHub issue linked" errors!** The command auto-creates missing issues.

### ✅ Archived Increment Behavior

**For archived/completed increments, this command ALWAYS creates issues for historical tracking:**

| Situation | Action |
|-----------|--------|
| Issue EXISTS | ✅ Sync final state + Close/Transition |
| NO issue linked | ✅ AUTO-CREATE + IMMEDIATELY CLOSE (historical tracking) |

**Why?** Historical tracking is important! Completed work should have external issues for:
- Team visibility
- Sprint retrospectives
- Release notes generation
- Audit trails

**For all increments (active or completed)**: Auto-creates issues if missing (the "single button" philosophy)

---

## When to Use This Command

### ✅ Use /sw:sync-progress when:

1. **First-time sync (no external issue yet)**: Just created increment, want to sync → auto-creates GitHub/JIRA/ADO issues!
2. **After completing tasks**: You've marked tasks as done in tasks.md and want to syn