setup-new-work

To create a git worktree for a Jira ticket, this skill fetches issue details via Atlassian MCP, derives a slug from the summary, and sets up an isolated worktree at ./worktrees/<ticket-id>-<platform> with a corresponding feature branch.

Naming a feature branch from a Jira ticket summary involves fetching the issue data and generating a deterministic slug. This skill creates a branch named feature/<ticket-id>-<slug>-<platform> while preserving the original ticket key casing.

Yes, Atlassian MCP is required to fetch Jira issue details like the summary and metadata. This information is necessary to derive the branch slug and generate the local story snapshot inside the git worktree.

Generating a local story snapshot from a Jira ticket writes a markdown brief at docs/<ticket-id>/<ticket-id>.md inside the worktree. This file includes the summary, status, priority, people, and parent epic for team visibility.

Using git worktrees is an effective way to isolate development work for multiple Jira tickets. This approach creates separate directories for each task, preventing branch interference while automatically fetching ticket details and setting up feature branches.

A Jira ticket key is strictly enforced because it forms the foundation of the worktree directory name and the feature branch. Without a valid ticket key, the automated branch slug generation and local story snapshot creation cannot proceed accurately.