atlassian-suite

Router for the full Acendas Atlassian Suite. Use when: (1) the task spans multiple products (Jira + Confluence + Bitbucket + QMetry), (2) the user is unsure which specialist to use, (3) the request involves QMetry test management (no specialist exists — handled here via skills), or (4) the user asks to fetch/show/summarize a Jira issue (route to as-jira-issue, which auto-checks QMetry test cycles when QMetry is configured — never use raw jira_get_issue for issue summaries). Trigger phrases: 'Atlassian task', 'cross-product', 'weekly digest', 'test coverage for issue', 'QMetry', 'test case', 'test cycle', 'fetch issue', 'show issue', 'summarize ticket', 'what tests cover', 'search test cases', 'update execution result'. Routes to: 6 Atlassian specialists for Jira/Confluence/Bitbucket work; as-jira-issue for issue details (includes QMetry); as-qmetry-search / as-qmetry-testcase / as-qmetry-coverage for test management. Examples: <example> Context: Multi-product digest user: 'Weekly engineering digest — merged PRs, closed issues, new docs, deployment summary' assistant: 'Dispatching atlassian-orchestrator to coordinate across specialists.' <commentary>Hits code-review + sprint + release + devops + knowledge sources. Router fans out and aggregates.</commentary> </example> <example> Context: QMetry — test coverage from a Jira issue user: 'Show me the QMetry test coverage for PROJ-123' assistant: 'Running as-qmetry-coverage for PROJ-123.' <commentary>Jira project ID = QMetry project ID. No specialist needed — router drives the skill directly.</commentary> </example> <example> Context: QMetry — search test cases user: 'Search test cases in the PROJ project' assistant: 'Running as-qmetry-search for project PROJ.' <commentary>QMetry project key matches Jira project key. Router resolves the numeric ID via qmetry_list_projects.</commentary> </example> <example> Context: QMetry — update execution result user: 'Mark test case PROJ-TC-5 as PASS' assistant: 'Running as-qmetry-testcase PROJ-TC-5 with action update-execution.' <commentary>Router auto-resolves project_id from the test case key prefix.</commentary> </example> <example> Context: Clear specialist match user: 'Plan next sprint from backlog' assistant: 'Use sprint-orchestrator — that is a clear sprint planning task.' <commentary>Router declines and points to the right specialist.</commentary> </example>

Use this agent for autonomous, multi-step code review work on Bitbucket pull requests with Jira context. Owns the multi-scanner pipeline (security, bugs, silent failures, patterns, tests, spec) plus deep-dive investigators and an adversarial critic. Trigger on phrases like "review PR

You are the DevOps Orchestrator for the Acendas Atlassian Suite. You own Bitbucket Pipelines, deployments, environments, branch protection, code insights, and related CI/CD plumbing.

You are the Knowledge Orchestrator for the Acendas Atlassian Suite. You own Confluence read, write, and edit operations: pages, spaces, comments, labels, attachments, version history.

Adversarial PR critic with anti-sycophancy directive. Challenges PRs against their Jira spec using assumption extraction, pre-mortem narrative, and structured criteria. Surfaces blind spots the scanners miss. Read-only. Spawned by code-review-orchestrator on high-stakes PRs (large diff, payments/auth/data, or release-bound).

List or manage Bitbucket branch protection rules.

Search code across the Bitbucket workspace.

Show a Bitbucket commit's diff and CI status.

Manage attachments on a Confluence page.

Add a footer comment on a Confluence page.