jira-ticket-plan-workflow

What I do

I implement a standardized JIRA ticket creation and planning workflow:

1. Gather Ticket Requirements: Prompt user for structured ticket description following industry best practices
2. Determine Ticket Scope: Ask if ticket is a Story (with subtasks) or a single Task
3. Create JIRA Ticket: Use Atlassian MCP server to create ticket in specified project
4. Create Git Branch: Generate branch from ticket key (e.g., PROJ-123)
5. Generate PLAN-{TICKET_KEY}.md: Create comprehensive plan with phases and todo list
6. Commit and Push: Commit PLAN-{TICKET_KEY}.md with semantic formatting and push to remote
7. Prompt Execution: Ask user if they want to proceed with plan execution

When to use me

Use this workflow when:

• Starting a new development task that needs JIRA tracking
• You want a standardized approach to ticket creation and planning
• You need to break down large work into structured phases
• Following the practice of planning before implementation

Prerequisites

• Active Atlassian/JIRA account with project access
• Git repository initialized with remote configured
• Write access to repository
• Atlassian MCP server configured

Steps

Step 1: Gather Ticket Description

Prompt the user for a structured ticket description with these sections:

Required Information:

1. Summary: Concise title (max 72 characters)
2. Overview: Brief description of what needs to be done
3. Acceptance Criteria: Definition of done (bullet points)
4. Scope: Files or areas affected
5. Technical Notes: Implementation considerations (optional)

Prompt Template:

Please provide the following for your JIRA ticket:

1. **Summary** (required): Brief title for the ticket
   Example: "Implement user authentication API"

2. **Overview** (required): What does this ticket accomplish?
   Example: "Add JWT-based authentication endpoints for user login/registration"

3. **Acceptance Criteria** (required): How do we know it's done?
   Example:
   - Users can register with email/password
   - Users can login and receive JWT token
   - Protected routes validate JWT

4. **Scope** (required): What files/areas will be affected?
   Example: src/api/auth/, src/middleware/, tests/auth/

5. **Technical Notes** (optional): Any implementation details?
   Example: Use bcrypt for password hashing, 24h token expiry