324 件 ・ 連携ツール: Jira ・ 人気順
Convert the canonical markdown+JSON deliverable of any SfSkills runtime agent into Excel, PDF, CSV, Notion card, ServiceNow ticket, or similar downstream format without adding dependencies to the consumer's project. NOT for an Agentforce action's output — use agentforce/agent-actions. NOT for exporting Salesforce data — use integration/bulk-api-2-patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, or audit a Change Advisory Board (CAB) process for Salesforce deployments: change classification (standard, normal, emergency), required approvals, deployment gate sequencing, and integration with external ITSM tooling. NOT for scoring how risky one release is - use admin/deployment-risk-assessment. NOT for executing or troubleshooting the deployment itself - use admin/change-management-and-deployment. Also covers: the CAB charter (membership, quorum, decision rights), the CAB decision record artefact and its linter, the change classification matrix, the deployOptions a CAB decision pins (checkOnly, testLevel, rollbackOnError, ignoreWarnings, runTests), the 10-day quick-deploy validity window, the deploy-window vs freeze-register check, and the emergency (ECAB) path with its mandatory retrospective.
日本語の概要は準備中です。原文の説明を表示しています。
Validate Jira/JPD ticket reference and create a feature branch
日本語の概要は準備中です。原文の説明を表示しています。
AI Agile/Scrum Coach — sprint ceremony, velocity tracking, retrospective, team coaching รองรับทีม dev + non-dev
日本語の概要は準備中です。原文の説明を表示しています。
Displays the full skills catalog with descriptions, autonomous build chains, recommended pipelines, and parallelization rules.
日本語の概要は準備中です。原文の説明を表示しています。
Maps dependencies between stories, code modules, tickets, or specs. Computes optimal implementation order with parallel batches, cycle detection, and critical path analysis.
日本語の概要は準備中です。原文の説明を表示しています。
Generates backend or frontend engineering specs in structured Jira format with description, categorized acceptance criteria, routes, dev notes, and table schemas.
日本語の概要は準備中です。原文の説明を表示しています。
Draft the QA scope and plain-language test scenarios for a Jira ticket — brief one-liners with automated test references by default, or full Given/When/Then steps — built from the full ticket, the decisions made in its comments, and the actual code change read commit by commit (open PR, the ticket's merged PR, the branch against its base, or a named commit range). Saves a Markdown draft under docs/, iterates with the user, then posts it to the ticket as a new Jira comment only after explicit approval. Use on "QA scope for PROJ-123", "what should QA test", "write test scenarios for QA", "hand this ticket to QA", "prep the QA handoff", "gherkin scenarios for this ticket", or when a branch is ready for manual testing — even when the user only names the ticket or says "this branch".
日本語の概要は準備中です。原文の説明を表示しています。
Turn the git commits for a Jira ticket into a short, business-friendly implementation report and save it as local markdown. Use when the user wants to report finished work on a Jira ticket: a Jira report, update, or comment, a summary of their commits or changes for the ticket, or a note telling PM/QA what shipped.
日本語の概要は準備中です。原文の説明を表示しています。
Use Composio Connect MCP (Tool Router) for authenticated SaaS actions — Gmail, Slack, Notion, Jira, Linear, GitHub, and 1000+ other apps. Rube is deprecated; do not use it.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Triage Linear or Jira backlogs and run bug sweeps via the Composio CLI. Bulk-fetch issues, deduplicate, relabel, reassign, and post summaries all from the shell.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ticket complexity and dependencies against the codebase before sprint planning. NOT for writing plans (mk:plan-creator); NOT for scope review (mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Pre-ticket Fibonacci sizing for pasted stories; advisory by default, writes a Sizing Report. Opt-in auto-create adds a confirm gate. NOT for single-ticket sizing (mk:jira-estimator).
日本語の概要は準備中です。原文の説明を表示しています。
Ship workflow: prepare stages/commits locally; release pushes + opens a PR; publish handles issues + versioning. Use for 'ship', 'push', 'create a PR'. Official (→main) and beta (→dev) modes.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly engineering retrospective from commit history, work patterns, and code-quality metrics, with trend tracking and per-person breakdown. NOT for per-session reflection (mk:memory / Phase 6).
日本語の概要は準備中です。原文の説明を表示しています。
JIRA-side cache + project-context discovery via jira-as, diagnostic-only, no Atlassian state changes. NOT issue CRUD or project admin (mk:jira-admin).
日本語の概要は準備中です。原文の説明を表示しています。
Bulk JIRA ops (10+ issues): transition/assign/priority/clone/delete via jira-as; dry-run mandatory. NOT single-issue ops (mk:jira-issue, mk:jira-lifecycle).
日本語の概要は準備中です。原文の説明を表示しています。
Generate dev artifacts from Jira tickets via jira-as: branch names, PR descriptions, parsed commits, PR-to-issue links. NOT running git/gh (mk:ship) or issue CRUD (mk:jira-issue).
日本語の概要は準備中です。原文の説明を表示しています。
JIRA issue CRUD via jira-as. NOT lifecycle (mk:jira-lifecycle), comments (mk:jira-collaborate), bulk (mk:jira-bulk), links (mk:jira-relationships), or time/sprint (mk:jira-time/agile).
日本語の概要は準備中です。原文の説明を表示しています。
Ticket/PRD intake: product-area classification, completeness scoring, RCA, technical assessment. Works with Jira, Linear, GitHub, or manual paste. Use to analyze or triage a ticket.
日本語の概要は準備中です。原文の説明を表示しています。
JIRA agile via jira-as: epics, sprints, backlog, ranking, story points, velocity. Board ID != project key. NOT issue CRUD (mk:jira-issue) or time tracking (mk:jira-time).
日本語の概要は準備中です。原文の説明を表示しています。
JIRA project/user/group/scheme/automation admin via jira-as. Requires admin role; destructive ops need 2-step confirm. NOT per-issue ops (mk:jira-issue/lifecycle) or JSM admin (mk:jira-jsm).
日本語の概要は準備中です。原文の説明を表示しています。