From aai-pm-jira
Fetches Jira ticket details by <ticket-key>, creates feature branch from main/develop, gathers codebase context, updates status to In Progress, and plans implementation.
npx claudepluginhub bradtaylorsf/alphaagent-team<ticket-key># /jira-start - Start Working on Jira Ticket Begin implementation on a specific Jira ticket. ## Usage ## Workflow 1. **Fetch Ticket Details** - Get full ticket description and acceptance criteria - Check current status and assignee - Review linked issues and epic 2. **Branch Setup** - Create appropriately named branch: `feature/PROJ-123-short-description` - Ensure clean working state - Set up ticket reference in branch 3. **Context Gathering** - Explore codebase for relevant files - Identify existing patterns to follow - Note any technical constraints 4. ...
/execute-ticketExecutes a specified Jira ticket (<ticket-key>) following its implementation plan, verifying details, exploring codebase, and offering parallel execution options.
/startCreates feature branch for new PR following repo conventions and config, prompting for ticket ID, change type, description, and fetching details from Linear/Jira/GitHub if available.
/developSpawns orchestrator subagent to autonomously implement ticket via triage-plan-code-review-QA-PR workflow, creates git worktree if needed, updates ticket status.
/ticketCreates a ticket in Linear, GitHub Issues, or Jira: interviews user for details, writes description, files issue, and sets up git branch.
/branchCreates Git branch named {type}/{ISSUE-KEY}-{kebab-description} using Jira issue key, auto-generates description from issue summary, handles existing branches, and optionally transitions issue to In Progress.
Share bugs, ideas, or general feedback.
Begin implementation on a specific Jira ticket.
/jira-start <ticket-key>
/jira-start PROJ-123
/jira-start https://company.atlassian.net/browse/PROJ-123
Fetch Ticket Details
Branch Setup
feature/PROJ-123-short-descriptionContext Gathering
Implementation Planning