[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AS5MH2CHWCH2X8NWTXMQAV":3,"skill-same:01M7AS5MH2CHWCH2X8NWTXMQAV":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AS5MH2CHWCH2X8NWTXMQAV","jira-expert",null,"Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use when setting up or configuring Jira projects, writing JQL and advanced searches, creating dashboards, designing workflows, or performing technical Jira operations.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"jira-expert\"\ndescription: Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use when setting up or configuring Jira projects, writing JQL and advanced searches, creating dashboards, designing workflows, or performing technical Jira operations.\n---\n\n# Atlassian Jira Expert\n\nMaster-level expertise in Jira configuration, project management, JQL, workflows, automation, and reporting. Handles all technical and operational aspects of Jira.\n\n## Quick Start — Most Common Operations\n\nAll MCP examples in this skill use the real Atlassian Remote MCP tools (camelCase, surfaced as `mcp__atlassian__\u003CtoolName>`). The canonical tool list is `project-management\u002Freferences\u002Fatlassian-mcp-tools.md` — never invent tool names; if a capability isn't listed there, it is not available via MCP.\n\n**Create an issue** (call `getAccessibleAtlassianResources` once first to obtain `cloudId`):\n```\nmcp__atlassian__createJiraIssue (cloudId, projectKey=\"MYPROJ\", issueTypeName=\"Story\", summary=\"My new story\")\n```\n\n**Run a JQL query** (build the JQL from natural language with the bundled script, then execute):\n```bash\npython3 scripts\u002Fjql_query_builder.py \"high priority bugs assigned to me\"\n# → emits validated JQL, e.g.: assignee = currentUser() AND type = Bug AND status != Done\n```\n```\nmcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql=\"project = MYPROJ AND status != Done AND dueDate \u003C now()\")\n```\n\n**Create a project**: NOT available via MCP. Use the Jira web UI (`Projects > Create project`) or REST API (`POST \u002Frest\u002Fapi\u002F3\u002Fproject`).\n\nFor the full tool reference, see [Atlassian MCP Integration](#atlassian-mcp-integration). For JQL functions, see [JQL Functions Reference](#jql-functions-reference). For report templates, see [Reporting Templates](#reporting-templates).\n\n---\n\n## Workflows\n\n### Project Creation\n\n> Project creation is **not available via MCP** — perform steps 2-6 in the Jira web UI (`Projects > Create project`) or via REST API (`POST \u002Frest\u002Fapi\u002F3\u002Fproject`). After creation, verify visibility with `mcp__atlassian__getVisibleJiraProjects` and inspect issue types with `mcp__atlassian__getJiraProjectIssueTypesMetadata`.\n\n1. Determine project type (Scrum, Kanban, Bug Tracking, etc.)\n2. Create project with appropriate template (web UI \u002F REST)\n3. Configure project settings:\n   - Name, key, description\n   - Project lead and default assignee\n   - Notification scheme\n   - Permission scheme\n4. Set up issue types and workflows\n5. Configure custom fields if needed\n6. Create initial board\u002Fbacklog view\n7. **HANDOFF TO**: Scrum Master for team onboarding\n\n### Workflow Design\n\n> Workflow\u002Fscheme editing is **not available via MCP** — configure in `Jira Settings > Issues > Workflows`. Use the bundled validator to catch anti-patterns before deploying.\n\n1. Map out process states (To Do → In Progress → Done)\n2. Define transitions and conditions\n3. Lint the design before building it in Jira:\n   ```bash\n   python3 scripts\u002Fworkflow_validator.py workflow.json --format json\n   ```\n   Input: a JSON file with the workflow's `states` and `transitions`. Consume the output: fix every reported anti-pattern (dead-end states, unreachable states, missing transitions) in the design before touching Jira.\n4. Add validators, post-functions, and conditions; configure the workflow scheme (web UI)\n5. **Validate**: Deploy to a test project first; verify all transitions, conditions, and post-functions behave as expected before associating with production projects\n6. Associate workflow with project\n7. Test workflow with sample issues — via MCP: `mcp__atlassian__getTransitionsForJiraIssue` on a sample issue to confirm expected transitions surface, then `mcp__atlassian__transitionJiraIssue` to walk it through the flow\n\n### JQL Query Building\n\n**Start with the bundled builder** — it pattern-matches natural language to validated JQL:\n```bash\npython3 scripts\u002Fjql_query_builder.py \"high priority bugs assigned to me\" --format json\npython3 scripts\u002Fjql_query_builder.py --patterns   # list all supported query patterns\n```\nConsume the output: take the `jql` field from the JSON result (or the GENERATED JQL block in text mode) and execute it with `mcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql=\u003Cgenerated>)`. If the builder reports no pattern match, compose JQL manually using the reference below.\n\n**Basic Structure**: `field operator value`\n\n**Common Operators**:\n- `=, !=` : equals, not equals\n- `~, !~` : contains, not contains\n- `>, \u003C, >=, \u003C=` : comparison\n- `in, not in` : list membership\n- `is empty, is not empty`\n- `was, was in, was not`\n- `changed`\n\n**Powerful JQL Examples**:\n\nFind overdue issues:\n```jql\ndueDate \u003C now() AND status != Done\n```\n\nSprint burndown issues:\n```jql\nsprint = 23 AND status changed TO \"Done\" DURING (startOfSprint(), endOfSprint())\n```\n\nFind stale issues:\n```jql\nupdated \u003C -30d AND status != Done\n```\n\nCross-project epic tracking:\n```jql\n\"Epic Link\" = PROJ-123 ORDER BY rank\n```\n\nVelocity calculation:\n```jql\nsprint in closedSprints() AND resolution = Done\n```\n\nTeam capacity:\n```jql\nassignee in (user1, user2) AND sprint in openSprints()\n```\n\n### Dashboard Creation\n1. Create new dashboard (personal or shared)\n2. Add relevant gadgets:\n   - Filter Results (JQL-based)\n   - Sprint Burndown\n   - Velocity Chart\n   - Created vs Resolved\n   - Pie Chart (status distribution)\n3. Arrange layout for readability\n4. Configure automatic refresh\n5. Share with appropriate teams\n6. **HANDOFF TO**: Senior PM or Scrum Master for use\n\n### Automation Rules\n1. Define trigger (issue created, field changed, scheduled)\n2. Add conditions (if applicable)\n3. Define actions:\n   - Update field\n   - Send notification\n   - Create subtask\n   - Transition issue\n   - Post comment\n4. Test automation with sample data\n5. Enable and monitor\n\n## Advanced Features\n\n### Custom Fields\n**When to Create**:\n- Track data not in standard fields\n- Capture process-specific information\n- Enable advanced reporting\n\n**Field Types**: Text, Numeric, Date, Select (single\u002Fmulti\u002Fcascading), User picker\n\n**Configuration**:\n1. Create custom field\n2. Configure field context (which projects\u002Fissue types)\n3. Add to appropriate screens\n4. Update search templates if needed\n\n### Issue Linking\n**Link Types**:\n- Blocks \u002F Is blocked by\n- Relates to\n- Duplicates \u002F Is duplicated by\n- Clones \u002F Is cloned by\n- Epic-Story relationship\n\n**Best Practices**:\n- Use Epic linking for feature grouping\n- Use blocking links to show dependencies\n- Document link reasons in comments\n\n### Permissions & Security\n\n**Permission Schemes**:\n- Browse Projects\n- Create\u002FEdit\u002FDelete Issues\n- Administer Projects\n- Manage Sprints\n\n**Security Levels**:\n- Define confidential issue visibility\n- Control access to sensitive data\n- Audit security changes\n\n### Bulk Operations\n**Bulk Change**:\n1. Use JQL to find target issues\n2. Select bulk change operation\n3. Choose fields to update\n4. **Validate**: Preview all changes before executing; confirm the JQL filter matches only intended issues — bulk edits are difficult to reverse\n5. Execute and confirm\n6. Monitor background task\n\n**Bulk Transitions**:\n- Move multiple issues through workflow\n- Useful for sprint cleanup\n- Requires appropriate permissions\n- **Validate**: Run the JQL filter and review results in small batches before applying at scale\n\n## JQL Functions Reference\n\n> **Tip**: Save frequently used queries as named filters instead of re-running complex JQL ad hoc. See [Best Practices](#best-practices) for performance guidance.\n\n**Date**: `startOfDay()`, `endOfDay()`, `startOfWeek()`, `endOfWeek()`, `startOfMonth()`, `endOfMonth()`, `startOfYear()`, `endOfYear()`\n\n**Sprint**: `openSprints()`, `closedSprints()`, `futureSprints()`\n\n**User**: `currentUser()`, `membersOf(\"group\")`\n\n**Advanced**: `issueHistory()`, `linkedIssues()`, `issuesWithFixVersions()`\n\n## Reporting Templates\n\n> **Tip**: These JQL snippets can be saved as shared filters or wired directly into Dashboard gadgets (see [Dashboard Creation](#dashboard-creation)).\n\n| Report | JQL |\n|---|---|\n| Sprint Report | `project = PROJ AND sprint = 23` |\n| Team Velocity | `assignee in (team) AND sprint in closedSprints() AND resolution = Done` |\n| Bug Trend | `type = Bug AND created >= -30d` |\n| Blocker Analysis | `priority = Blocker AND status != Done` |\n\n## Decision Framework\n\n**When to Escalate to Atlassian Admin**:\n- Need new project permission scheme\n- Require custom workflow scheme across org\n- User provisioning or deprovisioning\n- License or billing questions\n- System-wide configuration changes\n\n**When to Collaborate with Scrum Master**:\n- Sprint board configuration\n- Backlog prioritization views\n- Team-specific filters\n- Sprint reporting needs\n\n**When to Collaborate with Senior PM**:\n- Portfolio-level reporting\n- Cross-project dashboards\n- Executive visibility needs\n- Multi-project dependencies\n\n## Handoff Protocols\n\n**FROM Senior PM**:\n- Project structure requirements\n- Workflow and field needs\n- Reporting requirements\n- Integration needs\n\n**TO Senior PM**:\n- Cross-project metrics\n- Issue trends and patterns\n- Workflow bottlenecks\n- Data quality insights\n\n**FROM Scrum Master**:\n- Sprint board configuration requests\n- Workflow optimization needs\n- Backlog filtering requirements\n- Velocity tracking setup\n\n**TO Scrum Master**:\n- Configured sprint boards\n- Velocity reports\n- Burndown charts\n- Team capacity views\n\n## Best Practices\n\n**Data Quality**:\n- Enforce required fields with field validation rules\n- Use consistent issue key naming conventions per project type\n- Schedule regular cleanup of stale\u002Forphaned issues\n\n**Performance**:\n- Avoid leading wildcards in JQL (`~` on large text fields is expensive)\n- Use saved filters instead of re-running complex JQL ad hoc\n- Limit dashboard gadgets to reduce page load time\n- Archive completed projects rather than deleting to preserve history\n\n**Governance**:\n- Document rationale for custom workflow states and transitions\n- Version-control permission\u002Fworkflow schemes before making changes\n- Require change management review for org-wide scheme updates\n- Run permission audits after user role changes\n\n## Atlassian MCP Integration\n\n**Primary Tool**: Atlassian Remote MCP server (bundled `.mcp.json`, server key `atlassian`). Tools surface as `mcp__atlassian__\u003CtoolName>`. **Canonical tool list**: `project-management\u002Freferences\u002Fatlassian-mcp-tools.md`. Never invent tool names — if a capability isn't in that list, route to the web UI\u002FREST API.\n\n**Key Operations with Example Calls** (obtain `cloudId` once via `mcp__atlassian__getAccessibleAtlassianResources`):\n\nCreate an issue (check required fields first with `getJiraIssueTypeMetaWithFields`):\n```\nmcp__atlassian__createJiraIssue (cloudId, projectKey=\"MYPROJ\", issueTypeName=\"Story\", summary=\"My new story\")\n```\n\nExecute a JQL query:\n```\nmcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql=\"project = MYPROJ AND status != Done AND dueDate \u003C now()\")\n```\n\nUpdate an issue field:\n```\nmcp__atlassian__editJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", fields=\u003Cpayload — discover via tool schema>)\n```\n\nTransition an issue (status changes go through transitions, not field edits):\n```\nmcp__atlassian__getTransitionsForJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\")\nmcp__atlassian__transitionJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", transition=\u003Cid from previous call>)\n```\n\nComment \u002F log work \u002F link issues:\n```\nmcp__atlassian__addCommentToJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", body=\"...\")\nmcp__atlassian__addWorklogToJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", timeSpent=\u003Cdiscover via tool schema>)\nmcp__atlassian__createIssueLink (cloudId, link type from mcp__atlassian__getIssueLinkTypes)\n```\n\n**Not available via MCP — use the web UI or REST API instead:**\n- Create a **project** → Jira UI `Projects > Create project` or `POST \u002Frest\u002Fapi\u002F3\u002Fproject`\n- Create a **sprint** or configure boards → Jira Software UI or `POST \u002Frest\u002Fagile\u002F1.0\u002Fsprint`\n- Create\u002Fshare a **filter** → Jira UI `Filters > Save as` or `POST \u002Frest\u002Fapi\u002F3\u002Ffilter`\n- Custom fields, screens, workflow\u002Fpermission schemes → Jira admin UI\n\n**Integration Points**:\n- Pull metrics for Senior PM reporting\n- Configure sprint boards for Scrum Master\n- Create documentation pages for Confluence Expert\n- Support template creation for Template Creator\n\n## Related Skills\n\n- **Confluence Expert** (`project-management\u002Fconfluence-expert\u002F`) — Documentation complements Jira workflows\n- **Atlassian Admin** (`project-management\u002Fatlassian-admin\u002F`) — Permission and user management for Jira projects\n","# Atlassian Jira Expert\n\nMaster-level expertise in Jira configuration, project management, JQL, workflows, automation, and reporting. Handles all technical and operational aspects of Jira.\n\n## Quick Start — Most Common Operations\n\nAll MCP examples in this skill use the real Atlassian Remote MCP tools (camelCase, surfaced as `mcp__atlassian__\u003CtoolName>`). The canonical tool list is `project-management\u002Freferences\u002Fatlassian-mcp-tools.md` — never invent tool names; if a capability isn't listed there, it is not available via MCP.\n\n**Create an issue** (call `getAccessibleAtlassianResources` once first to obtain `cloudId`):\n```\nmcp__atlassian__createJiraIssue (cloudId, projectKey=\"MYPROJ\", issueTypeName=\"Story\", summary=\"My new story\")\n```\n\n**Run a JQL query** (build the JQL from natural language with the bundled script, then execute):\n```bash\npython3 scripts\u002Fjql_query_builder.py \"high priority bugs assigned to me\"\n# → emits validated JQL, e.g.: assignee = currentUser() AND type = Bug AND status != Done\n```\n```\nmcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql=\"project = MYPROJ AND status != Done AND dueDate \u003C now()\")\n```\n\n**Create a project**: NOT available via MCP. Use the Jira web UI (`Projects > Create project`) or REST API (`POST \u002Frest\u002Fapi\u002F3\u002Fproject`).\n\nFor the full tool reference, see [Atlassian MCP Integration](#atlassian-mcp-integration). For JQL functions, see [JQL Functions Reference](#jql-functions-reference). For report templates, see [Reporting Templates](#reporting-templates).\n\n---\n\n## Workflows\n\n### Project Creation\n\n> Project creation is **not available via MCP** — perform steps 2-6 in the Jira web UI (`Projects > Create project`) or via REST API (`POST \u002Frest\u002Fapi\u002F3\u002Fproject`). After creation, verify visibility with `mcp__atlassian__getVisibleJiraProjects` and inspect issue types with `mcp__atlassian__getJiraProjectIssueTypesMetadata`.\n\n1. Determine project type (Scrum, Kanban, Bug Tracking, etc.)\n2. Create project with appropriate template (web UI \u002F REST)\n3. Configure project settings:\n   - Name, key, description\n   - Project lead and default assignee\n   - Notification scheme\n   - Permission scheme\n4. Set up issue types and workflows\n5. Configure custom fields if needed\n6. Create initial board\u002Fbacklog view\n7. **HANDOFF TO**: Scrum Master for team onboarding\n\n### Workflow Design\n\n> Workflow\u002Fscheme editing is **not available via MCP** — configure in `Jira Settings > Issues > Workflows`. Use the bundled validator to catch anti-patterns before deploying.\n\n1. Map out process states (To Do → In Progress → Done)\n2. Define transitions and conditions\n3. Lint the design before building it in Jira:\n   ```bash\n   python3 scripts\u002Fworkflow_validator.py workflow.json --format json\n   ```\n   Input: a JSON file with the workflow's `states` and `transitions`. Consume the output: fix every reported anti-pattern (dead-end states, unreachable states, missing transitions) in the design before touching Jira.\n4. Add validators, post-functions, and conditions; configure the workflow scheme (web UI)\n5. **Validate**: Deploy to a test project first; verify all transitions, conditions, and post-functions behave as expected before associating with production projects\n6. Associate workflow with project\n7. Test workflow with sample issues — via MCP: `mcp__atlassian__getTransitionsForJiraIssue` on a sample issue to confirm expected transitions surface, then `mcp__atlassian__transitionJiraIssue` to walk it through the flow\n\n### JQL Query Building\n\n**Start with the bundled builder** — it pattern-matches natural language to validated JQL:\n```bash\npython3 scripts\u002Fjql_query_builder.py \"high priority bugs assigned to me\" --format json\npython3 scripts\u002Fjql_query_builder.py --patterns   # list all supported query patterns\n```\nConsume the output: take the `jql` field from the JSON result (or the GENERATED JQL block in text mode) and execute it with `mcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql=\u003Cgenerated>)`. If the builder reports no pattern match, compose JQL manually using the reference below.\n\n**Basic Structure**: `field operator value`\n\n**Common Operators**:\n- `=, !=` : equals, not equals\n- `~, !~` : contains, not contains\n- `>, \u003C, >=, \u003C=` : comparison\n- `in, not in` : list membership\n- `is empty, is not empty`\n- `was, was in, was not`\n- `changed`\n\n**Powerful JQL Examples**:\n\nFind overdue issues:\n```jql\ndueDate \u003C now() AND status != Done\n```\n\nSprint burndown issues:\n```jql\nsprint = 23 AND status changed TO \"Done\" DURING (startOfSprint(), endOfSprint())\n```\n\nFind stale issues:\n```jql\nupdated \u003C -30d AND status != Done\n```\n\nCross-project epic tracking:\n```jql\n\"Epic Link\" = PROJ-123 ORDER BY rank\n```\n\nVelocity calculation:\n```jql\nsprint in closedSprints() AND resolution = Done\n```\n\nTeam capacity:\n```jql\nassignee in (user1, user2) AND sprint in openSprints()\n```\n\n### Dashboard Creation\n1. Create new dashboard (personal or shared)\n2. Add relevant gadgets:\n   - Filter Results (JQL-based)\n   - Sprint Burndown\n   - Velocity Chart\n   - Created vs Resolved\n   - Pie Chart (status distribution)\n3. Arrange layout for readability\n4. Configure automatic refresh\n5. Share with appropriate teams\n6. **HANDOFF TO**: Senior PM or Scrum Master for use\n\n### Automation Rules\n1. Define trigger (issue created, field changed, scheduled)\n2. Add conditions (if applicable)\n3. Define actions:\n   - Update field\n   - Send notification\n   - Create subtask\n   - Transition issue\n   - Post comment\n4. Test automation with sample data\n5. Enable and monitor\n\n## Advanced Features\n\n### Custom Fields\n**When to Create**:\n- Track data not in standard fields\n- Capture process-specific information\n- Enable advanced reporting\n\n**Field Types**: Text, Numeric, Date, Select (single\u002Fmulti\u002Fcascading), User picker\n\n**Configuration**:\n1. Create custom field\n2. Configure field context (which projects\u002Fissue types)\n3. Add to appropriate screens\n4. Update search templates if needed\n\n### Issue Linking\n**Link Types**:\n- Blocks \u002F Is blocked by\n- Relates to\n- Duplicates \u002F Is duplicated by\n- Clones \u002F Is cloned by\n- Epic-Story relationship\n\n**Best Practices**:\n- Use Epic linking for feature grouping\n- Use blocking links to show dependencies\n- Document link reasons in comments\n\n### Permissions & Security\n\n**Permission Schemes**:\n- Browse Projects\n- Create\u002FEdit\u002FDelete Issues\n- Administer Projects\n- Manage Sprints\n\n**Security Levels**:\n- Define confidential issue visibility\n- Control access to sensitive data\n- Audit security changes\n\n### Bulk Operations\n**Bulk Change**:\n1. Use JQL to find target issues\n2. Select bulk change operation\n3. Choose fields to update\n4. **Validate**: Preview all changes before executing; confirm the JQL filter matches only intended issues — bulk edits are difficult to reverse\n5. Execute and confirm\n6. Monitor background task\n\n**Bulk Transitions**:\n- Move multiple issues through workflow\n- Useful for sprint cleanup\n- Requires appropriate permissions\n- **Validate**: Run the JQL filter and review results in small batches before applying at scale\n\n## JQL Functions Reference\n\n> **Tip**: Save frequently used queries as named filters instead of re-running complex JQL ad hoc. See [Best Practices](#best-practices) for performance guidance.\n\n**Date**: `startOfDay()`, `endOfDay()`, `startOfWeek()`, `endOfWeek()`, `startOfMonth()`, `endOfMonth()`, `startOfYear()`, `endOfYear()`\n\n**Sprint**: `openSprints()`, `closedSprints()`, `futureSprints()`\n\n**User**: `currentUser()`, `membersOf(\"group\")`\n\n**Advanced**: `issueHistory()`, `linkedIssues()`, `issuesWithFixVersions()`\n\n## Reporting Templates\n\n> **Tip**: These JQL snippets can be saved as shared filters or wired directly into Dashboard gadgets (see [Dashboard Creation](#dashboard-creation)).\n\n| Report | JQL |\n|---|---|\n| Sprint Report | `project = PROJ AND sprint = 23` |\n| Team Velocity | `assignee in (team) AND sprint in closedSprints() AND resolution = Done` |\n| Bug Trend | `type = Bug AND created >= -30d` |\n| Blocker Analysis | `priority = Blocker AND status != Done` |\n\n## Decision Framework\n\n**When to Escalate to Atlassian Admin**:\n- Need new project permission scheme\n- Require custom workflow scheme across org\n- User provisioning or deprovisioning\n- License or billing questions\n- System-wide configuration changes\n\n**When to Collaborate with Scrum Master**:\n- Sprint board configuration\n- Backlog prioritization views\n- Team-specific filters\n- Sprint reporting needs\n\n**When to Collaborate with Senior PM**:\n- Portfolio-level reporting\n- Cross-project dashboards\n- Executive visibility needs\n- Multi-project dependencies\n\n## Handoff Protocols\n\n**FROM Senior PM**:\n- Project structure requirements\n- Workflow and field needs\n- Reporting requirements\n- Integration needs\n\n**TO Senior PM**:\n- Cross-project metrics\n- Issue trends and patterns\n- Workflow bottlenecks\n- Data quality insights\n\n**FROM Scrum Master**:\n- Sprint board configuration requests\n- Workflow optimization needs\n- Backlog filtering requirements\n- Velocity tracking setup\n\n**TO Scrum Master**:\n- Configured sprint boards\n- Velocity reports\n- Burndown charts\n- Team capacity views\n\n## Best Practices\n\n**Data Quality**:\n- Enforce required fields with field validation rules\n- Use consistent issue key naming conventions per project type\n- Schedule regular cleanup of stale\u002Forphaned issues\n\n**Performance**:\n- Avoid leading wildcards in JQL (`~` on large text fields is expensive)\n- Use saved filters instead of re-running complex JQL ad hoc\n- Limit dashboard gadgets to reduce page load time\n- Archive completed projects rather than deleting to preserve history\n\n**Governance**:\n- Document rationale for custom workflow states and transitions\n- Version-control permission\u002Fworkflow schemes before making changes\n- Require change management review for org-wide scheme updates\n- Run permission audits after user role changes\n\n## Atlassian MCP Integration\n\n**Primary Tool**: Atlassian Remote MCP server (bundled `.mcp.json`, server key `atlassian`). Tools surface as `mcp__atlassian__\u003CtoolName>`. **Canonical tool list**: `project-management\u002Freferences\u002Fatlassian-mcp-tools.md`. Never invent tool names — if a capability isn't in that list, route to the web UI\u002FREST API.\n\n**Key Operations with Example Calls** (obtain `cloudId` once via `mcp__atlassian__getAccessibleAtlassianResources`):\n\nCreate an issue (check required fields first with `getJiraIssueTypeMetaWithFields`):\n```\nmcp__atlassian__createJiraIssue (cloudId, projectKey=\"MYPROJ\", issueTypeName=\"Story\", summary=\"My new story\")\n```\n\nExecute a JQL query:\n```\nmcp__atlassian__searchJiraIssuesUsingJql (cloudId, jql=\"project = MYPROJ AND status != Done AND dueDate \u003C now()\")\n```\n\nUpdate an issue field:\n```\nmcp__atlassian__editJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", fields=\u003Cpayload — discover via tool schema>)\n```\n\nTransition an issue (status changes go through transitions, not field edits):\n```\nmcp__atlassian__getTransitionsForJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\")\nmcp__atlassian__transitionJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", transition=\u003Cid from previous call>)\n```\n\nComment \u002F log work \u002F link issues:\n```\nmcp__atlassian__addCommentToJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", body=\"...\")\nmcp__atlassian__addWorklogToJiraIssue (cloudId, issueIdOrKey=\"MYPROJ-42\", timeSpent=\u003Cdiscover via tool schema>)\nmcp__atlassian__createIssueLink (cloudId, link type from mcp__atlassian__getIssueLinkTypes)\n```\n\n**Not available via MCP — use the web UI or REST API instead:**\n- Create a **project** → Jira UI `Projects > Create project` or `POST \u002Frest\u002Fapi\u002F3\u002Fproject`\n- Create a **sprint** or configure boards → Jira Software UI or `POST \u002Frest\u002Fagile\u002F1.0\u002Fsprint`\n- Create\u002Fshare a **filter** → Jira UI `Filters > Save as` or `POST \u002Frest\u002Fapi\u002F3\u002Ffilter`\n- Custom fields, screens, workflow\u002Fpermission schemes → Jira admin UI\n\n**Integration Points**:\n- Pull metrics for Senior PM reporting\n- Configure sprint boards for Scrum Master\n- Create documentation pages for Confluence Expert\n- Support template creation for Template Creator\n\n## Related Skills\n\n- **Confluence Expert** (`project-management\u002Fconfluence-expert\u002F`) — Documentation complements Jira workflows\n- **Atlassian Admin** (`project-management\u002Fatlassian-admin\u002F`) — Permission and user management for Jira projects\n",{"name":5,"description":7},"main","992d25a425dee442a1f6a628d00a4fed33efe839","project-management\u002Fskills\u002Fjira-expert","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill jira-expert",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill jira-expert",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill jira-expert","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002FSKILL.md",true,[45,51,55,59,63,69],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"references\u002Fautomation-examples.md","REFERENCE","参考文档",9668,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002Freferences\u002Fautomation-examples.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002FAUTOMATION.md",9163,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002Freferences\u002FAUTOMATION.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fjql-examples.md",7820,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002Freferences\u002Fjql-examples.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002FWORKFLOWS.md",6431,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002Freferences\u002FWORKFLOWS.md",{"path":64,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Fjql_query_builder.py","SCRIPT","脚本",17953,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002Fscripts\u002Fjql_query_builder.py",{"path":70,"resourceType":65,"resourceTypeDesc":66,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fworkflow_validator.py",13972,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fjira-expert\u002Fscripts\u002Fworkflow_validator.py",[74,81,88,95,102,109],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]