Loading...
Loading...
Found 100 Skills
Use for time-based grouping of issues into delivery phases. Creates, updates, and tracks milestones, associates issues and epics, monitors progress toward milestone completion.
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
Unified task execution protocol for Codex-only work. Supports Single Task, Epic Task, and Batch Task while preserving CSV truth-source, validation gates, context recovery, and Debug-First failure exposure. WHEN TO USE: user asks to "track tasks", "create todo list", "make a plan", "track progress", "long task", "big project", "build from scratch", "autonomous session", "跟踪任务", "自主执行", "长时任务", "从零开始", "任务管理", "做个计划", "大工程", or when a task clearly requires 3+ ordered steps that produce file changes. DO NOT USE: single-step fixes, pure Q&A, code review, explaining code, search/research tasks, tasks with fewer than 3 steps, or tasks that do not produce file changes.
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
Coordinates 3 specialized audit workers (query efficiency, transaction correctness, runtime performance). Researches DB/ORM/async best practices, delegates parallel audits, aggregates results into single Linear task in Epic 0.
James Bach's HTSM Product Factors (SFDIPOT) analysis for comprehensive test strategy generation. Use when analyzing requirements, epics, or user stories to generate prioritized test ideas across Structure, Function, Data, Interfaces, Platform, Operations, and Time dimensions.
Explore and manage Azure DevOps work items: Epics, Features, User Stories, and Tasks. Provides project overview (tree), get epic, get feature, create work item, and edit work item modes. Use when the user wants to list epics, view features, browse work items, create tasks, edit user stories, or explore the backlog in Azure DevOps.
Turn a PRD into a traceable Memory Bank with product, requirements, epics, and features.
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
This skill should be used when a user wants to create a task, write a ticket, decompose a feature into implementable work, break down a story, define a vertical slice for development, or write Gherkin scenarios — for example "create a task", "write a task for this feature", "break this feature into tasks", "define implementation work", or "add a sub-issue to this feature". Guides creation of a GitHub Task issue linked to a parent Feature and Epic, derives Gherkin acceptance scenarios from the Feature's ACs, enforces DDD ubiquitous language in scenarios, and checks for vertical-slice integrity and task dependencies.
Platform submission processes, certification requirements, and distribution across Steam, Epic, console, and mobile platforms.
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.