From slack-forge
Guidance for parsing JIRA bot activity from local transcript files and producing actionable digests.
How this skill is triggered — by the user, by Claude, or both
Slash command
/slack-forge:jira-digestThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when analyzing local JIRA transcript snapshots.
Use this skill when analyzing local JIRA transcript snapshots.
slack-forge/transcripts/*jira*.md.For each event capture:
ticketevent_typesummaryneeds_actionneeds_action: true for:
Default informational events to false.
high: clear ticket reference with full event contextmedium: partial parse — ticket identified but event type or summary unclearlow: ambiguous message, no clear ticket reference, or noise that could be JIRA-relatedStructure the digest content as an executive briefing:
Title format: "JIRA Digest — {date} ({timeframe})"
Never use "Untitled" as the title.
For each digest record, preserve:
jira_event entry to a specific messagenpx claudepluginhub jeremybrice/the-forge --plugin slack-forgeExtracts action items and assignees from meeting notes or Confluence pages, looks up Jira account IDs, and creates tasks.
Extracts action items, commitments, assignments, and follow-ups from Fireflies meeting transcripts for all attendees (default) or a specific person using parallel subagents and MCP tools.
Generates short Jira comments from git commits summarizing shipped features or bug fixes with root cause analysis. Fetches issue details via Atlassian MCP and saves as local markdown report.