AgentSkillsCN

Jira Sprint Helper

Vanguards 团队的 JIRA Sprint 助手——验证 JIRA 字段、生成工作类型报告，并确保符合冲刺指南

SKILL.md
--- frontmatter
description: JIRA Sprint Helper for Vanguards team - validates JIRA fields, generates work type reports, and ensures compliance with sprint guidelines
allowed-tools:
  - mcp__atlassian__*
  - Read
  - Write
  - Bash

JIRA Sprint Helper Skill

This skill helps manage JIRA issues for the Vanguards team, ensuring proper field population, generating work type reports, and maintaining sprint planning best practices.

Core Capabilities

1. Epic Management

When creating or reviewing JIRA Epics, ensure ALL required fields are filled:

Required Fields:

  • •Epic Name: Clear, descriptive name
  • •Epic Description: Default to "TBD" - NEVER auto-fill, must be manually provided
  • •Work Type (customfield_10348): One of: "Bugs and KTLO", "Engineering Initiatives", "Product Capabilities", "Professional Services"
  • •Epic Assignee: Required if epic is in progress
  • •Due Date: Required if epic is in progress
  • •Quarter Labels: Label with quarters when work is planned (e.g., "2025-Q1", "2025-Q2")

Validation Checklist:

  • •✓ Epic Name is descriptive and clear
  • •✓ Description is "TBD" or manually filled (never auto-generated)
  • •✓ Work Type is set
  • •✓ If in progress: Assignee is set
  • •✓ If in progress: Due Date is set
  • •✓ Quarter labels are applied

2. Story Management

When creating or reviewing JIRA Stories, ensure ALL required fields are filled:

Required Fields:

  • •Story Name: Clear, actionable title
  • •Story Description: Default to "TBD" - NEVER auto-fill
    • •Must include "Definition of Done" section
    • •Ask Reporter to add DoD if not provided
  • •Parent Epic (customfield_10009): Link to parent epic if applicable
  • •Work Type (customfield_10348): Same values as Epic
  • •Sprint (customfield_10010): Current sprint if in progress
  • •Story Points (customfield_10100): Estimated effort
  • •Story Assignee: Required if story is in progress
  • •Start Date (customfield_10044): Required if in progress
  • •DevRel (customfield_10115): Calculate from Sprint name
    • •Example: "Vanguards Sprint 167" → DevRel = "167"

Validation Checklist:

  • •✓ Story Name is clear and actionable
  • •✓ Description is "TBD" or has Definition of Done
  • •✓ Parent Epic linked (if applicable)
  • •✓ Work Type is set
  • •✓ Story Points estimated
  • •✓ If in progress: Sprint assigned
  • •✓ If in progress: Assignee set
  • •✓ If in progress: Start Date set
  • •✓ If in progress: DevRel calculated from Sprint

3. Bug Management

When creating or reviewing JIRA Bugs, ensure ALL required fields are filled:

Required Fields:

  • •Severity: Critical/High/Medium/Low
  • •Bug Source: Where the bug was discovered
  • •Sprint (customfield_10010): Current sprint if in progress
  • •Affected Customers (customfield_10340): List of impacted customers

Required in Description:

  • •Steps to reproduce
  • •Expected result
  • •Actual result
  • •Environment (Production, Staging, etc.)

Validation Checklist:

  • •✓ Severity level set
  • •✓ Bug Source documented
  • •✓ Sprint assigned if in progress
  • •✓ Affected customers listed
  • •✓ Description has: reproduction steps, expected/actual results, environment

4. Work Type Report Generation

Generate sprint or quarter reports showing story point distribution by Work Type.

Report Format:

Work TypeStory PointsPercentage of Sprint
Bugs and KTLOXY%
Engineering InitiativesXY%
Product CapabilitiesXY%
Professional ServicesXY%
TotalX100%

Recommended Allocation (for comparison):

  • •Bugs and KTLO: 15%
  • •Engineering Initiatives: 15%
  • •Product Capabilities: 50%
  • •Professional Services: 20%

Analysis:

  • •Highlight deviations from recommended allocation
  • •Flag if any category is significantly over/under target
  • •Consider only Stories and Bugs (exclude other issue types)

5. DevRel Auto-Calculation

When a Sprint is assigned, automatically suggest the DevRel value:

  • •Extract sprint number from Sprint name
  • •Example: "Vanguards Sprint 167" → DevRel = "167"
  • •Example: "Sprint 168" → DevRel = "168"

6. Field Reference Lookup

Quickly provide custom field IDs when needed. Reference the field-mappings.json file for accurate field IDs.

Usage Patterns

When to Invoke:

  • •User mentions "JIRA", "epic", "story", "bug", "sprint"
  • •User asks to create/update JIRA issues
  • •User requests "work type report" or "sprint report"
  • •User asks about JIRA field requirements
  • •User mentions sprint planning or allocation

What NOT to Do:

  • •Never auto-fill Description fields - always default to "TBD"
  • •Never skip validation checks
  • •Never create issues without checking required fields
  • •Never generate DoD content - ask user to provide it

Team Context

  • •Team Name: Vanguards
  • •JIRA Project: Vanguards
  • •Confluence Space: EN (Engineering) → Vanguards section
  • •Sprint Retrospectives: Stored under "Vanguards Sprints and Retros"
  • •Sprint Duration: 2 weeks

Reference Files

  • •field-mappings.json: Complete list of custom field IDs
  • •work-type-guidelines.md: Detailed work type allocation guidelines
  • •templates/: Issue templates for epics, stories, and bugs

Best Practices

  1. •Always validate before creating/updating issues
  2. •Use actual field IDs from field-mappings.json
  3. •Cross-reference with work type guidelines for reports
  4. •Prompt user for missing information rather than guessing
  5. •Include validation checklist in responses
  6. •Calculate DevRel automatically from Sprint name
  7. •Always compare actual vs recommended allocations in reports