What problem does it solve? Turning a feature request or bug report into properly scoped Jira issues, correctly named git branches, and isolated worktrees is repetitive manual setup that is easy to get wrong, especially when deciding whether work should split into parallel sub-tasks or follow a hotfix path. ## Core Features & Use Cases - Issue scoping and creation: Investigates the codebase, asks clarifying questions, and decides whether the request is one self-contained task or splits into parallel sub-tasks, then creates the corresponding Task, Story, Bug, or Sub-task issues in Jira. - Branch and worktree provisioning: Creates one feature/ branch and git worktree per leaf issue off the default base branch, or a single hotfix/ branch off the production branch for emergency production fixes. - Executor handoff: Leaves PR-target comments on each issue and an Assignment report so downstream executor skills can pick up work in each worktree with no issue-key argument. - Use Case: Paste a feature description like "add OAuth login with a settings page" and receive a parent Jira issue, two sub-tasks with their own branches and worktrees, ready for parallel implementation. ## Quick Start Run the jira-task-assigner skill from the main repo checkout on the base branch with your task description as the argument to create the Jira issues, branches, and worktrees.
