TaskPacer
Back to action plan
A power comboSource-backedVerified 2026-04-20

Project Manager / Manage the RAID log (risks, assumptions, issues, dependencies) and decision records

Combine Atlassian Intelligence + Claude to keep the RAID log in sync with Jira

Use Atlassian Intelligence to link risks and issues in Confluence to Jira tickets automatically. Each Friday, export the linked RAID tables and run them through Claude to produce a one-page RAID briefing for the steering committee: top 5 risks by severity × likelihood, top 3 blocked dependencies, and recommended decisions. The RAID log stops being a spreadsheet graveyard and becomes a working document.

Tool

Atlassian Intelligence + Claude.ai

Open tool

Best for

Coordination

Atlassian Intelligence add-on ≈$10/user/mo · Claude Pro $20/mo

Setup

45 min

One-time setup estimate

Workflow

  1. 1Collect the source material for "Manage the RAID log (risks, assumptions, issues, dependencies) and decision records" before opening the tool.
  2. 2Run the starter prompt in Atlassian Intelligence + Claude.ai and paste in the real context.
  3. 3Review the output for accuracy, tone, names, numbers, and policy-sensitive details.
  4. 4Save the improved prompt or checklist so the next run takes less time.

Inputs you need

  • - Project Manager
  • - Manage the RAID log (risks, assumptions, issues, dependencies) and decision records
  • - Examples, notes, files, or customer context for this task
  • - Your preferred tone, constraints, and final format

Expected output

  • - Combine Atlassian Intelligence + Claude to keep the RAID log in sync with Jira
  • - A usable draft or workflow for manage the raid log (risks, assumptions, issues, dependencies) and decision records
  • - A repeatable prompt you can improve after each run

Ready-to-copy asset

Starter prompt

Here is this week's RAID extract from Confluence/Jira: [PASTE]. Produce a one-page RAID briefing: 1) top 5 risks ranked by severity × likelihood with mitigation status, 2) top 3 blocked or at-risk dependencies with the unblocker ask, 3) recommended decisions for steering committee. Keep it under 400 words. Flag anything stale (>14 days no update).

Caveats

  • - Do a human review before sending, publishing, filing, or making a decision.
  • - Verify numbers, names, claims, citations, and compliance-sensitive details.
  • - AI drafts. You decide. Final responsibility is yours.

Measurable value

30 min saved per run

Before: 40 min. After: 10 min.

Back to action planUnlock more solutions