Loading...
Loading...
Found 443 Skills
Update a TODO task in One Horizon. Use when asked to "mark this todo done", "update this task", or "edit this TODO". Do not use for initiatives or bug/feature-request updates. Requires One Horizon MCP.
Update initiative tasks in One Horizon, including status, ownership, parent linkage, and taxonomy labels. Use when asked to "update initiative status", "reassign initiative", or "move this under another initiative". Requires One Horizon MCP.
Interact with Basecamp via the Basecamp CLI. Full API coverage: projects, todos, cards, messages, files, schedule, check-ins, timeline, recordings, templates, webhooks, subscriptions, lineup, and campfire. Use for ANY Basecamp question or action.
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
Collaborative problem-solving protocols: write technical specifications (spec, or alspec), create implementation plans (plan, or alplan), or use Align-and-Do Protocol (AAD). Also generates PR/MR descriptions (aldescription).
Final pass to identify missed items, edge cases, and risks before considering a scope done
Manages Atlassian Jira and Confluence via the Rovo MCP Server. Handles MCP setup, OAuth authentication, and troubleshooting. Runs agentic project management: Confluence plans, Jira Epics with child tickets, agent team coordination, and resuming interrupted work from Jira state. Supports uploading images/attachments to Confluence pages via REST API. Reads and writes Confluence page comments (footer, inline, reply threads). Creates git branches linked to Jira tickets (GitHub and Bitbucket). Use this skill whenever the user mentions Jira, Confluence, Atlassian, tickets, epics, sprints, project boards, wiki pages, or Confluence spaces. Also trigger when the user wants to plan a project, break work into tasks, track progress, resume interrupted work, upload images to wiki pages, manage comments on Confluence pages, or create git branches linked to tickets — even if they don't mention Atlassian by name.
Define roles and responsibilities using RACI matrix. Use for process improvement, organizational design, project management, and change initiatives.
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
Create subtasks in Jira from a previously generated task plan. Reads the plan from docs/<TICKET_KEY>-tasks.md and creates one Jira subtask per task under the parent ticket. Use when the user says "create subtasks", "push tasks to Jira", "sync plan to Jira", "create Jira tickets", "make subtasks for PROJECT-1234", or anything about turning a plan into Jira issues. Also triggered by the orchestrating-jira-workflow skill as Phase 4. Requires the task plan to already exist (run planning-jira-tasks first if it does not). Use this skill even if the user just says "push to Jira" or "create the tickets" after a planning phase — those are subtask creation requests.
Retrieve ALL information from a Jira ticket (description, comments, subtasks, attachments metadata, labels, sprint, status, assignee, reporter, linked issues, custom fields, acceptance criteria) and persist it as a single Markdown file. Use whenever the user says "fetch ticket", "retrieve Jira", "pull ticket info", "get ticket details", "look up ticket", "grab the Jira", "what does ticket X say", "check the ticket", "read the ticket", "show me the ticket", or provides a Jira ticket URL or key like PROJECT-1234. Also triggered by the orchestrating-jira-workflow skill as Phase 1 of the end-to-end pipeline. Trigger even if the user only pastes a ticket key with no other context — that alone means "fetch this ticket." This skill ONLY retrieves — it never modifies the ticket or starts implementation.