Jira
ProductivityCommonly used with
Skills using Jira (398)
cs-project-manager
Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills.
jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
clickup-migration-deep-dive
Migrate to ClickUp from other project management tools (Jira, Asana, Trello) or migrate data between ClickUp workspaces using API v2. Trigger: "migrate to clickup", "clickup migration", "jira to clickup", "asana to clickup", "trello to clickup", "clickup data migration", "move tasks to clickup", "clickup import".
linear-migration-deep-dive
Migrate from Jira, Asana, GitHub Issues, or other tools to Linear. Use when planning a migration, executing data transfer, or mapping workflows between issue tracking tools. Trigger: "migrate to linear", "jira to linear", "asana to linear", "import to linear", "linear migration", "github issues to linear".
jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
progressive-estimation
Estimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops
pm-skills
6 project management agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Senior PM, scrum master, Jira expert (JQL), Confluence expert, Atlassian admin, template creator. MCP integration for live Jira/Confluence automation.
jira-ticket-generator
Generate jira ticket generator operations. Auto-activating skill for Enterprise Workflows. Triggers on: jira ticket generator, jira ticket generator Part of the Enterprise Workflows skill category. Use when working with jira ticket generator functionality. Trigger with phrases like "jira ticket generator", "jira generator", "jira".
jira-workflow-creator
Create jira workflow creator operations. Auto-activating skill for Enterprise Workflows. Triggers on: jira workflow creator, jira workflow creator Part of the Enterprise Workflows skill category. Use when working with jira workflow creator functionality. Trigger with phrases like "jira workflow creator", "jira creator", "jira".
building-vulnerability-dashboard-with-defectdojo
Deploy DefectDojo as a centralized vulnerability management dashboard with scanner integrations, deduplication, metrics tracking, and Jira ticketing workflows.
implementing-ticketing-system-for-incidents
Implements an integrated incident ticketing system connecting SIEM alerts to ServiceNow, Jira, or TheHive for structured incident tracking, SLA management, escalation workflows, and compliance documentation. Use when SOC teams need formalized incident lifecycle management with automated ticket creation, assignment routing, and resolution tracking.
team-collaboration-standup-notes
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
api-connector-builder
Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.
jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.
scrum-master
Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.
jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
daily-meeting-update
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
openspec-ff-change
Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually.
atlassian-mcp
Integrates with Atlassian products to manage project tracking and documentation via MCP protocol. Use when querying Jira issues with JQL filters, creating and updating tickets with custom fields, searching or editing Confluence pages with CQL, managing sprints and backlogs, setting up MCP server authentication, syncing documentation, or debugging Atlassian API integrations.
atlassian-admin
Atlassian Administrator for managing and organizing Atlassian products (Jira, Confluence, Bitbucket, Trello), users, permissions, security, integrations, system configuration, and org-wide governance. Use when asked to add users to Jira, change Confluence permissions, configure access control, update admin settings, manage Atlassian groups, set up SSO, install marketplace apps, review security policies, or handle any org-wide Atlassian administration task.
atlassian-templates
Atlassian Template and Files Creator/Modifier expert for creating, modifying, and managing Jira and Confluence templates, blueprints, custom layouts, reusable components, and standardized content structures. Use when building org-wide templates, custom blueprints, page layouts, and automated content generation.
confluence-expert
Atlassian Confluence expert for creating and managing spaces, knowledge bases, and documentation. Configures space permissions and hierarchies, creates page templates with macros, sets up documentation taxonomies, designs page layouts, and manages content governance. Use when users need to build or restructure a Confluence space, design page hierarchies with permission structures, author or standardise documentation templates, embed Jira reports in pages, run knowledge base audits, or establish documentation standards and collaborative workflows.
jira-expert
Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations.
jira
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
n8n-workflow-patterns
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.
044-planning-jira
Use when you need the Jira CLI (`jira`) to verify installation, configure Jira Cloud access, list issues (all or by JQL) as markdown tables, and fetch issue descriptions and comments for analysis. Uses an interactive install gate - if `jira` is missing, ask whether to show installation guidance before any issue commands. This should trigger for requests such as jira issue list; List Jira issues; Jira JQL issue query; jira issue view comments; Jira CLI issue workflow. Part of cursor-rules-java project
technical-spec-template
Create structured technical specification documents that bridge product requirements and engineering implementation. Use when writing a tech spec, engineering spec, system design doc, or API specification. Produces a complete spec with problem statement, proposed solution, data model, API design, alternatives considered, security considerations, testing plan, and rollout strategy.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
competitive-analysis
Competitive analysis - feature matrix, SWOT, market positioning, benchmark.
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check security alerts, manage variable groups, approve deployments, or configure branch policies. Covers 13 domains with 99 tools via REST API.
deep-research
Execute autonomous multi-step research using Google Gemini Deep Research Agent. Use for: market analysis, competitive landscaping, literature reviews, technical research, due diligence. Takes 2-10 minutes but produces detailed, cited reports. Costs $2-5 per task.
elevenlabs
Convert documents and text to audio using ElevenLabs text-to-speech. Use this skill when the user wants to create a podcast, narrate a document, read aloud text, generate audio from a file, or convert text to speech.
gmail
Interact with Gmail - search emails, read messages, send emails, create drafts, and manage labels. Use when user asks to: search email, read email, send email, create email draft, mark as read, archive email, star email, or manage Gmail labels. Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication.
google-calendar
Interact with Google Calendar - list calendars, view events, create/update/delete events, and find free time. Use when user asks to: check calendar, schedule a meeting, create an event, find available time, list upcoming events, delete or update a calendar event, or respond to meeting invitations. Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication.
google-docs
Interact with Google Docs - create documents, search by title, read content, and edit text. Use when user asks to: create a Google Doc, find a document, read doc content, add text to a doc, or replace text in a document. Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication.
google-drive
Interact with Google Drive - search files, find folders, list contents, download files, upload files, create folders, move, copy, rename, and trash files. Use when user asks to: search Google Drive, find a file/folder, list Drive contents, download or upload files, create folders, move files, or organize Drive content. Lightweight integration with standalone OAuth authentication supporting full read/write access.
google-sheets
Read and write Google Sheets spreadsheets - get content, update cells, append rows, fetch specific ranges, search for spreadsheets, and view metadata. Use when user asks to: read a spreadsheet, update cells, add data to Google Sheets, find a spreadsheet, check sheet contents, export spreadsheet data, or get cell values. Lightweight integration with standalone OAuth authentication supporting full read/write access.
google-slides
Read and write Google Slides presentations - get text, find presentations, create presentations, add slides, replace text, and manage slide content. Use when user asks to: read a presentation, create slides, find slides, add a slide, replace text in a presentation, or manage presentation content. Lightweight integration with standalone OAuth authentication supporting full read/write access.
imagen
Generate images using Google Gemini's image generation capabilities. Use this skill when the user needs to create, generate, or produce images for any purpose including UI mockups, icons, illustrations, diagrams, concept art, placeholder images, or visual representations.
jules
Delegate coding tasks to Google Jules AI agent for asynchronous execution. Use when user says: 'have Jules fix', 'delegate to Jules', 'send to Jules', 'ask Jules to', 'check Jules sessions', 'pull Jules results', 'jules add tests', 'jules add docs', 'jules review pr'. Handles: bug fixes, documentation, features, tests, refactoring, code reviews. Works with GitHub repos, creates PRs.
manus
Delegate complex, long-running tasks to Manus AI agent for autonomous execution. Use when user says 'use manus', 'delegate to manus', 'send to manus', 'have manus do', 'ask manus', 'check manus sessions', or when tasks require deep web research, market analysis, product comparisons, stock analysis, competitive research, document generation, data analysis, or multi-step workflows that benefit from autonomous agent execution with parallel processing.
mssql
Execute read-only SQL queries against multiple Microsoft SQL Server databases. Use when: (1) querying MSSQL/SQL Server databases, (2) exploring database schemas/tables, (3) running SELECT queries for data analysis, (4) checking database contents. Supports multiple database connections with descriptions for intelligent auto-selection. Blocks all write operations (INSERT, UPDATE, DELETE, DROP, etc.) for safety.
mysql
Execute read-only SQL queries against multiple MySQL databases. Use when: (1) querying MySQL databases, (2) exploring database schemas/tables, (3) running SELECT queries for data analysis, (4) checking database contents. Supports multiple database connections with descriptions for intelligent auto-selection. Blocks all write operations (INSERT, UPDATE, DELETE, DROP, etc.) for safety.
notebooklm
Query and manage Google NotebookLM notebooks with persistent profile auth, source sync, batch/multi queries, and structured exports. Use when user asks to query NotebookLM, 'ask my notebook', shares NotebookLM notebook URLs, wants to list/create notebooks, manage sources, do bulk folder sync, dedupe, or audit exports.
outline
Search, read, and manage Outline wiki documents. Use when: (1) searching wiki for documentation, (2) reading wiki pages or articles, (3) listing wiki collections or documents, (4) creating or updating wiki content, (5) exporting documents as markdown. Works with any Outline wiki instance (self-hosted or cloud).
postgres
Execute read-only SQL queries against multiple PostgreSQL databases. Use when: (1) querying PostgreSQL databases, (2) exploring database schemas/tables, (3) running SELECT queries for data analysis, (4) checking database contents. Supports multiple database connections with descriptions for intelligent auto-selection. Blocks all write operations (INSERT, UPDATE, DELETE, DROP, etc.) for safety.
product-data-audit
Use when auditing a product, business, or project ecosystem — analyzing data sources, decision loops, bottlenecks, and implementation contours. Triggers on "аудит продукта", "product audit", "data audit", "аудит данных", "аудит бизнеса", "проанализируй экосистему", "аудит систем".
attach-jira-issue
Use this skill only when the user explicitly invokes /attach-jira-issue to upload one or more local files as attachments to a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Shows a preview of what will be uploaded and requires explicit confirmation before POSTing.
comment-jira-issue
Use this skill only when the user explicitly invokes /comment-jira-issue to add, list, edit, or delete comments on a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Subcommands: add (post a new comment), list (fetch all comments with pagination), edit (update an existing comment), delete (remove a comment — irreversible). Write subcommands show a payload preview and require explicit confirmation before calling the API.
create-jira-issue
Use this skill only when the user explicitly invokes /create-jira-issue to create a new Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts a project key, issue type, summary, optional Markdown body, and optional fields (assignee, priority, labels, components, parent, custom fields). Converts the body to ADF, shows a payload preview, requires explicit confirmation, then POSTs to Jira and returns the new issue key.
init-jira
Set up the Jira Cloud integration for this project. Verifies credentials against a real Jira Cloud tenant, discovers the tenant's custom-field catalogue and project list, and persists the results under `<paths.integrations>/jira/` (default `.accelerator/state/integrations/jira/`) as team-shared, version-controlled JSON caches. Idempotent: safe to re-run after credential or project changes.
search-jira-issues
Use this skill whenever the user wants to search, list, or filter Jira tickets — by assignee, status, label, project, type, component, reporter, parent, or free text — even if they say 'find', 'show me', 'what's open', 'list my tickets', or similar phrasing rather than 'search Jira'. Composes safe JQL from structured flags, executes a paginated search against a Jira Cloud tenant, and renders a summary table of the results. Supports --render-adf to convert ADF descriptions to Markdown inline. Prefer this skill over raw JQL whenever the user's intent maps to a structured flag.
show-jira-issue
Use this skill when the user asks about a specific Jira issue by key (e.g. PROJ-123, ENG-456) — for viewing the description, status, comments, transitions, or any other field. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' a key, or asks any direct question about an issue they reference. Do NOT trigger when an issue key appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.
transition-jira-issue
Use this skill only when the user explicitly invokes /transition-jira-issue to move a Jira issue through its workflow by state name. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts an issue key and target state name (case-insensitive). Shows a transition preview and requires explicit confirmation before posting.
update-jira-issue
Use this skill only when the user explicitly invokes /update-jira-issue to modify an existing Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts an issue key and at least one mutating flag (summary, body, priority, assignee, labels, components, parent, custom fields). Shows a payload preview with explicit set-vs-update label semantics, requires explicit confirmation, then PUTs to Jira.
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows
jira
Jira Cloud integration for issue management and search. This skill should be used when working with Jira tickets, searching issues with JQL, creating or updating issues, adding comments, or transitioning issue status. Covers REST API v3 and Jira Query Language.
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
nathan-standards
Development standards for the Nathan n8n-Jira agent automation system. Covers n8n workflows, Python patterns, and project conventions.
mkconfluence-spec-analyst
Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).
mkintake
Ticket/PRD intake: product area classification, completeness scoring, RCA, technical assessment. Works with Jira (via mk:jira-issue / jira-as), Linear (via MCP), GitHub (via gh CLI), or manual paste. Triggers: 'analyze ticket', 'intake PRD', 'triage issue', 'classify ticket', 'check ticket'.
mkjira-agile
JIRA agile via the jira-as wrapper: epics, sprints, backlog, ranking, story points, subtasks, velocity. Triggers: 'create sprint', 'add KEY to sprint', 'set story points on KEY', 'rank KEY before KEY', 'velocity for board', 'epic add'. Board ID ≠ project key. NOT for issue CRUD (mk:jira-issue); NOT for time tracking (mk:jira-time).
mkjira-lifecycle
Drive JIRA workflow lifecycle via the jira-as wrapper: transition, assign, resolve, reopen, manage versions and components. Triggers: 'transition KEY to Status', 'mark KEY as Done', 'assign KEY to user', 'reopen KEY', 'release version', 'create component'. NOT for issue CRUD (mk:jira-issue); NOT for bulk transitions (mk:jira-bulk).
daily-meeting-update
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
acli
Atlassian CLI (official `acli` binary, v1.3+ as of 2026) for Jira Cloud, Confluence Cloud, and org admin tasks from the terminal. Use whenever the user wants to create, view, edit, transition, assign, clone, archive, comment on, link, or bulk-operate on Jira work items; list or manage projects, boards, sprints, filters, dashboards, or custom-field definitions; create or update Confluence spaces, pages, or blog posts; activate/deactivate users at the org level; or authenticate to Atlassian from a shell or CI pipeline. Triggers on: `acli`, Atlassian CLI, Jira from the terminal, Confluence from the terminal, bulk Jira operations, scripting Jira, automate Jira tickets, transition a bunch of issues, create issues from a JSON/CSV file, CI pipeline that touches Jira, log in to Jira CLI, switch Atlassian sites, API-token auth for Jira. Use this skill even when the user does not say the word `acli` — if the task is CLI-driven Jira or Confluence work, this is the right tool. Do NOT use for: Atlassian MCP server work (t
agentic-qa-onboard
Walks new users through this repo's QA flow — Playwright + KATA + Allure + Xray stack, Jira QA workflow (Backlog → Shift-Left QA → Estimation → Ready For Dev → Ready For QA → In Testing → Tested → Closed), /shift-left-testing for pre-sprint AC refinement on backlog Stories, /sprint-testing for in-sprint manual QA, /test-documentation for TMS test cases, /test-automation for KATA-compliant E2E/API tests, /regression-testing for CI suite execution, /framework-development for boilerplate evolution, MCPs available (Context7, Tavily, Atlassian, Playwright, DBHub, OpenAPI, Postman), critical env vars. ALSO the front desk for anyone who is lost or wants to understand how the repo or any workflow skill works — conceptually AND visually: it explains in plain human language (suspending caveman/compressed register) and can open per-skill how-it-works presentations (English + Spanish) in the user's default browser after asking. Triggers on: `onboard me to QA`, `explain this QA repo`, `first time using this`, `primer vez
judgment-day
Trigger: judgment day, dual review, adversarial review, juzgar. Run blind dual review, fix confirmed issues, then re-judge.
shift-left-testing
Orchestrates pre-sprint Shift-Left QA on a batch of backlog Stories. Use when the user wants to refine acceptance criteria, surface ambiguities + gaps, draft an ATP outline, and hand off to PO/Dev BEFORE the Story enters a sprint — so defects are prevented in the requirements, not detected after implementation. Triggers on: shift-left testing, shift-left these stories, groom the backlog, pre-sprint QA, refine these N stories, pre-sprint refinement batch, prepare backlog for sprint planning, run AC refinement on UPEX-100/101/102, run shift-left QA, do early-game testing, pre-sprint test planning. ALSO trigger when the user pastes a comma-separated list of Story IDs sitting in Backlog / Shift-Left QA / Estimation / Ready For Dev and asks any variant of "refine", "groom", "clean these ACs", "shift-left these". Do NOT use for: in-sprint manual QA per ticket (use /sprint-testing — entry status is Ready For QA, this skill's entry status is Backlog/Shift-Left QA), Stage 4 TMS documentation + ROI (test-documentation)
xray-cli
Xray Cloud test management via `bun xray` CLI: create/list tests, manage test executions and plans, import JUnit/Cucumber/Xray JSON results, update run statuses, back up and restore projects, link defects. Triggers on: create a test in Xray, import test results to Xray, list Xray executions, update run status, backup Xray project, restore Xray tests, link defect to run, sync tests, Xray auth login. Do NOT use for: writing automated tests (test-automation); documenting test cases or ROI analysis (test-documentation); running CI regression suites (regression-testing); browser automation (playwright-cli).
add-integration
Add a new third-party integration (Jira/Linear-style) — per-workspace credentials, 90s auth-health poller, settings page, link/import buttons. Use when scaffolding a new external service integration.
atlassian
Manage Jira issues and Confluence wiki pages in Atlassian Cloud. Use when: (1) searching/creating/updating Jira issues with JQL, (2) searching/reading/creating Confluence pages with CQL, (3) managing Jira workflows, transitions, and comments, (4) browsing Confluence spaces and page hierarchies. Supports OAuth 2.1 via MCP server (recommended) or API token authentication (fallback).
google-chat
Interact with Google Chat - list spaces, send messages, read conversations, and manage DMs. Use when user asks to: send a message on Google Chat, read chat messages, list chat spaces, find a chat room, send a DM, or create a new chat space. Lightweight alternative to full Google Workspace MCP server with standalone OAuth authentication.
google-tts
Convert documents and text to audio using Google Cloud Text-to-Speech. Use this skill when the user wants to: narrate a document, read aloud text, generate audio from a file, convert text to speech, create a recording of documentation or analysis, create a podcast from a document, or use Google TTS/text-to-speech. Trigger phrases: "read this aloud", "narrate this", "create a recording", "text to speech", "TTS", "convert to audio", "audio from document", "listen to this", "generate audio", "google tts", "create a podcast".
bug-analyzer
Use when the user shares a Sentry error, Jira bug ticket, or error description and wants root cause analysis. Also for proactive bug hunting and code audits for hidden bugs.
bug-investigate
Investigate a bug — auto-detect ticket from branch, gather Jira/Sentry/description context, trace root cause
challenge-mevision
Stress-test a plan or idea by one-question-at-a-time interview until 95% confidence — emits a copyable Markdown vision pitch for tickets, roadmaps, or fresh-chat handoff.
command-routing
Use when the user invokes a slash command like /create-pr, /commit, /fix-ci, or pastes command file content — routes to the right command with context inference and GitHub API patterns.
conventional-commits-writing
Use when writing commit messages or squash-merge titles — `feat:`, `fix:`, `chore:`, scopes, breaking changes — even when the user just says 'commit this' without naming Conventional Commits.
featureplan
Interactively plan a feature — research, discuss, and create a structured feature document
kelos
Author, debug, and operate Kelos resources (Task, Workspace, AgentConfig, TaskSpawner) on Kubernetes. Use when working with Kelos CRDs or the kelos CLI.
mkjira-admin
JIRA project / user / group / scheme / automation administration via the jira-as wrapper (11 sub-domains, ~65 verbs). Triggers: 'create JIRA project', 'list users', 'delete user USERNAME', 'list permission schemes', 'create group NAME'. Requires admin role. Destructive ops (project/user/group delete) require 2-step token confirmation. NOT for per-issue ops (mk:jira-issue / mk:jira-lifecycle); NOT for JSM admin (mk:jira-jsm).
mkjira-analyst
Full Jira ticket context analysis via the jira-analyst agent — including media (attached images / PDFs / screenshots) and linked issues. Produces structured findings suitable for posting back as a Jira comment. Read-only. Triggers: 'analyze KEY', 'rca for KEY', 'describe KEY with media'. NOT for complexity scoring (mk:jira-evaluator); NOT for story-point estimation (mk:jira-estimator).
mkjira-bulk
Bulk JIRA operations on 10+ issues via the jira-as wrapper: bulk transition / assign / set-priority / clone / delete. Dry-run is MANDATORY first. Triggers: 'bulk update N issues', 'mass transition', 'transition 50+ issues to Done', 'bulk-clone', 'bulk-delete'. NOT for single-issue ops (mk:jira-issue / mk:jira-lifecycle).
mkjira-collaborate
Manage JIRA collaboration surface via the jira-as wrapper: comments, attachments, watchers, notify. Triggers: 'comment on KEY', 'add attachment to KEY', 'watch KEY', 'notify KEY watchers'. Internal-vs-public comment safety enforced. NOT for issue CRUD (mk:jira-issue); NOT for issue links (mk:jira-relationships).
mkjira-dev
Generate developer artifacts from Jira tickets via the jira-as wrapper: branch names, PR descriptions, parsed commits, commit/PR-to-issue links. Triggers: 'branch name for KEY', 'PR description for KEY', 'parse commits for issue keys', 'link PR to KEY'. NOT for executing git/gh commands directly (mk:ship); NOT for issue CRUD (mk:jira-issue).
mkjira-estimator
Heuristic story-point estimation for a single Jira ticket via the jira-estimator agent. Read-only. Triggers: 'estimate KEY', 'story points for KEY', 'how complex is KEY'. NOT for complexity-only analysis (mk:jira-evaluator); NOT for full RCA (mk:jira-analyst).
mkjira-evaluator
Evaluate Jira ticket complexity + inconsistencies via the jira-evaluator agent. Read-only. Triggers: 'evaluate KEY', 'analyze ticket complexity for KEY', 'check ticket quality for KEY'. NOT for estimation (mk:jira-estimator); NOT for full RCA (mk:jira-analyst).
mkjira-fields
JIRA custom field discovery + configuration via the jira-as wrapper. Triggers: 'field ID for X', 'list custom fields', 'check fields for project PROJ', 'configure agile fields for board'. Read ops are open; create/configure-agile require admin. NOT for setting per-issue field values (mk:jira-issue update).
mkjira-issue
JIRA issue CRUD via the jira-as wrapper. Triggers: 'create bug/task/story', 'show me PROJ-123', 'get/view/look up issue', 'update PROJ-123', 'delete PROJ-123'. NOT for transitions (mk:jira-lifecycle); NOT for comments/attachments (mk:jira-collaborate); NOT for bulk ops (mk:jira-bulk); NOT for issue links (mk:jira-relationships); NOT for time logging (mk:jira-time); NOT for sprint/epic (mk:jira-agile).
mkjira-jsm
JIRA Service Management via the jira-as wrapper: service desks, request types, requests, customers, organizations, queues, SLAs, approvals (8 sub-domains). Triggers: 'create JSM request', 'list service desks', 'SLA status for KEY', 'approve request KEY', 'list queue NAME'. Requires JSM-licensed tenant + agent role. NOT for core Jira issue ops (mk:jira-issue); NOT for project admin (mk:jira-admin).
mkjira-ops
JIRA-side cache + project-context discovery via the jira-as wrapper. Triggers: 'jira cache status', 'clear jira cache', 'discover project context for PROJ'. Diagnostic-only — no Atlassian state changes. NOT for issue CRUD; NOT for project admin (mk:jira-admin).
babysit-pr
Watch a PR through CI and review feedback: commit/push, wait for CI, auto-fix high-confidence failures, reply to active review threads, address top-level Conversation-tab comments, and summarize automated review-body content with sentinel-tagged comments. Runs one pass against the current branch's PR; pass a PR number or URL to `gh pr checkout` that PR first. Use when the user says 'babysit my PR', 'babysit PR 482', 'watch my PR', 'keep my PR moving', or 'respond to comments'.
clipboard-testing
End-to-end testing playbook for Clipboard Health changes. Use when the user wants to verify, exercise, or set up test data for a backend or frontend change against a live environment — "test my change end-to-end", "verify this works in dev", "create a test workplace / worker / shift", "get a shift through to paid / invoiced", "prove the API change works". Defaults to the `development` AWS environment, API-first (cbh CLI tokens + curl). The skill knows enough to run the core happy-path flow (workplace → worker → shift → clock in/out → pay → invoice) autonomously; for anything else, it orients around the codebase and asks the user for missing directories.
seed-data
Trigger seed data generation for test environments via GitHub Actions. Use when asked to seed, create test data, or set up HCPs/facilities/shifts.
copilot-coding-agent
GitHub Copilot Coding Agent automation. Apply the ai-copilot label to an issue → GitHub Actions auto-assigns Copilot via GraphQL → Copilot creates a Draft PR. One-click issue-to-PR pipeline.
create-issue
Create an issue in GitHub or Jira. Automatically detects if GitHub issues are enabled; if so creates a GitHub issue, otherwise creates a Jira issue.
daily-meeting-update
Interactive daily standup/meeting update generator. Use when user says 'daily', 'standup', 'scrum update', 'status update', 'what did I do yesterday', 'prepare for meeting', 'morning update', or 'team sync'. Pulls activity from GitHub, Jira, and Claude Code session history. Conducts 4-question interview (yesterday, today, blockers, discussion topics) and generates formatted Markdown update.
jira-automation
Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
jira
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKET_ID]" or similar phrases.
jira
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.
backlog-grooming-assistant
Analyze backlog files (CSV or Markdown) to flag problematic items and generate a structured grooming agenda. No Jira API needed — works entirely with local exports. Use when preparing for sprint grooming, auditing accumulated tasks, or reviewing the backlog after a sprint. Triggers: 'groom my backlog', 'backlog grooming assistant', 'подготовь повестку груминга', 'груминг-ассистент', 'проверь бэклог на проблемы'.
sprint-review-summarizer
Transform sprint notes into a structured stakeholder doc: delivered, deferred, risks, next focus. No Jira needed. Use when preparing sprint review or stakeholder updates from free-form PM notes. Triggers: 'sprint review summary', 'summarize sprint results', 'итоги спринта', 'оформи итоги спринта'.
jira
Fetches and optimizes context from a JIRA issue for AI-assisted development. Searches assigned issues or fetches by key. Distills title, description, acceptance criteria, sprint context, and comments into a structured task description. Analyzes the codebase to surface missing criteria, scope, and risks. Optionally enriches the JIRA issue with a structured analysis comment, and for Complex-scope work can spawn implementation tickets in JIRA. Re-running on the same key refreshes the local task with the latest JIRA state instead of overwriting prior enrichment. Use before /optimus:tdd, /optimus:brainstorm, or /optimus:branch to pull task context from JIRA, or to refresh existing context after JIRA edits.
tdd
Guides test-driven development — decompose a feature or bug fix into behaviors, then cycle through Red (failing test) → Green (minimal implementation) → Refactor for each one. Requires /optimus:init and working test infrastructure. Use when starting a new feature or bug fix with test-first discipline.
atlassian-mcp
Integrates with Atlassian products to manage project tracking and documentation via MCP protocol. Use when querying Jira issues with JQL filters, creating and updating tickets with custom fields, searching or editing Confluence pages with CQL, managing sprints and backlogs, setting up MCP server authentication, syncing documentation, or debugging Atlassian API integrations.
adversarial-review
Perform an adversarial review of proposed work. Use ONLY when the user explicitly types /adversarial-review. Never auto-trigger, even if the user mentions reviewing, questioning, or challenging their approach.
cognito-user-analysis
Use when looking up Cognito user details by sub UUID, finding duplicate accounts sharing phone or email, analyzing which duplicates to keep vs delete, or fixing orphaned UNCONFIRMED signups. Symptoms include 403 Forbidden on login, multiple accounts for same phone, backend sync issues.
datadog-investigate
Investigate production issues by querying Datadog logs, metrics, and APM traces, then correlating findings with the codebase. Use this skill whenever the user mentions production errors, Datadog, observability, log investigation, latency spikes, error rate increases, 500s, trace IDs, monitor alerts, or wants to debug any service issue in a deployed environment.
flaky-test-debugger
Debug and fix flaky tests including Playwright E2E, NestJS service/integration, React component, and unit tests. Use this skill when investigating intermittent test failures, triaging flaky tests, or fixing test instability.
interview-feature
Use when clarifying requirements for a feature ticket. Iteratively researches and interviews the user until the problem is well-understood, then produces a structured problem brief. Dispatched by write-feature-ticket when context is insufficient.
investigate-ticket
Use when investigating a bug, incident, or issue before implementation. Researches codebase, queries Datadog, and presents structured findings with handoff options. Also use when asked to "look into" or "investigate" something.
write-bug-ticket
Use when creating a Linear bug report ticket from conversation context, investigation findings, or user-provided evidence. Focuses on structuring and writing — not investigating.
write-feature-ticket
Use when creating a Linear feature request ticket from conversation context, a brief description, or code/PR analysis. Interviews the user for clarity when context is insufficient.
write-tech-debt-ticket
Use when creating a Linear tech debt ticket while working in the codebase — from code review, PR comments, codebase audits, or post-incident findings. Expects deep technical context; classifies debt, assesses interest/risk with evidence, and justifies impact.
auto-pass
Canonical main-chain orchestrator for locked/current refinement-owned sources (DP-backed or JIRA Epic-backed). It routes a source through breakdown, engineering, and verify-AC without taking over their mutation authority. Trigger: "auto-pass {KEY}", "快速通關 {KEY}", "完整流程 {KEY}" when the source is LOCKED and artifacts are current. `{KEY}` 可以是 `DP-NNN` 或 JIRA Epic key。
breakdown
Universal planning skill: Bug reads ROOT_CAUSE then estimates; Story/Task/Epic explores codebase then splits into sub-tasks with estimates, and packs each sub-task into a self-contained task.md work order for engineering to consume. Also handles scope challenge (advisory mode). Trigger: 拆單, 'split tasks', 拆解, 'breakdown', 'break down', 子單, 'sub-tasks', 評估這張單, 'evaluate this ticket', 估點, 'estimate', 'scope challenge', '挑戰需求', 'challenge scope', '需求質疑'.
bug-triage
Bug diagnostic skill: root cause analysis and RD confirmation for Bug tickets. Use when the user wants to triage, analyze, or diagnose a Bug ticket — before planning starts. Trigger: '修 bug', 'fix bug', '分析 bug', 'triage bug', 'bug 分析', '修這張 bug', 'help me fix', '幫我修正', '開始修正', '修正這張', 'fix this ticket' (when issue type is Bug), 'debug', '找 bug', '為什麼壞了', 'why is this failing', 'investigate', '查問題', '這個怎麼回事', 'root cause', '根因', '排查'. NOT for: PR review fixes (use engineering revision mode), already-diagnosed bugs with root cause confirmed (use breakdown → engineering). This skill handles DIAGNOSIS only — estimation, test plan, QA challenge, and design doc are delegated to breakdown.
engineering
Engineer-minded execution orchestrator: takes a planned JIRA ticket and implements it with strict quality discipline — TDD, lint, typecheck, test, behavioral verify, PR. Two modes: first-cut (new implementation) and revision (fix PR review comments by returning to the work order). Local-only workflows may register delivery extensions, but those extensions are not part of the portable skill contract. Supports batch mode via parallel sub-agents. Trigger: "做 PROJ-123", "work on", "engineering", "開始做", "接這張", "做這張", "修 PROJ-123", "fix review on PROJ-123", PR URL (from pr-pickup or direct), or user provides JIRA ticket key(s). NOT for planning: Bug → bug-triage first; Story/Task/Epic → breakdown first. Key distinction: "下一步" / "繼續" without ticket key → my-triage (zero-input router + resume scan).
intake-triage
批次收單排工：分析 PM 開出的一批 ticket，評估優先序，告訴 PM 哪些先做、哪些後做、哪些規格不足需補。 產出 JIRA label + comment + Slack 摘要。 觸發：「收單」、「排工」、「intake」、「這批單幫我看」、「PM 開了一堆單」、「幫我排優先」、 「intake-triage」、「triage these tickets」、「prioritize this batch」。 當使用者提供一批 ticket key 並要求排優先序時使用此 skill，不要與 /my-triage（個人每日盤點）混淆。
learning
Use when the user wants to learn from external resources (URLs, repos, articles), extract patterns from merged PRs, process a learning queue, configure the daily learning scanner, or backfill review lessons. Trigger: '學習', 'learn', '研究', 'deep dive', '學習 PR', '每日學習', 'daily learning', '設定學習', '批次學習', '掃歷史 PR', or when user shares a URL to analyze.
my-triage
個人工作盤點與 zero-input next router；列出 assigned Epics/Bugs/Tasks，整合 cross-session resume signals，協助決定下一步。
refinement
Iteratively enriches incomplete JIRA Epics into estimation-ready, technically-validated specs. Five modes: batch readiness scan, RD discovery (Phase 0), PM elaboration (Phase 1), technical approach (Phase 2), and multi-round iteration. Phase 1 goes beyond checklist filling — it explores the codebase, hardens AC, and produces a structured artifact for downstream skills. Trigger: "refinement", "grooming", "討論需求", "需求釐清", "補完 Epic", "這張單缺什麼", "brainstorm", "方案討論", "想重構", "tech debt", "batch refinement", "sprint prep", or Epic with sparse content needing enrichment.
sasd-review
Generates a SA/SD (System Analysis / System Design) document for a JIRA ticket — a structured implementation plan produced before coding begins. Use this skill whenever the user mentions SASD, SA/SD, 寫 SA, 出 SA/SD, SA 文件, SD 文件, 架構文件, implementation plan, 系統分析, 系統設計, 技術設計, 異動範圍, dev scope, design doc, technical design, or asks to analyze what changes are needed for a ticket, plan the implementation approach, or produce a technical design document — even if they don't explicitly say "SA/SD".
sprint-planning
Use when the user wants to conduct or prepare for a Sprint planning session — organizing ticket candidates, reviewing capacity, or preparing a release page. Trigger: 'sprint planning', 'sprint 規劃', '下個 sprint', '排 sprint', 'release page'.
standup
Use when the user wants to generate a daily standup report or end-of-day summary (YDY/TDT/BOS/口頭同步). Single entry point for all standup and end-of-day workflows. Trigger: 'standup', '站會', 'daily', '寫 standup', '下班', '收工', 'EOD', 'wrap up', '今天做了什麼'.
use-company
Sets the active company context or diagnoses company routing. Two modes: (1) Set — declare which company to work with, bypassing auto-detection. (2) Diagnose — show which company a JIRA ticket or project routes to. Trigger keywords: "use company", "switch company", "切換公司", "用這間", "/use-company", "set company", "公司切換", "我要做 X 公司的", "which company", "哪間公司", "/which-company".
verify-ac
QA agent: executes Epic AC (Acceptance Criteria) verification against an AC ticket or Epic. Runs all AC steps, classifies each as PASS/FAIL/MANUAL_REQUIRED/UNCERTAIN, and presents observed vs expected as pure facts (no root-cause judgement). On FAIL, surfaces human disposition gate (spec issue vs implementation drift); on PASS, it may transition the AC ticket to Done only after verification artifact/report is current and the shared verification contract resolves to PASS. Trigger: "驗 PROJ-123", "verify {TICKET}", "verify AC", "跑驗收", "AC 驗證". NOT for planning or implementation: implementation drift routes to bug-triage; spec issue routes back to refinement.
beads-workflow
Converting markdown plans into beads (tasks with dependencies) and polishing them until they're implementation-ready. The bridge between planning and agent swarm execution. Includes exact prompts used.
jira-safe
Implement SAFe methodology in Jira. Use when creating Epics, Features, Stories with proper hierarchy, acceptance criteria, and parent-child linking.
jira-workflow
Orchestrate Jira workflows end-to-end. Use when building stories with approvals, transitioning items through lifecycle states, or syncing task completion with Jira.
api-connector-builder
Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.
code-review
Code review a pull request or a set of related PRs created by someone else. Reads diffs, comments inline, and posts a consolidated review summary.
sendsprint
Autonomous sprint delivery. Reads a Jira / Azure DevOps / GitHub sprint, delegates each task's code edit to simplicio-cli, captures evidence, and opens a draft PR. Triggers on "rode o sendsprint", "executar sprint", "entregar sprint", "run sendsprint", "ship my sprint", "deliver my sprint", "ejecutar sprint".
requirements-gathering
Conducts structured requirements gathering through sequential questioning before any research, planning, or implementation begins. Extracts true intent, constraints, edge cases, unknowns, and acceptance criteria from the user through focused one-at-a-time questions. Use this skill whenever the user mentions a new feature, task, ticket, bug fix, or any work item that hasn't been fully scoped yet. Also use when the user says "let's start", "new task", "I need to build", "requirements", "scope this", or "grill me" — even if they jump straight to implementation, redirect to requirements first.
jira-best-practices
Advise on USING Jira well, not operating it: make the structural call — is this an epic, a story, a task, or a sub-task? — and diagnose why a Jira is a dread, then recommend the lean fix. Adapt to the organisation's OWN hierarchy names, conventions, and working language instead of imposing a methodology. Self-hosted-first: Jira Data Center 10.3/11.x (no Cloud AI; dual Epic Link + Parent Link). Built for an agent that ACTS on Jira through the jira-cli tool or the mcp-atlassian MCP server while advising the user; Jira web-UI and admin-schema guidance is secondary. Covers ALL project types — software AND non-software (operations, engineering, services, business).
jira-cli
Drive Atlassian Jira from the terminal with the `jira` CLI (jira-cli, v1.7.0) against ANY Jira — Cloud or on-premise/Data Center. Covers the full command surface (issue / epic / sprint / board / project / release), the non-interactive automation contract (`--no-input` + `--plain`/`--raw`/`--csv` for agent-safe, parseable output), JQL filtering, GitHub/Jira markdown → Atlassian Document Format (ADF) conversion, authentication for every backend (Cloud API token, on-prem basic, PAT/bearer, mTLS), and live-discovery of instance-specific values (project keys, issue types, statuses, priorities, link types, custom fields) instead of guessing them.
jira-confluence-mcp
Install, configure, secure, and troubleshoot the mcp-atlassian MCP server (sooperset/mcp-atlassian) that connects an agent to Jira/Confluence — including AIR-GAPPED setup (mirror the prebuilt image by digest; no PyPI/git mirror) and internal-CA / TLS handling (mount the CA vs JIRA_SSL_VERIFY=false). Self-hosted Data Center first: the #1 gotcha is DC uses JIRA_PERSONAL_TOKEN (a PAT), NOT the Cloud username+API-token pattern. Covers `claude mcp add`, the env-var catalog, hardening (READ_ONLY_MODE, TOOLSETS/ENABLED_TOOLS, project filters, the v0.22 default-toolset change), Cloud-vs-DC tool/format divergence, and 401/403/field/rate-limit/SSL fixes. NOT a catalogue of the 72 tools — those self-document at runtime; this is the setup/ops knowledge invisible at call time.
board-deck-builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Covers deck structure, narrative frameworks, bad news delivery, section-by-section guidance, and common mistakes. Use when preparing board meetings, investor updates, quarterly business reviews, fundraising narratives, or when user mentions board deck, investor update, board pack, board presentation, quarterly review, fundraising deck, or investor deck.
board-meeting
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions, critic analysis, synthesis, founder review, and decision extraction. Prevents groupthink through isolated contributions. Use when making major strategic decisions, resolving cross-functional disagreements, evaluating irreversible choices, or when user mentions board meeting, executive deliberation, strategic decision, multi-perspective, or structured deliberation.
ceo-advisor
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.
cfo-advisor
Financial leadership advisor for CFOs on financial planning, fundraising, investor reporting, unit economics, cash management, and financial operations. Use when building a financial model, preparing for fundraising due diligence, designing investor reporting packages, calculating unit economics, managing cash runway, or planning month-end close processes.
channel-economics
Channel economics: design and analyze the financial structure of go-to-market channels (direct sales, resellers, distributors, marketplaces, embedded partners, MSPs, integrators). Use when picking the right channel mix for a product, modeling partner margin / TCO, designing partner tiers with rebate structures, analyzing channel conflict, or building the financial model that justifies (or kills) a partnership. Pairs with our partnerships-architect (partnership type / strategy) and deal-desk (partner-deal mechanics) — this one is the spreadsheet behind those conversations.
chief-ai-officer-advisor
AI leadership advisor for Chief AI Officers on AI strategy, governance, risk management, investment planning, organizational design, and the AI/ML talent stack. Use when defining an AI strategy, building an AI governance program, evaluating build-vs-buy for AI capability, scoring AI maturity, drafting an AI risk register, or planning AI investment across the portfolio.
chief-customer-officer-advisor
Customer leadership advisor for Chief Customer Officers on customer experience strategy, retention and expansion, voice-of-customer programs, CX organizational design, and customer outcomes accountability. Use when defining a CX strategy, scoring CX maturity, planning churn interventions, designing a VoC program, or preparing the customer section of a board update.
chief-data-officer-advisor
Data leadership advisor for Chief Data Officers on data strategy, governance, quality, monetization, platform decisions, and team design. Use when defining a data strategy, scoring data maturity, auditing a data governance program, evaluating a data platform stack, designing the data org, or preparing the data section of a board update.
chief-of-staff
C-suite orchestration layer that routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, tracks decisions, and manages cross-functional alignment. Every C-suite interaction starts here. Use when coordinating executive decisions, routing strategic questions, managing board meetings, synthesizing multi-perspective advice, tracking decision history, resolving inter-department conflicts, or when user mentions chief of staff, orchestrator, c-suite coordinator, executive routing, board coordination, decision synthesis, advisor routing, multi-agent coordination, or strategic orchestration.
chro-advisor
People leadership for scaling companies. Covers hiring strategy, compensation design, org structure, performance management, retention, culture health, and workforce planning. Use when building hiring plans, designing comp frameworks, restructuring teams, managing performance, building career ladders, handling attrition, workforce planning, or when user mentions CHRO, HR, people strategy, talent acquisition, headcount, compensation, org design, retention, performance management, employee engagement, or people operations.
churn-prevention
SaaS churn reduction covering cancel flow design, dynamic save offers, exit survey architecture, dunning sequences, payment recovery, win-back campaigns, and churn impact modeling.
ciso-advisor
Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap sequencing (SOC 2, ISO 27001, HIPAA, GDPR), security architecture strategy, incident response leadership, vendor security assessment, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, preparing for audits, or when user mentions CISO, security strategy, compliance, zero trust, board security, risk assessment, incident response, SOC 2, ISO 27001, HIPAA, GDPR, penetration testing, or vulnerability management.
cmo-advisor
Marketing leadership advisor for CMOs on brand strategy, demand generation, marketing operations, growth marketing, and revenue marketing alignment. Use when building a marketing strategy, planning demand-gen campaigns, designing lead scoring models, allocating marketing budget, or aligning marketing with revenue targets.
commercial-policy
Commercial policy: the written governance framework that defines what commercial terms sales can offer, what triggers approval, and what's off-limits. Use when authoring or refreshing a company commercial-policy charter, defining discount / contract / payment / termination / liability policies, auditing existing deals for policy compliance, drafting commercial-policy training for sales, or generating a tailored policy for a new region or vertical. Sits above deal-desk (which enforces) and pricing-strategy (which sets prices) — this is the policy layer that reflects how the company decides to do business.
company-os
The meta-framework for how a company runs -- the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse design, issue resolution (IDS), 90-day rocks, and communication cadence. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, quarterly planning, or meeting cadence.
competitive-intel
Systematic competitor tracking that feeds CMO positioning, CRO battlecards, and CPO roadmap decisions. Covers competitor identification, 8-dimension tracking, analysis frameworks, battlecard creation, win/loss analysis, and intelligence distribution. Use when analyzing competitors, building battlecards, tracking market moves, conducting win/loss analysis, updating positioning, or when user mentions competitive intelligence, competitor analysis, battlecards, win/loss, market positioning, or competitive strategy.
competitive-teardown
Systematic competitor analysis covering product teardowns, 12-dimension scoring rubric, feature comparison matrices, SWOT analysis, pricing model deconstruction, UX audits, and strategic action plans with stakeholder presentation templates.
competitor-alternatives
Competitor comparison and alternative page creation for SEO and sales enablement. Covers 4 page formats (singular alternative, plural alternatives, vs pages, competitor vs competitor), content architecture, research methodology, and centralized competitor data management.
coo-advisor
Operations leadership advisor for COOs on business operations, process optimization, scaling infrastructure, cross-functional alignment, and operational excellence. Use when designing operational processes, planning headcount capacity, optimizing vendor relationships, building business continuity plans, or scaling operations for rapid growth.
cpo-advisor
Strategic product leadership for scaling companies. Covers product vision, portfolio strategy, product-market fit measurement, product org design, north star metrics, investment postures, and board-level product reporting. Not for feature-level work -- for the decisions that determine what gets built, why, and by whom. Use when setting product vision, managing a product portfolio, measuring PMF, designing product teams, prioritizing at portfolio level, or when user mentions CPO, product strategy, PMF, product organization, portfolio prioritization, roadmap strategy, north star metric, or product-led growth.
cro-advisor
Revenue leadership for B2B SaaS companies. Covers revenue forecasting, sales model design, pricing strategy, net revenue retention, sales team scaling, pipeline management, and board-level revenue reporting. Use when designing the revenue engine, setting quotas, modeling NRR, evaluating pricing, building forecasts, scaling sales teams, or when user mentions CRO, revenue strategy, sales model, ARR growth, NRR, expansion revenue, churn, pricing strategy, sales capacity, pipeline, quota, or MEDDPICC.
cs-onboard
Structured C-suite onboarding through a founder interview that captures company context across 7 dimensions. Generates a persistent company context file used by all C-level advisory skills. Includes quarterly refresh protocol, context quality scoring, and graceful handling of missing information. Use when setting up advisory context for the first time, refreshing stale company context, or onboarding a new executive.
cto-advisor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.
culture-architect
Build, measure, and evolve company culture as operational behavior -- not wall posters. Covers mission/vision/values workshops, values-to-behaviors translation, culture code creation, culture health assessment, cultural rituals by stage, and culture debt management. Use when building company values, assessing culture health, designing rituals, creating culture codes, handling culture clashes, managing through rapid growth, M&A integration, or when user mentions culture, values, culture debt, founder culture, culture code, psychological safety, engagement, eNPS, or remote culture.
customer-success-manager
Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
deal-desk
Deal desk: the cross-functional function that reviews, approves, and structures non-standard sales deals. Use when standing up a deal-desk function from scratch, defining the deal-desk charter and SLA, building approval-threshold matrices (discount %, contract length, custom terms, payment terms, custom SLAs), designing a deal-review packet template, routing deals through the right approvers, analyzing deal velocity to find bottlenecks, or auditing recent deals for policy compliance. Pairs with our existing pricing-strategy (sets the prices) and revenue-operations (measures the funnel) skills — this one runs the operational machinery between those two.
decision-logger
Two-layer memory architecture for tracking executive decisions. Layer 1 stores raw deliberation transcripts, Layer 2 stores founder-approved decisions only. Future sessions read Layer 2 to prevent hallucinated consensus from past debates. Handles conflict detection, supersession tracking, DO_NOT_RESURFACE enforcement, overdue action item alerts, and decision search. Use when logging decisions, reviewing past decisions, checking overdue items, detecting conflicting decisions, or when user mentions decision log, decision history, past decisions, action items, decision tracking, or decision review.
executive-mentor
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for board meetings, dissects decisions with no good options, forces honest post-mortems, and identifies blind spots before competitors or board members do. Use when you need plan validation, board preparation, hard decision frameworks, assumption stress-testing, failure analysis, or when user mentions stress test, challenge, board prep, hard decision, pre-mortem, post-mortem, devil's advocate, plan review, or executive coaching.
form-cro
Form optimization for lead capture, contact, demo request, application, and checkout forms. Covers field-cost analysis, multi-step form design, validation UX, mobile optimization, and A/B testing frameworks.
founder-coach
Personal leadership development for founders and first-time CEOs. Covers founder archetype identification, delegation frameworks, energy management, CEO calendar audits, leadership style evolution, blind spot identification, imposter syndrome, founder mental health, succession planning, and the founder mode trap. Use when a founder feels like the bottleneck, struggles to delegate, is burning out, transitioning from IC to executive, managing a board for the first time, or when user mentions founder mode, CEO growth, leadership development, delegation, burnout, imposter syndrome, founder bottleneck, or executive transition.
free-tool-strategy
Free tool marketing strategy covering idea evaluation, tool design, lead capture architecture, SEO landing pages, launch playbook, and ROI measurement for calculators, generators, checkers, graders, and interactive tools.
general-counsel-advisor
Legal leadership advisor for General Counsels and senior legal leaders on legal strategy, risk management, contract and commercial governance, regulatory tracking, litigation management, and legal-team operating model. Use when defining a legal strategy, scoring legal risk, auditing the contract portfolio, building a regulatory calendar, or preparing the legal section of a board update.
internal-narrative
Build and maintain one coherent company story across all stakeholder audiences -- employees, investors, customers, candidates, and partners. Covers narrative construction, audience translation, contradiction detection, all-hands design, investor updates, crisis communication, and change management communications. Use when preparing all-hands meetings, investor updates, board presentations, recruiting narratives, crisis communications, or any time narrative consistency matters.
intl-expansion
International market expansion strategy for scaling companies. Covers market selection scoring, entry mode evaluation, localization requirements, regulatory compliance by region, go-to-market adaptation, team structure decisions, and launch planning. Use when expanding to new countries, evaluating international markets, planning localization, building regional teams, assessing regulatory requirements, or when user mentions international expansion, market entry, localization, regional strategy, global expansion, cross-border, or new market.
ma-playbook
M&A strategy for acquiring companies or being acquired. Covers strategic rationale assessment, target screening, due diligence frameworks, valuation methodologies, deal structure, negotiation strategy, integration planning, and post-acquisition execution. Use when evaluating acquisitions, preparing to be acquired, conducting due diligence, planning integration, negotiating deal terms, or when user mentions M&A, acquisition, merger, acqui-hire, due diligence, valuation, LOI, earnout, integration, or deal structure.
ml-ops-engineer
Expert MLOps engineering covering model deployment, ML pipelines, model monitoring, feature stores, and infrastructure automation. Use when deploying models to production, building training pipelines, setting up drift detection, configuring feature stores, or automating ML CI/CD workflows.
onboarding-cro
Post-signup user onboarding optimization covering activation metrics, time-to-value reduction, onboarding flow design, empty state optimization, multi-channel coordination, and stalled user recovery.
org-health-diagnostic
Cross-functional organizational health check combining signals from all C-suite roles. Scores 8 dimensions on a traffic-light scale with drill-down recommendations and cascade analysis. Use when assessing overall company health, preparing for board reviews, identifying at-risk functions, diagnosing cross-functional problems, or when user mentions org health, health check, health dashboard, company health, functional health, or health assessment.
page-cro
Landing page and marketing page conversion rate optimization covering value proposition clarity, headline effectiveness, CTA hierarchy, visual flow, social proof placement, objection handling, and structured A/B testing.
partnerships-architect
Design strategic partnerships — technology / channel / strategic / co-marketing — and the programs that scale them. Use when evaluating a potential partner, picking the right partnership type (tech integration vs reseller vs OEM vs strategic alliance), designing a partner program from scratch, structuring a specific partnership deal, modeling ROI on a partnership investment, or auditing an existing partner portfolio for ROI / strategic fit. Pairs with our channel-economics (financial mechanics) and deal-desk (per-deal approval) — this skill is the strategy layer above both.
paywall-upgrade-cro
In-app paywall and upgrade screen optimization covering feature gate design, usage limit UX, trial expiration flows, upgrade trigger timing, save offer strategy, and ethical monetization patterns.
popup-cro
Popup and modal optimization for conversion. Covers exit-intent, slide-ins, banners, timing optimization, frequency capping, audience targeting, compliance, and A/B testing frameworks for lead capture, promotions, and announcements.
pricing-strategy
SaaS pricing design and optimization covering value metric selection, tier architecture, price point research, pricing page design, price increase execution, and competitive pricing analysis.
referral-program
Referral and affiliate program design covering referral loop architecture, incentive design, trigger moment optimization, viral coefficient modeling, affiliate program structure, and optimization playbook.
revenue-operations
Analyzes pipeline coverage, tracks forecast accuracy with MAPE, and calculates GTM efficiency metrics for SaaS revenue optimization
sales-engineer
Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and plans proof-of-concept engagements for pre-sales engineering
scenario-war-room
Cross-functional what-if modeling for compound adversity scenarios. Models cascading multi-variable risks across all business functions simultaneously. Unlike single-assumption stress tests, this shows how one problem creates the next. Use when facing complex risk scenarios, strategic decisions with major downside, multi-variable threats, or when someone asks "what if X AND Y both happen?
signup-flow-cro
Signup and registration flow optimization covering SSO strategy, progressive profiling, field reduction, multi-step flow design, authentication UX, post-submit experience, and mobile registration patterns.
strategic-alignment
Cascades strategy from boardroom to individual contributor and detects misalignment. Covers strategy articulation testing, cascade mapping, orphan goal detection, conflicting goal identification, silo diagnosis, communication gap analysis, and realignment protocols. Use when teams are pulling in different directions, OKRs don't connect, departments optimize locally at company expense, strategy doesn't translate to execution, or when user mentions alignment, strategy cascade, silo, conflicting OKRs, strategy communication, goal cascade, or misalignment.
local-package
Use Clipboard's internal CLI to link and unlink @clipboard-health packages across repositories for local development. Use when testing local package changes, linking @clipboard-health packages between repos, or using the cbh CLI local-package command.
onboard
Setup wizard for a freshly-installed claude-flightdeck. Walks 8 stages — topology detection, codebase scan, team interview, git-history mining, document drafting, A-rule ratification, state capture, first-feature handoff — to bring Claude Code from 'template installed' to 'fully understands this project'. Use right after `install.sh` ('how do I get started', 'set up the workflow', 'onboard the project', '/onboard'). Subcommands: /onboard refresh (re-run on existing install), /onboard scan (Stage 1 only), /onboard rules (Stages 3+5), /onboard retro (post-first-sprint reflection).
team-collaboration-standup-notes
You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.
git-commit-helper
Intelligent commit message generator that enforces Conventional Commits and links changes to Jira issues for traceability.
jira
Manage Jira issues, sprints, and epics using the Jira CLI. Handles context retention and Markdown-to-JiraWiki formatting.
zk-merge
Summarizes current session consolidating memories, tasks, and key findings into a Zettelkasten note.
atlassian-mcp
Use when querying Jira issues, searching Confluence pages, creating tickets, updating documentation, or integrating Atlassian tools via MCP protocol.
jira-context
Resolves the Jira issue key for a git branch and pulls the ticket's essence — summary, acceptance criteria, and (for bugs) reproduction steps — as a structured context block for QA. Works without the Atlassian MCP via a manual-paste fallback. Use when you need the requirement/AC context behind a change, standalone or as part of a QA cycle.
commit-push-pr
Commit, push, and open a PR. Use when the user wants to ship changes, create a pull request, or says things like 'commit and push', 'open a PR', 'ship it', 'send it', 'create a PR for this', or 'push this up'.
visual-regression
Transitional standalone visual regression guard using before/after screenshot comparison. Two modes: SIT (compare staging vs local dev) or Local (compare git-stashed base vs current changes). No long-lived baselines — captures fresh screenshots each run and deletes after comparison. Config-driven from workspace-config.yaml. Use when: "跑 visual regression", "檢查畫面", "頁面有沒有壞", "visual test", "screenshot test", "畫面測試", "截圖比對", "有沒有跑版", "畫面壞了嗎", "UI 有沒有問題", "check if pages look right", for standalone manual investigation. Engineering / verify-AC Layer C uses scripts/run-visual-snapshot.sh instead.
fizzy-product-manager
Product management knowledge for Fizzy Kanban boards — Kanban principles, API workflows, triage, hygiene, and reporting
autopilot
Use to run the board autonomously — let the AI advance through SEVERAL ready cards on its own, each as an independent PR off main, guided by the blocker graph, without stacked PRs. Trigger when the user says "run the board", "execute the board", "advance on your own", "knock out the ready tasks", "autopilot", or asks the AI to work multiple cards in one go. It maps the dependency graph, settles every ready card's open decisions with the user UP FRONT (so execution never guesses), asks sequential-vs-parallel, then runs each ready card through the `implement` lifecycle + `review` gate on its own branch, opens a PR, and STOPS when only PR-dependent or blocked work remains — never merging to main itself. To execute ONE specific card interactively, use `implement`; to plan a new demand, use `plan`.
plan
Use to turn a NEW fuzzy demand — a feature, a change, a fix — into structured work in claude-organizer (sprints, histories/stories, tasks). Trigger whenever the user describes something new to build (a feature, a change, a fix) before it's broken down, asks to plan/organize the work, or asks to CREATE A CARD (or several) — card creation always runs through this skill, never a direct create_card call. Even a single obvious card goes through here. Understands the demand, organizes it, gets the design approved, then creates the cards. This is PLANNING, not execution — do NOT write code here.
management-talk
Reshape engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers) and shape it for the channel — JIRA comment, Slack post, async standup, email, or meeting talking-points. Use AFTER `/post-mortem` or any engineering writeup when the same information needs to flow up-the-org. Strips function/file/SHA identifiers but keeps JIRA keys, PR numbers, product names, and customer/workload identifiers. Maps to H4 (Win-Win — leadership gets the right facts, not a code dump) + H6 (Synergize — engineer + leadership channels reinforce).
nexus
Use for persistent TODO capture, daily brief retrieval, and shared Codex/Claude operating rules. Trigger on remember/track/follow-up requests, "nexus add/show/brief", or policy/workflow questions across Slack, Outlook, and Jira contexts. When in doubt, use this skill.
review-spec
This skill should be used for SPEC.md artifact reviewer — validates spec quality against the SB spec template: required sections, non-empty overview, user story format, testable acceptance criteria, assumption completeness, and frontmatter fields
jirac
Jira issue management skill for OpenClaw using the jirac CLI. Requires the `jirac` binary to be installed and authenticated before use. Use when listing, viewing, creating, updating, transitioning, commenting on, attaching files to, bulk-editing, cloning, deleting, linking, archiving, moving, changing types of Jira issues, logging work, generating standup or sprint summaries, managing sprint lifecycles, browsing fix versions, scanning Jira mention notifications, rendering markdown to ADF, registering jirac-mcp into MCP clients, or running raw Jira REST calls from agent workflows.
adk-implement
Implement, build, add, write, ship, code-up, wire-up code in an existing repo. Triggers on: Jira URL or KEY-NUM (specialized from-jira sub-flow — the most common path), GitHub issue URL or #N (from-issue), Confluence TDD URL (from-tdd), Slack thread permalink (from-slack-thread), or a freeform description (greenfield). Git mandatory; GitHub MCP optional but enables PR-by-URL flow. Every run: question-first (3 questions max), advisor-strategy plan with 2–4 trade-off options, edit-format discipline (SEARCH/REPLACE blocks per shared/edit-format.md), repo-native typecheck+lint+narrow-tests on each checkpoint. Writes plan/steps/diffs/report under `<repo>/.temp/adk/implement/<task>/`. Pushes only after explicit confirmation; never force-pushes; never merges; never touches a protected branch. Pulls Jira context via adk-mcp-atlassian, GitHub context via adk-mcp-github, and optional RAG via adk-mcp-rag. Supports --plan (read-only planning) → --act (writes). Sub-flows under references/.
adk-sync
Publish, sync, push-to, post-to, update, fetch-as-markdown, pull-from-Confluence/Jira/Slack. Bidirectional 3P bridge for markdown. Hybrid path: writes to `<repo>/.temp/adk/sync/<task>/synced/` when invoked from a repo with a repo-coupled doc, else `$ADK_DATA_HOME/sync/<task>/synced/` (default). READ mode (--read <url>): pulls a Confluence page / Jira description / GDoc / GitHub PR body / GitHub issue / Slack thread into local markdown. WRITE mode (--write <md-path> --to <destination>): publishes markdown to confluence / jira-desc / jira-comment / gh-pr-body / gh-issue-comment / slack / gdoc. Idempotent: match-by-id first, match-by-title-and-parent second, never by content hash. Format conversions are programmatic (md ↔ Confluence storage XHTML, md ↔ Jira ADF, md ↔ Slack blocks); AI only for "is this update safe?" checks. Per-invocation user confirmation required for every write regardless of mode (constitution §I.4). NEVER overwrites a human-authored target without explicit opt-in. NEVER changes sharing/restr
jira
Manage Jira issues via CLI. View, create, update, transition, assign, comment, sprint ops. Use when user mentions issue keys (PROJ-123), tickets, sprints, or keywords like jira/ticket/backlog.
helix
Helix QA assistant menu — route to TC FE prep, TC API prep, retest bug, testing ticket, or create bug. Use when the user says Helix, /helix, QA assistant menu, or is unsure which QA workflow to run. Do NOT use when the user already chose a specific workflow — use the matching command (/tc-fe-prep, /tc-api-prep, /retest-bug, /testing-ticket, /create-bug) directly.
jira-driven-planning
Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
chameleon-pr-review
Use when the user explicitly invokes /chameleon-pr-review to review a PR or branch diff against the repo's chameleon conventions, principles, and task requirements. Reports convention violations + logic gaps.
amendment-record
Author or update amendment records in openEHR specification documents — the `master00-amendment_record.adoc` table in `specifications-XX` repos. This skill should be used when the user asks to add or update an amendment entry, add a CR/PR reference, mark a release boundary, or update the `latest_issue`/`latest_issue_date` anchors. Not for general spec authoring (use authoring), the release process (use governance), or non-openEHR documents.
authoring
Create or edit openEHR specification documents — the AsciiDoc sources, `manifest.json`, and boilerplate includes in `specifications-XX` repos. This skill should be used when the user asks to create a new spec, add or edit a chapter/section, set up `master.adoc`, edit a spec `manifest.json`, or work on `.adoc` files in a `specifications-XX` repo. Not for: archetype/template/AQL work (openehr-assistant plugin), amendment records (use amendment-record), prose style (use content-patterns), ITS-REST OpenAPI (use its-rest), or BMM class tables/diagrams (use class-generation).
governance
Manage the openEHR specification governance lifecycle — releases, change requests (CR/PR), and lifecycle states (DEVELOPMENT/TRIAL/STABLE…). This skill should be used when the user asks to create or tag a release, prepare a release branch, update the manifest for a release, submit or manage a CR/PR, promote a spec's status, or discuss the openEHR change process or Jira workflow. Not for clinical/archetype governance, amendment-record authoring (use amendment-record), or non-openEHR release management.
go
Implement a plan file or direct request end-to-end, then hand off to commit-push-pr to ship it. Use when the user says 'go', 'execute the plan', 'implement the plan', or gives an implementation request.
plugin-recommender
Given a task description, searches internal and external open-source ecosystems to find and recommend suitable plugins with installation guidance. Activates on "recommend a plugin", "what tool should I use?", "is there a plugin for this?", "recommend a tool". Also checks for duplicate installations.
plugin-recommender
Given a task description, searches internal and external open-source ecosystems (including Codex marketplace and Claude Code marketplace) to find and recommend suitable plugins with installation guidance. Recommendation is quality-validation based (marketplace-listed + performance-validated), not source-origin based. Activates on "recommend a plugin", "what tool should I use?", "is there a plugin for this?", "recommend a tool". Also checks for duplicate installations.
api-checklist
Generate an API-level QA checklist in CSV format for manual GraphQL API testing (Postman / GraphQL Playground). Reads the project GraphQL schema from .claude/context/schema.graphql. Use when you need to verify backend/API behavior for a feature separately from UI checks.
bug-report
Convert a short bug description, screenshot, or video into a standard Jira bug report. Use when you need to quickly format a bug to team standards. Accepts text, screenshots, or video.
checklist-csv
Generate a QA test case checklist in CSV format for import into TestRail/Zephyr. Use when you need to quickly create a checklist from a spec, acceptance criteria, task description, or screenshots.
agency-deliverable-handoff
Package a finished deliverable for client handoff — produces the handoff message, the QA checklist that proves it's done, the asset link manifest, and the next-action ask. Use whenever the user says "ship this", "hand this over", "send to client", "deliverable is ready", or pastes a list of done items + asset URLs and asks for the handoff message. Do NOT use this skill for weekly status updates (use agency-weekly-report instead) or for internal team handoffs between two agency staff.
agency-weekly-report
Generate a polished, client-ready weekly status report for a marketing, content, or creator agency client. Use whenever the user asks to "build the weekly report", "write the Friday update", "summarize the week for [client name]", or pastes raw work logs / Linear / Notion exports and asks for a client-facing summary. Do NOT use this skill for internal team retros or for individual employee performance reviews — it is specifically scoped to outbound client communication.
silveringest
This skill should be used for external artifact ingestion: JIRA/Figma/Google Docs to SPEC.md + DESIGN.md via MCP connectors, plus cross-repo spec fetch with version pinning
atlassian-browser-macos
Use to read or write Jira / Confluence (create / update / delete / comment / transition issues and pages, run JQL/CQL) on macOS when the Atlassian MCP and API tokens are blocked or unavailable. Drives the user's already-logged-in Safari OR Google Chrome tab via osascript and calls Atlassian's own REST API from inside the authenticated browser session — no API token, no MCP.
atlassian-browser-windows
Use to read or write Jira / Confluence (create / update / delete / comment / transition issues and pages, run JQL/CQL) on Windows when the Atlassian MCP and API tokens are blocked or unavailable. Attaches to a Chrome tab via the DevTools remote-debugging port and calls Atlassian's own REST API from inside the authenticated browser session — no API token, no MCP. Zero-install path uses built-in PowerShell.
sync-all-repos
Sync all GitHub-backed git repos on this machine with origin. Pulls behind repos, pushes ahead repos, reports dirty/non-main/conflict cases for Claude to resolve.
capturing-session-learnings
Capture session learnings into AGENTS.md or CLAUDE.md. Triggers on /revise-agents-md and /revise-claude-md.
databricks-core
Databricks CLI operations: auth, profiles, data exploration, and bundles. Contains up-to-date guidelines for Databricks-related CLI tasks.
improving-instructions
Audit and improve AGENTS.md and CLAUDE.md files across project and user scopes.
document
Draft a technical document from an intent or a source. Triggers on "write the runbook / ADR / RCA / PR description / commit message / changelog / diagram / README / migration guide / API reference / experiment report / incident summary / onboarding doc / design doc". Markdown-first: produces a draft in a local file and NEVER publishes (no Confluence / Jira / Slack / GitHub posting — that is a separate concern). Reader-first voice: leads with the reader's question, cites every non-trivial claim to a repo path or quoted source, caps external quotes at 15 words, cuts filler. Audience-tuned (engineer / pm / exec / mixed) — the voice does not mix. GitHub context (PR / issue) is read via the gh CLI.
implement
Implement, build, ship, or wire up a change in an existing repo. Polymorphic on input: a Jira URL/KEY-123, a GitHub issue URL or #N (fetched via the gh CLI), a Confluence/Slack link (fetched via MCP), or freeform "build the X" prose. Plans before it acts: gathers context, presents 2-4 approaches with trade-offs, confirms, then writes the smallest correct change matching repo conventions, with tests for new behavior. Validates with the repo's own typecheck/lint/narrow tests at every checkpoint. Git via git directly (feature branch, never protected, never force, never merge); GitHub via the gh CLI only (PRs via gh pr create); clones SSH-only.
backend-spec
Generates backend or frontend engineering specs in structured Jira format with description, categorized acceptance criteria, routes, dev notes, and table schemas.
simplify
Instructions for simplifying code.
api-connector-builder
Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.
create-jira-issues
ユーザーストーリーマップやタスク分解プランからJiraチケットを一括作成する場合に使用。ストーリーマップ完成後のチケット化、プランファイルからの一括作成、計画済みストーリー・タスクのJiraへの移行が必要な場合にトリガーされる。
map-user-stories
設計書・プロジェクト仕様・Jira epic等からユーザーストーリーマップを作成し、タスク分解・スプリント計画まで行う場合に使用。新しいプロジェクトフェーズの計画、設計書の分析、大きな機能の実装単位への分解が必要な場合にトリガーされる。
purge-private-vocab
Detects local-plan coinages, abbreviations, and number labels in reader-facing text and rewrites them so readers without the source plan can follow. Use after generating PR description, Jira ticket, design doc, RFC, or other reader-facing text from a local plan/spec file, when readers don't share the source plan.
set-jira-story-points
JiraキーとStory Pointsのマップデータを受け取り、Jiraチケットに一括でStory Pointsを設定する。「ストーリーポイント設定」「SP設定」「story points」などのキーワードでトリガーされる。
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows
sprint-review
Generate a professional sprint review report for stakeholders — PMs, leadership, and cross-functional teams. Use this skill whenever a user wants to write up a sprint, summarize what the team shipped, produce a sprint retrospective document, recap what was completed in an iteration, or create a sprint summary for leadership. Triggers include: "write my sprint review", "generate a sprint recap", "create a sprint report", "summarize what we shipped this sprint", "help me write up our sprint for stakeholders", or any mention of sprint outcomes, velocity reports, or iteration summaries — even if they don't use the word "skill" or "report". Also trigger when a user pastes a list of tickets/tasks and asks for a write-up or summary.
daily-driver
Daily personal assistant for morning planning, task prioritization, and end-of-day review. Integrates with Obsidian daily notes for continuity. Use when user says "start my day", "daily plan", "morning routine", "EOD review", "what should I focus on", or "wrap up my day".
data-analysis
Data analysis and reporting assistant for a Product & Engineering team. Processes GA4 analytics, builds metric reports, analyzes article CTR, data page sources, and ad revenue. Accesses GA4 via Zapier MCP, Looker via browser, and Jira for sprint data. Use when asked to "analyze data", "create a report", "review metrics", "process CSV", "trend analysis", "build a dashboard", "GA4", "Looker", "impressions", "page views", or "ad revenue".
jira-automation
Jira automation for Product & Engineering teams. Creates Epics, Design Stories ([Design] prefix), and Implementation Stories ([Implementation] prefix) from PRDs or natural language. Runs JQL queries, manages sprints, and handles bulk operations via Atlassian MCP. Use when asked to "create a ticket", "write Jira tickets", "break down this PRD", "JQL query", "bulk create", "sprint management", or any Jira workflow task.
daily-briefing
Daily orientation and chief-of-staff briefing. Pulls from Slack (saved items), Gmail (important/starred), Google Calendar (today's events), Jira CLI (configured projects), and Todoist CLI, validates every action item, synthesizes a prioritized briefing using three consequence-based tiers, then produces a decisive hour-by-hour day shape anchored to the user's energy and focus windows. Appends to the daily Zettelkasten note on confirmation. Use this skill whenever the user types /daily-briefing, says "orient me for the day", "morning briefing", "what's on my plate today", "daily standup prep", "chief of staff", or any variant of wanting a cross-source daily work summary.
akb-ingest
Ingest whatever you point at into an AKB vault — a local file, a web URL, a GitHub PR/release/commit, a Confluence page, or a Jira issue. Auto-detects the source type and dispatches to a specialized ingest subagent; the router fetches and writes nothing itself. One target per invocation; globs expand to a sequential loop of document ingests.
refine
Refine a raw requirement into a structured engineering specification with acceptance criteria, edge cases, and risks.
daf-active
Show information about the currently active conversation
daf-cli
Quick reference and safety guide for daf commands in Claude Code sessions
daf-git
GitHub/GitLab issue operations (update, link) with Markdown syntax reference and gh/glab CLI guide
daf-jira
JIRA operations (view, create, update, comment) with Wiki markup syntax reference
daf-jira-fields
JIRA field mapping rules, validation, and defaults for DevAIFlow
daf-jira-mcp
Using MCP JIRA tools with DevAIFlow validation logic and field intelligence
daf-workflow
DevAIFlow session context loader. Activates when DAF_SESSION_NAME env var is set. Reads session metadata, issue tracker tickets, and context files to understand the current task. Provides per-command workflow guidance for daf open, daf new, daf git new, daf jira new, and daf investigate.
release
Automate project release workflow with version management, CHANGELOG updates, and git operations
deploy-ship
Use when committing, pushing, creating PRs, or completing branches - conventional commits, PR creation, Jira updates, worktree cleanup
dev-brainstorm
Use when brainstorming new features, making architectural decisions, evaluating technical tradeoffs, or documenting decisions as ADRs - before any implementation planning or coding begins
dev-implement
Use when executing an implementation plan task-by-task - dispatches subagents for implementation, manages git worktrees, handles phased multi-service deployment
dev-plan
Use when creating implementation plans from specs or requirements - phased task breakdown with deployment readiness gates before any coding begins
pm-refine
Use when refining user stories, writing feature specifications, sizing work (T-shirt), creating subtasks, planning spikes, or generating QA test plans - covers the product management side of development before implementation begins
qa-test
Use for QA-perspective testing - Playwright automation or manual browser testing focused on user journeys, not implementation details
review-code
Use when requesting or receiving code review - dispatches reviewer subagent or processes human PR feedback with technical evaluation
review-design
Use when reviewing frontend implementation against design specs - design system compliance, responsive behavior, accessibility audit
agency-roster
List and discover available specialist agents from the agency-agents fork. Use when the user asks "what agents do I have", "which agent should I use for X", "list the available specialists", "show me the agent roster", or wants to browse capabilities across the 163-agent collection. Also use when uncertain which agent to delegate to and want to ground the choice in the actual installed roster.
daf-config
View current configuration (read-only)
test-kapsam-denetimi
Test senaryolarinin kullanim senaryolarini ne kadar karsiladigini madde madde denetler ve kapsam boslugu raporu uretir. Uc kaynak dokumandan (SRS gereksinim .xlsx, kullanim senaryolari .docx, test senaryolari .xlsx) yola cikip her kullanim senaryosunu ayri bir paralel ajan (Opus 4.8) ile denetler; ana akis adimlari, alternatif senaryolar, is kurallari, on/son kosullar ve SRS gereksinimlerini Tam/Kismi/Yok olarak eslestirir. Cikti olarak kapsam boslugu raporu (.md), izlenebilirlik matrisi (.xlsx), yorumlu test kopyasi (.xlsx) ve KS bazinda Jira yorumlari (.md) uretir; sonunda sert bir dogrulama (test kontrol) yapisi calistirir. Tetikleyiciler - "test kapsam denetimi", "kapsam boslugu", "coverage gap", "test kullanim senaryosu kapsam", "test senaryolari yeterli mi", "use case test coverage", "BVAKP test kapsam", "test eksik bul", "kapsam matrisi".
autopilot
Autopilot for autonomous feature shipping from brainstorm to PR using .workbench/autopilot.md.
brainstorming
Use before creative work to grill the user toward a shared design concept through exhaustive sequential question and answer.
calendar
View agendas, manage events, check availability, and update calendars with gws.
claude-codex-bridge
Align Claude Code and Codex project files, settings, hooks, agents, and plugins.
copilot
Use when the user wants semi-autonomous, human-in-the-loop feature shipping where the user drives the brainstorm and spec by hand and the agent (the copilot) automates the plan, implementation, docs, audit, and PR using .workbench/autopilot.md. The interactive sibling of workbench:autopilot.
crafting-design-systems
Use when the user wants to create or edit a workbench design system, a directory of CSS variable overrides, optional components, and optional images that themes HTML output from workbench producer skills.
crafting-html
Use when producing a standalone HTML artifact that is not already covered by another workbench skill (writing-spec, writing-plans, brainstorming, systematic-debugging) or by research:research. Covers PR walkthroughs, code explainers, slide decks, status and incident reports, design prototypes, SVG illustrations, custom editing interfaces, and similar single-file HTML outputs. Bundles 20 reference examples plus an index file (21 files total) for inspiration; read individual files lazily, not all at once.
crafting-presentations
Use when the user wants to build a multi-slide HTML presentation with slide-type templates, a deck-stage engine, and an optional two-window presenter view for live sharing in Teams, Zoom, or Meet. For one-off single-file slide artifacts, see workbench:crafting-html. For brand theming, see workbench:crafting-design-systems.
creating-skills
Use when scaffolding, iterating on, pressure-testing, optimizing the description of, or extracting from a session a Claude Code or Codex skill in any plugin marketplace. Detects the marketplace shape automatically (Claude Code, Codex, or both) and adapts to the repo's own conventions for paths, author, license, test layout, and version-tracking. Triggers on phrases like "create a skill", "scaffold a skill", "iterate on this skill", "pressure-test", "optimize the description", or "turn this conversation into a skill".
dispatching-parallel-agents
Use when facing two or more independent tasks that can be worked on concurrently without shared state or sequential dependencies.
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
exporting-decks-to-pptx
Use when the user wants to export or convert an existing workbench HTML deck into a native, editable PowerPoint file (.pptx) with real text boxes, autoshapes, embedded images, and speaker notes. Triggers on requests like "make a PowerPoint version of this deck" or "export the deck to pptx". For building a new HTML presentation, see workbench:crafting-presentations.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
gmail
Search, read, send, and manage Gmail messages, drafts, labels, and filters with gws.
jira
Search Jira, manage issues, add comments, transition work, and inspect sprints.
perfecting-presentations
Use when the user wants to review, audit, polish, or perfect an existing HTML slide deck until it is genuinely done, for example "review this deck until it is perfect", "make this presentation crisp", "audit my slides". Runs a strict convergence loop, deterministic hard gates plus fresh-context judge panels with adversarial verification, terminating only when consecutive review rounds come back dry. For building a deck see workbench:crafting-presentations; for designing slide content see writing:presentations.
playground
Creates interactive HTML playgrounds, self-contained single-file explorers that let users configure something visually through controls, see a live preview, and copy out a prompt. Use when the user asks to make a playground, explorer, or interactive tool for a topic.
presentations
Use when the user wants to design the content of a slide presentation, from audience brief through critiqued storyboard. Produces a markdown deck.md with structured per-slide front-matter. For a written prose talk instead of a deck, use writing:writing with format talk. For rendering a deck.md to HTML, use workbench:crafting-presentations.
pyramid
Structure memos, recommendations, briefings, and decision documents with the Pyramid Principle.
quizzing-a-topic
Use when the user wants to be taught and quizzed on a topic, theme, or concept they name (not the current session), to verify they deeply understand it. For example "teach me about Kafka consumer groups and test me" or "quiz me on this repo's auth flow".
quizzing-the-session
Use when the user wants to be taught and quizzed on the work from the current session, what was just built, decided, debugged, or changed, to verify they deeply understand it. Not for updating agent instruction files; that is capturing-session-learnings.
research
Research complex topics with sources, synthesis, review, and a final report.
subagent-driven-development
Use when executing an implementation plan with fresh subagents, task ownership, and review gates in the current session.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
tech-doc
Draft, review, and finish tutorials, how to guides, references, and explanations.
terse-mode
Use only when the user explicitly asks to switch the session into terse mode, terse-mode, less tokens mode, token saving mode, or /terse-mode.
test-driven-development
Use when implementing any feature, bugfix, refactor, or behavior change before writing implementation code. Enforces test-first RED-GREEN-REFACTOR discipline.
tmux
Use when the user wants to control interactive terminal programs through tmux, drive REPLs, debuggers, TUI tools, or experiment with steering nested Claude Code or Codex CLI sessions by sending keys and reading pane output.
using-workbench
Load Workbench skill rules and choose the right Workbench skill.
verification-before-completion
Use when about to claim work is complete, fixed, passing, ready, or safe to merge, especially before commits, pushes, PRs, or handoff summaries.
visualizing-options
Use when a design discussion needs visual options shown in a browser: mockups, layout comparisons, wireframes, or architecture diagrams that the user can click to choose between. Spawns a local server and renders content fragments.
writing
Draft, review, and finish long form prose, essays, talks, newsletters, memos, and briefings.
writing-plans
Use when a design spec or approved requirements need to become a concrete, step-by-step implementation plan before code changes.
writing-spec
Use when a design discussion is ready to be written into a spec document, before any implementation planning. Synthesizes the conversation into a spec, runs a fresh-eyes self-review subagent, and gates on user approval before handing off to writing-plans.
scriptrunner-behaviours
Use when a user asks to write, debug, refactor, or review a ScriptRunner Cloud behaviour in TypeScript, or mentions getFieldById, getContext, makeRequest, ONLOAD, ONCHANGE, extensions.yaml, field visibility, field validation, or template pre-filling on issue screens
scriptrunner-discovery
Use when a user needs to find Jira custom field IDs, test a JQL query, inspect an issue's data structure, discover project keys, look up workflow statuses, or find transition IDs, role IDs, issue type IDs, or link type IDs before writing ScriptRunner scripts
scriptrunner-groovy
Use when a user asks to write, debug, refactor, or review a ScriptRunner Cloud Groovy script, or mentions HAPI, Issues.getByKey, Issues.create, listeners, script fields, jobs, escalation services, workflow post functions, conditions, validators, ComponentAccessor, or addComment in a Cloud context
mcp-deduplicator
MCP tool deduplication and unified abstraction layer for multi-server setups. Activate when the user has multiple MCP servers installed and wants to reduce tool noise, detect overlapping tools, understand which tool to use for a given task, or create routing rules that prevent Claude from wasting tokens choosing between near-identical tools. Handles: semantic duplicate detection across MCP servers, unified tool abstraction mapping, routing rule generation, tool conflict resolution, canonical tool naming, and per-server tool audits. Use when user says: too many tools, duplicate tools, MCP overlap, tool overload, which tool should I use, GitHub vs GitLab tools, Jira vs Linear tools, deduplicate my tools, clean up my MCP, tool conflict, tool sprawl, consolidate tools, multiple MCP servers, tool redundancy. Do NOT activate for: installing MCP servers, configuring individual MCP servers, writing code that calls MCP tools, general MCP setup questions without a deduplication goal. First response: "MCP Deduplicator a
agentic-ops-orchestrator
Route a real-world operations task to the right skill among 16 agentic-ops specialists — email, messages, GitHub, Jira, Google Workspace, project flow, unified notifications, terminal/CI, knowledge base, customer + finance billing, automation audit, workspace-surface audit, social connections, and dashboards. USE WHEN an agent must operate, triage, or prove work on a live external surface (inbox, repo, tracker, billing, docs) but the user hasn't named the specific skill.
daf-info
Show detailed information about the current session
daf-list-conversations
List all conversations in the current multi-project session
daf-read-conversation
Read the conversation history from another repository in this multi-project session
daf-workspace
List configured workspaces for multi-branch development
confluence
Search, read, create, and update Confluence pages.
project-management-routing
Project management specialist routing for studio operations, cross-functional shepherding, experiment tracking, realistic scoping, and Jira workflow discipline. Use when the user asks about high-level portfolio orchestration, day-to-day studio efficiency, cross-team project coordination, A/B experiment management, converting specs to realistic tasks, or enforcing Jira-linked Git workflow and traceable commits. Triggers on portfolio management, multi-project, studio operations, project shepherding, cross-functional coordination, experiment tracking, A/B test management, hypothesis validation, realistic scoping, spec to tasks, Jira ticket, conventional commits, branch strategy.
plan-website
Creates a Work Breakdown Structure for planning and executing a website build from scratch or as a migration/overhaul. Organizes repository setup, planning artifacts, implementation slices, QA gates, and launch work into deliverables, work packages, and tasks, with phase checklists as supporting artifacts. Use when the user mentions building, launching, or overhauling a website: redesigns, CMS migrations, new site builds, or multi-team web projects. Triggers on phrases like "website build", "site launch", "web project checklist", "website redesign", "launching a site", "new website", or "website planning". Also use when the user wants to know what documents or deliverables a web project needs, or is coordinating design, dev, content, and SEO teams on a site.
ticket-context
Fetch ticket context from Jira (PROJ-123), Confluence, or GitHub (`#NNN`). Auto-loads on ticket references. Returns title, summary, acceptance criteria, links, and recent activity.
jira-datacenter
This skill should be used when the user asks to "get Jira issue", "create Jira ticket", "search Jira", "update issue status", or needs to interact with Jira Data Center/Server instances.
databricks-docs
Use when the user asks a Databricks product question (Apps, DABs, Jobs, Lakebase, Model Serving, Pipelines, Unity Catalog, SQL Warehouses, MLflow, serverless, secrets, workflows) that databricks-core's CLI cheatsheet does not answer. Resolves a canonical URL from references/docs-index.md and fetches it with the host agent's WebFetch tool.
devpilot-prd-to-issues
Use when the user wants to turn a PRD, spec, design doc, or feature brief into a set of GitHub issues — "break this PRD into tickets", "create issues from the spec", "split this into tasks", "file the work for this feature", "decompose into deliverables", "/prd-to-issues". Produces an issue tree where every ticket is a deliverable slice with explicit parent/child/blocks relationships and a bounded change size.
daf-help
Show available daf commands and quick reference
daf-list
List all DevAIFlow sessions
daf-notes
Add and view progress notes for sessions
daf-status
Show status and progress dashboard
sprint-lifecycle
Manage Jira sprint lifecycle with jirac — list, create, start, complete, update, or delete sprints for a project
daily-standup-prep
Generate a per-team standup markdown report by gathering activity over the last N days from Jira, GitLab, Confluence, and a local Git repo. Maps activity to team members from a roster CSV, renders a Mermaid kanban + randomized talking order, captures a `daily`-tagged sprint snapshot, and runs a clarity-council (infographics-expert burndown chart + statistics-expert forecast + scrum-master suggestions) for sprint pulse. Writes one file per team into the Obsidian vault. Use when the user says "daily standup prep", "standup report", "generate standup", "scrum prep", or invokes /daily-standup-prep.
good-morning
Morning kickoff wrapper that runs sprint-snapshot (daily tag), daily-standup-prep (with sprint burndown), and daily-briefing (report only — no focus-block suggestions) in order. Re-runs idempotently — existing same-day artifacts are overwritten in place. Use when user says "good morning", "morning routine", "kick off my day", "start my day", or invokes /good-morning.
issue-dup-find
Scan all open issues in a Jira project and identify likely duplicates using semantic comparison. Produces a markdown report listing each suspected duplicate pair with a probability score and reasoning. Read-only — never modifies, links, or transitions tickets. Default project key is read from memory (`reference_jira_default_project.md`); accepts an override project key. Use when user says "find duplicates", "duplicate check", "dedupe issues", "find duplicate tickets", or invokes /issue-dup-find with or without a project key.
issue-estimate-sp
Estimate story points for a Jira ticket using historical data and multi-persona scrum poker. Use when user says "estimate this ticket", "how many points", "story point estimate", "estimate [TICKET-KEY]", or invokes /issue-estimate-sp. Read-only — never modifies the ticket.
issue-suggest-component
Suggest Jira components for one ticket or sweep all open tickets in a project. Gathers context from Jira, Confluence, and GitLab, proposes a conservative set of existing components (or recommends new ones), and confirms with the user before any modification. Bulk mode default project key is read from memory (`reference_jira_default_project.md`); max 250 tickets, highest key first. Use when user says "suggest components", "tag components", "fix components", "categorize tickets", or invokes /issue-suggest-component with or without a ticket key.
issue-triage
Triage a bug or issue by gathering context (Jira ticket or free-form description), mapping the suspected code area via codebase-explain, hypothesizing root causes via clarity-council, and producing a structured triage report with ranked root-cause candidates and proposed solution paths. Read-only by default; the user may opt in at the end to publish the report as a Jira comment. Use when user says "triage this", "triage [TICKET-KEY]", "what's causing this bug", "help me find the root cause", or invokes /issue-triage with a ticket key or issue description.
sprint-plan
Convert the start-of-sprint canvas into a planning markdown report — sprint goal summary, committed scope, capacity vs commitment (split into carry-over from previous sprint vs new commit), key observations, and risks. Assumes all unclosed items from the previous sprint's end snapshot are carried into this sprint and surfaces them as a dedicated section with WIP-saturation risk. Reuses sprint-snapshot's `_sprint.md`, `_team-rules.md`, current `start.canvas`, and previous sprint's `end.canvas`. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner) for the observations/risks block. Output is date-stamped (`sprint-plan-YYYY-MM-DD.md`) — same-day re-runs silently refresh today's file, prior days are preserved as historical record; a `sprint-plan-latest.md` pointer always wikilinks the newest. Use when user says "sprint plan", "sprint planning report", "convert sprint plan to markdown", or invokes /sprint-plan.
sprint-snapshot
Capture a point-in-time snapshot of a scrum team's current sprint board from Jira and render it into the Obsidian vault as (1) an Obsidian Canvas with sprint overview, team workload, kanban columns, and issue cards, (2) a companion markdown summary, and (3) an append-only JSONL trend log. Auto-detects sprint phase (start / week 1 / week 2 / week 3 / end) from today's date. Supports `--as-of <date>` for historical snapshots. Reuses obsidian-canvas / obsidian-vault / obsidian-markdown for vault writes and follows the issue-* skills' Jira context-gathering patterns. Use when user says "sprint snapshot", "snapshot the sprint", "capture sprint state", "sprint planner", "scrum board snapshot", or invokes /sprint-snapshot.
sprint-sos-report
End-of-week scrum-of-scrums report comparing two sprint snapshots and surfacing key findings, observations, trouble areas, and trends. Auto-detects which two snapshots to compare (most-recent two by snapshot_at) with `--from`/`--to` overrides for re-planning churn comparisons (e.g. compare `week 1` vs a mid-week `week 1.5`). Applies team-specific overhead, wedge-balancing, and in-review overhead rules from `_team-rules.md`. Auto-runs a clarity-council session (statistics-expert + scrum-master + product-owner). Use when user says "scrum of scrums", "sos report", "weekly sprint report", "sprint progress report", or invokes /sprint-sos-report.
request-refactor-plan
Create a detailed refactor plan with tiny commits via user interview, then file it as a Jira ticket. Use when planning a refactor, creating a refactoring RFC, or breaking a refactor into safe incremental steps.
api
Execute a raw Jira REST API call through the jirac CLI, including GET, POST, PUT, DELETE, and PATCH requests to any Jira REST endpoint
archive
Archive Jira issues matching a JQL query with jirac
attach
Upload local files as Jira issue attachments through the jirac CLI
batch
Run mixed Jira operations (create, update, transition, archive) from a single JSON manifest file using jirac batch
bulk-comment
Add the same Markdown comment to multiple Jira issues with jirac, either by JQL query or explicit issue keys
bulk-create
Create multiple Jira issues at once from a JSON manifest file using jirac bulk-create
bulk-transition
Bulk transition multiple Jira issues with a JQL filter through the jirac CLI
bulk-update
Bulk update assignee or priority on multiple Jira issues matching a JQL query with jirac
change-type
Change a Jira issue to another issue type using Jira's native move semantics with jirac
clone-issue
Clone a Jira issue with jirac, optionally into another project or with a new summary and assignee
comment
Manage Jira issue comments with jirac, including listing existing comments and adding a new Markdown comment to an issue
create-issue
Create new Jira issues with jirac, including interactive prompts for project, issue type, summary, and custom fields
daily-standup
Generate a markdown-ready daily standup summary from assigned Jira issues using jirac
delete-issue
Permanently delete a Jira issue with jirac, with optional force flag to skip confirmation
fields
Inspect Jira field metadata with jirac for a project and issue type, especially before create or update flows that use custom fields or backlog-specific schemas
jql
Build or run Jira JQL queries with jirac, either directly from a query string or through the interactive JQL helper
link
Manage Jira issue links (blocks, relates, duplicates, etc.) with jirac — list link types, add a link, or delete an existing link
list-issues
List Jira issues with jirac by project, assignee, or custom JQL, including the default current-user flow
move-issue
Move a Jira issue to another project using Jira's native move semantics with jirac (not clone+delete)
notifications
Scan recent Jira @mention notifications from issue descriptions and comments using jirac
render
Render and validate Markdown content as Jira ADF with jirac before sending it to Jira as a description or comment
sprint-summary
Summarize the current or named Jira sprint by status and assignee using jirac
transition
Transition Jira issues to a new workflow state with jirac, either directly or through the interactive transition picker
update-issue
Update existing Jira issues with jirac, including summary, description, assignee, priority, labels, components, fix versions, and custom fields
versions
Browse Jira project fix versions, preview their backlog items, or update version metadata with jirac
worklog
Manage Jira worklogs with jirac, including list, add, and delete flows for issue time tracking
jira-spike
Create or refine Jira Spike tickets in Jira Markup. Use when the user wants a Spike, research ticket, investigation ticket, technical exploration, discovery work, research question, or SDD-ready Spike input.
jira-task
Create or refine Jira Task tickets in Jira Markup. Use when the user wants a Jira Task, technical task, implementation task, maintenance task, operational work item, developer-ready task, acceptance criteria for a task, or SDD-ready Task input.
jira-user-story
Create or refine Jira User Story tickets in Jira Markup. Use when the user wants a user story, story ticket, product capability, end-user outcome, acceptance criteria for a story, developer-ready story, or SDD-ready User Story input.
write-ac
Generate structured Jira acceptance criteria in Gherkin format (Given/When/Then). Use when the user wants to define, write, or create acceptance criteria for a Jira task, story, or ticket. Triggers include "acceptance criteria", "AC", "write the ACs", "define ACs for", or any request to document expected behavior as testable conditions. También se activa en castellano: "criterios de aceptación", "CA", "escribir los criterios", "definir criterios de aceptación", "crear los CA", "ACs del ticket", "criterios Gherkin", "dado cuando entonces", "condiciones de aceptación", "escribir los ACs", "generar criterios", "criterios para esta historia", "definir los criterios".
api-connector-builder
Build a new API connector or provider by matching the target repo's existing integration pattern exactly. Use when adding one more integration without inventing a second architecture.
issue-feature-breakdown
Analyze a Jira ticket by gathering full context from Jira and Confluence, following linked tickets, then running a clarity-council to identify gaps and ambiguities. Produces an actionable breakdown plan. All actions are read-only. Use when user says "break down this feature", "analyze this ticket", "feature breakdown", or provides a Jira ticket key for analysis.
meeting-notes
Transform meeting transcripts into structured action items, decisions, and key insights. Processes raw notes, voice memos, or recordings.
delivery-engine
Operational backbone for backlog health through release readiness. Modes: Backlog scan · Ticket insight · DoR gate · Sprint planning · Execution control · DoD gate · RAID updates. Use for sprint planning, backlog review, quality gates, or velocity tracking across Agile and Waterfall governance. Triggers: "run DoR on this", "run DoD on this", "check this backlog", "plan the sprint", "velocity check", "is this release ready", "update the RAID log."
file-router
Classifies, routes, and triggers processing for new files arriving in the PMO workspace. Uses three-layer classification (content analysis, project identification, filename patterns) with confidence thresholds. Triggers: "route this", "file this", "where does this go", "classify this", "I have a new transcript", "I just uploaded this", "what folder does this go in."
pmo-process-designer
Converts business context into structured, traceable requirements and process documentation. Modes: Requirements definition · Workflow documentation · Gap analysis · Traceability matrix · Compliance mapping. Use when uploading business requirements, FDDs, or Jira exports. Triggers: "document this process", "build the requirements", "build the traceability matrix", "write the FRD", "trace from requirement to Jira", "what's the gap."
view-issue
View full Jira issue details with jirac, including description, attachments, and other issue metadata
n8n-workflow-patterns
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, or scheduled tasks.
from-issue
Generate Playwright tests from a Jira ticket (read via the Atlassian MCP), composing /scaffold-page-object when a target Page Object doesn't yet exist, and open a GitHub PR with the generated tests for review.
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
refine-ticket
Iteratively harden a Jira automation ticket against a "bulletproof" rubric — grounded in existing automation, app docs, and user-supplied sources — then write the refined acceptance criteria back to the ticket on approval, so /from-issue has nothing left to guess.
spike
Generate well-structured Jira Spike tickets in Jira Markdown syntax. Use when the user wants to create a spike, investigation task, technical research task, or feasibility study for Jira. Triggers include requests like "create a spike", "write a Jira spike", "I need a spike for [topic]", or any request to document a technical investigation or research task as a Jira ticket. También se activa en castellano: "crear un spike", "escribir un spike", "spike de investigación", "tarea de investigación", "investigación técnica", "spike en Jira", "necesito un spike para", "estudio de viabilidad", "ticket de investigación", "spike técnico", "hacer un spike", "documentar investigación", "crear tarea de investigación".
atlassian-mcp
Use the Atlassian MCP Server to interact with JIRA from coding agents (Cursor, Claude Code). This skill documents how to use the official Atlassian MCP server for JIRA and Confluence operations. Enable this MCP server in your Cursor/Claude Code settings for JIRA access.
create-tickets
Create tickets via Linear/Jira MCP or generate formatted ticket text
scaffold-page-object
Generate a draft Page Object class from a live page snapshot, composing framework components when detected.
changelog-manager
Manages changelog entries following Keep a Changelog format with CalVer versioning. Analyzes changes and generates appropriate changelog descriptions.
init-specs
Initialize spec documents (requirements, specs, plans) for a new task. Creates scaffolded markdown files in specs/ directory. Use when user wants to start a new task specification.
spec-manager
Orchestrates specification management workflow by coordinating init-specs, specify-with-requirements, plan-with-specs, plan-with-requirements, update-requirements, and sync-to-jira skills. Manages the full lifecycle of task specifications from requirements through implementation planning and Jira push-back.
sync-to-jira
완성된 specs/plans 문서를 Jira 이슈로 push-back 합니다 (Markdown → ADF 자동 변환). Jira MCP가 가용한 환경에서만 동작합니다.
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows
package-upgrade
升級 Python / JavaScript / TypeScript / Go 套件或修復 CVE 漏洞的完整工作流。 當使用者提到「升級 package」、「更新套件」、「fix CVE」、「修復漏洞」、 「package migration」、「dependency update」、「bump version」、 「升級 npm package」、「update axios / react / lodash」、「bump <pkg>」、 「升級 go module」、「update go.mod」、「go get upgrade」、 「govulncheck」、「v1 升 v2」、「major version upgrade」 時觸發此 skill。也適用於使用者提供 CVE 編號 (如 CVE-2024-xxxxx) 並希望修復的場景，以及提供 Atlassian Jira ticket URL (如 https://trendmicro.atlassian.net/browse/V1E-148968) 或 Jira issue key (如 V1E-148968) — 此時會自動讀取 ticket 內容、 分析應升級的套件、完成後將報告 comment 回 ticket，並依目前 ticket 狀態提議推進 (To Do → Ready for Work → Development → Done)。 也適用於使用者提供 GitHub Dependabot 安全警示頁面 URL (如 https://github.com/<owner>/<repo>/security/dependabot) — 此時會抓取所有 open 警示、依語言/manifest 分組、產出一份批次升級計畫 供使用者核可後，逐項驅動既有升級流程 (batch mode)。 Python: 支援 pip、poetry、uv 三種套件管理工具。 JavaScript/TypeScript: 支援 npm、yarn (1 & 3 Berry)、pnpm、bun，含 TypeScript .d.ts API surface diff、workspace/monorepo 偵測、 @types/<pkg> 同步升級偵測。 Go: 支援 go modules、major version path rewrite (v1→v2+)、apidiff
package-upgrade-feedback
收集對 `/package-upgrade` skill 本身的改進建議（流程 / 功能 / UX），開成 GitHub Issue 送到 millerlai/auto-package-migration。當使用者輸入「/package-upgrade-feedback」、 「改進 package-upgrade」、「report package-upgrade issue」、「package-upgrade feedback」、 「想給 package-upgrade 建議」時觸發。 流程：(1) LLM 主動讀 `/package-upgrade` SKILL.md 並從外部視角擬一份 Improvement.md 草稿（純針對 skill 流程與功能面，**完全不引用**使用者環境、套件、ticket、路徑、 token 等私人 / 專案資料）→ (2) 用 `AskUserQuestion` 工具以「多選 + 自動 Other 自由輸入」 方式收集使用者優先項與補充意見 → (3) 整合為 final issue body 並過 `sanitize_feedback.sh` 過濾敏感資料 → (4) Review gate：使用者選 `y` 立即送出 / `edit` 修改 / `n` 取消 → (5) `gh issue create` 送到 millerlai/auto-package-migration (label=feedback)。
sprint-effort-report
Generate a per-assignee effort summary from a Jira sprint CSV export. Use when the user provides a sprint CSV file (e.g. s144.csv, sprint export) and wants to summarize effort by assignee, see who helped on cross-team subtasks, or understand sprint load distribution. Produces a new markdown report file.
sprint-to-jira
Generate agile user stories and bulk-create Jira tickets from a sprint planning markdown file's Feature Summary table. Use when given a sprint doc and asked to create Jira tickets, generate stories for sprint features, or run the sprint-to-jira pipeline. Triggers on phrases like "create jira tickets for sprint", "generate stories from sprint doc", "make tickets for each feature", or "foreach item in sprint".
jira-sync
CHANGELOG 기반 Jira 티켓 상태를 Git 브랜치 상태에 맞게 동기화하는 로직을 가이드합니다.
slopstop-gh-init
Bootstrap a GitHub repo for the slopstop ticket workflow. Creates status labels, writes .project-conf.toml. Invoke as /slopstop:gh-init (or /slopstop-gh-init). Idempotent — safe to re-run.
sync-jira-tickets-command
Run the `platform-dev-team-common:sync-jira-tickets` workflow from the original Claude slash command. Use when the user asks to 현재 프로젝트의 CHANGELOG.md에 있는 Jira 티켓들을 Git 브랜치 상태에 맞게 동기화합니다.
archive
End the local lifecycle for a ticket. Delegates the documentation push to /slopstop:document (description body + DoD-confirmation comment + findings comment, with idempotent skip-when-current and divergence-stop safety), then mv the local tracking dir to ~/.claude/ticket-archive/. Use /slopstop:archive AFTER moving the ticket to a terminal state (Done/Closed/etc.) on the ticket system yourself. Refuses to run otherwise. Does NOT support --force — if the documentation push would overwrite a divergent managed version on the ticket, archive stops cleanly; the user runs /slopstop:document --force separately to overwrite (after eyeballing the diff), then re-runs :archive. Auto-detects ticket system.
create-gh
Create a new GitHub issue and assign it a BILL ticket key that matches the GitHub issue number — so BILL-N always equals GitHub issue
doc-sync
Mirror the design/ directory to the project's ticket-system documentation store (GitHub wiki, Linear Docs). One-way push; design/ files unchanged; orphan pages pruned. Reads .project-conf.toml for the backend. Use /slopstop:doc-sync.
document
Sync the active ticket's local tracking documentation (task plan, DoD-confirmation evidence, findings) to the ticket on Linear/JIRA. Use /slopstop:document to push or refresh the description + DoD-confirmation comment + findings comment WITHOUT ending the local lifecycle (no archive, no local-dir move, no state change). Idempotent — running it twice on unchanged local state is a clean no-op. Safe by default — if the ticket already has managed documentation that differs from what would be pushed (e.g., someone hand-edited the description), stops with a per-artifact diff explanation and refuses to push anything. --force overrides the divergence check. --dry-run shows what would happen without doing it. Auto-detects ticket system.
merge
End-to-end "ship it" for the active ticket — code side only. Use /slopstop:merge to merge the PR, advance the ticket by one state in its workflow on Linear/JIRA (NOT auto-Done — same-bucket transitions like "In Progress" → "In Review" are preferred over jumps to Done so review/QA gates aren't skipped), and delete the merged branch. Does NOT archive local tracking or push the task plan back to the ticket — that's /slopstop:archive, which the user runs separately once the ticket actually reaches a terminal Done-type state (typically after QA). The end-of-run summary classifies the post-transition state and tells the user whether to run :archive now or wait. Confirms once before any destructive remote operation; the confirmation prompt shows the specific computed next state so you know what you're agreeing to. Refuses safely on dirty trees, unpushed commits, draft PRs, or merge conflicts. Auto-detects ticket system.
plan
Replace the active ticket's empty Plan section with a thorough, parallelism-aware plan grounded in real codebase investigation, starting with a Phase 0 that writes RED tests for the expected behavior. Also drafts a client-readable Definition of Done (plain-language observable outcomes) that ends up at the top of the ticket description on archive. Use /slopstop:plan [constraint] — the optional textual constraint scopes BOTH the investigation and the resulting plan literally. Phase 0's red tests anchor each work item's "Done when" criteria. The skill confirms before destructive actions (commit before fanout, agent launch, auto-merge); auto-stops hard-stuck agents (60+ min no commits AND repeating errors); never auto-merges without your explicit yes.
pr
Open a pull request for the active ticket's branch with pre-commit simplify + tests + configurable review (CodeRabbit or Claude). Use /slopstop:pr to (1) run Claude Code's code-simplifier agent on uncommitted changes, (2) run the project's tests and refuse to commit on failures, (3) commit with a ticket-anchored message, (4) push and open a PR via GitHub MCP or gh CLI, (5) trigger or run the configured review backend — CodeRabbit (default) or Claude /code-review — posting findings to the PR, and (6) categorize the suggestions for action. Stops after presenting — never auto-applies (unless fix = true in [pr_review], which commits fixable findings after code-review completes). Review backend is set via [pr_review] in .project-conf.toml; omit the block to keep CodeRabbit as the default.
search
Semantic search over the project's RAG-indexed ticket corpus and code graph. /slopstop:search "<query>" finds tickets by semantic similarity (descriptions + comments); optional subcommands --callers, --implementors, --blast-radius, and --ticket-code navigate the SCIP code graph. Reads [rag] from .project-conf.toml (endpoint, corpus_scope); gracefully degrades if [rag] is absent or if the RAG service is not running.
start
Start or resume work on a Linear or JIRA ticket. Use /slopstop:start <KEY> (e.g. /slopstop:start MAZ-26). Fresh-starts a new ticket (fetches it, transitions to In Progress, asks for a Conventional-Commits-style branch type and creates a feature branch like fix/MAZ-26 or feat/MAZ-26 — with a heuristic suggestion from labels/title and the choice between branching off the default branch vs the current branch when cwd is on a feature branch, plus a "skip" option to opt out of branch creation entirely — then seeds tracking files), or resumes an existing one. Auto-detects ticket system.
update
Mid-session checkpoint to the active ticket's progress.md. Use /slopstop:update to snapshot what's been done so far during the same ticket session. The ticket stays active. Local-only — never calls JIRA or Linear.
jira
This skill should be used when the user mentions a Jira ticket key (e.g. SOX-1234, DEVTOOLS-456), asks about ticket details, or wants to look up a Jira issue. Fetches live ticket data from Jira Cloud.
Integration detected automatically from skill content. Some results may be false positives.