Loading...
Loading...
Found 5 Skills
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
Reference guide for the Atlassian CLI (acli) - a command-line tool for interacting with Jira Cloud and Atlassian organization administration. Use this skill when the user wants to perform Jira operations (create/edit/search/transition work items, manage projects, boards, sprints, filters, dashboards), administer Atlassian organizations (manage users, authentication), or automate Atlassian workflows from the terminal. Covers all acli commands including: jira workitem (create, edit, search, assign, transition, comment, clone, link, archive), jira project (create, list, update, archive), jira board/sprint, jira filter/dashboard, admin user management, and rovodev (Rovo Dev AI agent). Requires an authenticated acli binary already installed on the system.
Execute a single task from a Jira task plan using a structured pipeline of specialist subagents: planning, testing, refactoring, implementation, documentation, code-quality review, architecture review, security audit, and requirements verification. The user must specify which task number to execute. Use when the user says "execute task 3", "work on task 2", "implement task 1", "start task 5 for PROJECT-1234", or "run task N". Also triggered by the orchestrating-jira-workflow skill as Phase 5 of the end-to-end pipeline (called once per task). Requires that the task plan exists at docs/<TICKET_KEY>-tasks.md. Executes ONLY the specified task — never continues to the next one without explicit user approval.
Interact with Atlassian Jira and Confluence using REST APIs — no MCP server needed. Use this skill whenever the user mentions Jira, Confluence, Atlassian, tickets, issues, sprints, backlogs, epics, stories, or any project management task that involves creating/editing/searching/transitioning Jira issues, writing or reading Confluence pages, generating status reports, triaging bugs, converting specs to backlogs, capturing tasks from meeting notes, searching company knowledge, syncing local BMAD documents with Jira or Confluence, pushing docs to Jira, pulling from Jira, linking documents to tickets, downloading Confluence spaces to local markdown, or converting between Confluence storage format and markdown. Also trigger when the user says things like "move that ticket to done", "what's the status of PROJ-123", "create a bug for X", "search our wiki for Y", "file a ticket", "check for duplicates", "write a status update", "break this spec into stories", "sync this doc", "push to jira", "pull from jira", "sync to confluence", "link this to jira", "sync my epics", "download confluence pages", "sync confluence space", "convert confluence to markdown", or "pull docs from confluence". If there is even a chance the user wants to interact with Jira or Confluence, use this skill.
Use when needing to search Jira issues, retrieve issue details, get pull request links, or manage issue workflows programmatically - provides complete workflows and examples for common Jira automation tasks using the atlassian CLI