work-on-ticket

To automate Jira ticket branch creation and task planning, reference a Jira ticket ID like AGP-782. This fetches ticket details, creates a named git branch, and initiates a planning prompt.

Yes, you can fetch Jira ticket details and create a git branch in one step. By mentioning a Jira ticket like AGP-782, the workflow retrieves the summary and generates a correctly named branch.

Yes, you need MCP Zapier to start work on a Jira ticket. The workflow requires access to Jira data via the MCP Zapier tool to retrieve ticket summaries, descriptions, and statuses.

The best way to generate a branch name from a Jira ticket is using the [TICKET_ID]-[kebab-case-summary] format. This ensures consistent naming and checks git state on staging before creation.

Git state validation performs safe git state checks on staging before creating a Jira branch. This ensures the repository is clean and ready before checking out the newly generated branch.

After the Jira branch is created, the workflow initiates task planning by constructing a /eng:chore prompt. This generates a concise, actionable planning prompt for execution.