sync-to-jiralisted

# Sync to Jira ## Skill Info Part of the **spec-manager** agent. This skill takes the finalized `specs.md` and/or `plans.md` for a slug and pushes them back into the linked Jira issue's `description` (or a configured custom field), wrapping the content with marker comments so the same region can be updated repeatedly. The actual markdown → ADF conversion and the PUT call live in the Jira MCP server (tool: `jira_update_ticket_from_markdown`). This skill is the **orchestration layer**: detection, payload assembly, diff confirmation, and result reporting. ## Input `/sync-to-jira <slug> [--target=spec|plan|both] [--field=description|customfield_<id>]` Flags: | Flag | Values | Default | Effect | |------|--------|---------|--------| | `--target` | `spec` / `plan` / `both` | `both` | Which documents to include in the payload. | | `--field` | `description` or `customfield_<id>` | `description` | Where on the Jira issue to write. `description` uses marker splice; custom fields are overwritten. | If `<slug>` is omitted, list slugs in `specs/` and ask the user to pick. ## Markers The skill uses two marker strings to delimit the region inside Jira's description that it owns: - `markerStart`: `<!-- sdd:start -->` - `markerEnd`: `<!-- sdd:end -->` These are passed to `jira_update_ticket_from_markdown` so subsequent syncs replace only the bounded region. The first sync to a ticket appends a new marker block at the end of the description (the MCP tool reports `mode: "append-marke