tracker-sync

Files (1)

• SKILL.md

SKILL.md (first lines)

# tracker-sync — one source of truth per artifact

Legacy systems already hold records that auditors accept. The loop fits around them: for each artifact one
system is the truth and the other holds a copy or a link.

Read `sdlc.config.json`: `sourceOfTruth`, `tracker.type` (`jira | youtrack | gitlab | github | none`),
`tracker.baseUrl`, `tracker.project`.

## Modes

| `sourceOfTruth` | Authoritative | At session start | After committing an artifact |
|---|---|---|---|
| `repo` | Markdown in Git | nothing required | add a comment/link on the record: artifact path + commit SHA + PR URL |
| `tracker` | the tracker record | read the record; treat the Markdown as a working copy; if they differ, the record wins and you update the Markdown | write the outcome back: summary of intent/spec/plan, status transition if the workflow allows, commit SHA, PR URL |
| `linked` | both, cross-referenced | read the record if a `tracker:` id exists | ensure the artifact frontmatter has `tracker: <id>` and the record has the commit SHA (comment or custom field) |

## Connector usage

- **Jira (Atlassian MCP)**: `getJiraIssue`, `addCommentToJiraIssue`, `editJiraIssue`, `transitionJiraIssue`
  (tool names as exposed by `https://mcp.atlassian.com/v1/sse`). Never move a ticket to Done; humans close.
- **YouTrack MCP** (`<baseUrl>/mcp`): search/read issue, add comment, update fields.
- **GitLab MCP** (`<baseUrl>/api/v4/mcp`): issues and merge requests; write the SHA as an issue note.
- **GitHub MCP**: issues and PRs; write the SHA as an issue comment.
- If no connector is configured, print the exact text to paste into the record and the exact `tracker:` value
  to put in the frontmatter, and continue.

## Rules

- Tickets are `tracker:` ids in frontmatter; commits keep `SDLC-Change:`; records get the SHA. That linkage is
  the minimum bar and is enough for an auditor to walk from ticket to code and back.
- Never create tickets unless asked; never change assignees, priorities or close records.
- Write back **in the same session** that produced the artifact, so the record and the file share a timestamp.

From bibutikoley/ai-sdlc-claude, MIT.

More from bibutikoley/ai-sdlc-claude