From cyber-mango
Ticket tracking workflow — sync external tickets (GitHub issues, Jira, Linear) with the Cyber Mango kanban board.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cyber-mango:ticket-trackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When the user mentions an external ticket, issue, or work item from any issue tracker, follow this protocol to sync it with the Cyber Mango board and keep both systems in agreement.
When the user mentions an external ticket, issue, or work item from any issue tracker, follow this protocol to sync it with the Cyber Mango board and keep both systems in agreement.
Activate this protocol when the user references:
https://github.com/org/repo/issues/123)PROJ-100, JIRA-55)ENG-12, CYB-7)Also activate when the user says things like "let's work on the ticket", "check the issue", or "I'm picking up [external reference]".
Extract from the user's message:
123, PROJ-100)Before touching the board, call mem_search with the ticket ID as the query. If a prior session saved a mapping between this ticket and a card ID, retrieve it via mem_get_observation to get the full entry. This prevents duplicate work and recovers cross-session context.
Call get_board and scan the card titles for the ticket reference. Look for the naming pattern [SOURCE-ID] at the start of card titles (e.g., [GH-123], [JIRA-100]). This is the canonical way to identify tracked tickets on the board.
If a card is found via engram mapping but not in the board, assume it was deleted and create a new one.
Call create_card with:
[SOURCE-ID] Brief description — see naming convention belowAfter creating, save the ticket-to-card mapping to engram immediately:
mem_save:
title: "Linked [SOURCE-ID] to card [card_id]"
type: decision
topic_key: ticket-map/[SOURCE-ID]
content:
What: Created card for [SOURCE-ID] on the Cyber Mango board
Why: User referenced this ticket in session
Where: card_id=[card_id], board card title=[card title]
Learned: [any non-obvious detail about the ticket]
Call update_card if any of the following have changed:
Do not call update_card if nothing has changed — unnecessary updates pollute the activity log.
After creating or finding the card, move it to the column that reflects the actual work state:
Card titles MUST follow this exact format:
[SOURCE-ID] Brief description
Examples:
[GH-42] Add OAuth2 support to login flow[GH-123] Fix memory leak in WebSocket handler[JIRA-100] Migrate user table to new schema[ENG-12] Implement rate limiting on API gateway[PROJ-55] Remove deprecated payment providerRules:
GH, Jira -> the project key (e.g., JIRA, PROJ), Linear -> the team key (e.g., ENG)Use this structure for every tracked ticket card:
Source: [Full URL to the original ticket]
Summary:
[1-3 sentence summary of what the ticket is about. Do not just copy the title — add context.]
Acceptance Criteria:
- [Criterion 1, if known]
- [Criterion 2, if known]
- (Add more as they become known)
Notes:
[Any additional context, linked PRs, blocked by, dependencies — update this as work progresses]
If acceptance criteria are not available, write "(Not specified — to be confirmed)" rather than leaving the section empty.
Engram is the source of truth for ticket-to-card mappings across sessions. The board reflects current state. These two systems complement each other:
On any session where a ticket is mentioned, search engram FIRST before touching the board. This prevents duplicate cards and recovers context that is not visible in card titles alone.
When saving to engram, use topic_key: ticket-map/[SOURCE-ID] as a stable identifier so subsequent sessions can find it with a targeted search.
A tracked ticket is complete when ALL of the following are true:
Do not move a ticket to Done unilaterally based on code being merged. Confirm with the user that the ticket's acceptance criteria are met before moving.
When the user asks for the status of a tracked ticket:
get_board to read the current state of the cardDo not report status from memory alone — always read the board to get the current state.
npx claudepluginhub juandagalo/cyber-mango-plugin-go --plugin cyber-mangoGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.