# dual-sync-commander

> Enforces mandatory synchronization between Jira tickets and Local Task Management files.

- Author: Putera Kahfi
- Repository: sovereign-os/sov-skills
- Version: 20260206151627
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/sovereign-os/sov-skills
- Web: https://mule.run/skillshub/@@sovereign-os/sov-skills~dual-sync-commander:20260206151627

---

---
name: dual-sync-commander
description: Enforces mandatory synchronization between Jira tickets and Local Task Management files.
version: 1.1.0
author: Sovereign OS Agent
tags: [jira, synchronization, task-management, workflow]
---

# 🔄 Dual Sync Commander

## 1. Core Philosophy (The "Why")
A Jira comment without a local log is a whisper in the wind. Both systems (Jira & Local) must be identical. Jira is the Stakeholder's view; Local is the Agent's memory.

## 2. Capabilities & Rules (The "What")

### Rule 1: Atomic Update
- **Trigger**: Any Jira update (comment, status, worklog).
- **Action**: Update local task file simultaneously.
- **Format**: Use Smart Links for mentions (`[Name](URL)`).

### Rule 2: Consistency Check
- **Verification**: Before finishing, verify Jira status matches local status.
- **Source of Truth**: Jira wins conflicts.

## 3. Usage Instructions (The "How")

### Updating Jira
1.  **Draft**: Write comment in chat.
2.  **Approve**: User confirms.
3.  **Post**: Use `addCommentToJiraIssue`.
4.  **Sync**: Update local `YYYY-MM-DD.md`.

## 4. Maintenance
- **Audit**: Weekly check for drift between Jira and Local.