JIRA Digest

Use this skill when analyzing local JIRA transcript snapshots.

Scope

• •Input is transcript text from slack-forge/transcripts/*jira*.md.
• •Do not fetch JIRA/Slack data directly.

Event Types

• •assignment
• •status_change
• •comment
• •mention
• •created
• •priority_change
• •sprint_change
• •resolution

Extraction

For each event capture:

• •ticket
• •event_type
• •summary
• •needs_action

Prioritization

• •Surface actionable items first.
• •Group events by ticket.
• •Summarize high-volume/noisy changes.

Actionability Rules

needs_action: true for:

• •direct assignment to user/team
• •explicit mentions/review requests
• •blockers requiring intervention

Default informational events to false.

Confidence

• •high: clear ticket reference with full event context
• •medium: partial parse — ticket identified but event type or summary unclear
• •low: ambiguous message, no clear ticket reference, or noise that could be JIRA-related

Provenance Requirements

For each digest record, preserve:

• •source channel name and ID
• •source author (bot username that posted the event)
• •source timestamp (timestamp of first event in the digest window)
• •transcript evidence mapping each jira_event entry to a specific message