Review Jira delivery risk
Connect Atlassian and prepare a weekly brief of blocked, overdue, and unowned work against the plan.
The Jira delivery risk review template reads a Jira project and any linked
Confluence plan pages, then reports blocked, overdue, and unowned work with
the issue or page cited behind every finding. It follows the marketing-plan
skill's execution-review posture: compare progress against stated plan dates
without inventing status.
Enable and connect Atlassian
An operator must enable MANAGED_MCP_ATLASSIAN_ENABLED. Then connect the
Atlassian card and complete Atlassian's consent flow for your site. Access
follows your own Jira and Confluence permissions; Work on Repeat requests no
scope beyond what Atlassian's server assigns during client registration.
Current beta boundary
Atlassian is connection-only until exact authenticated tool schemas are captured and reviewed, so the packaged routine ships as a preview. After review, the first manifest should stay read-only: project, board, sprint, issue, and page reads. Issue creation and transitions, page edits, and deletions must remain blocked or approval-gated.
Recovery
If authorization expires or is revoked, the connection moves to
reauthorization_required; reconnect the same card to update it in place.
Site admins can also revoke the grant from Atlassian's connected-apps
settings.