Split production from base

Gitflow needs two distinct long-lived branches, and a single-branch repo isn't a supported configuration. Point DEFAULT_BASE_BRANCH and PRODUCTION_BRANCH at different branches. First inspect what already exists:

git branch -a
git remote get-url origin

The names are your choice; main and development are the documented defaults. If your repo only has main, create the base branch off it once:

git switch main
git switch -c development
git push -u origin development

Making development the repository default is optional. It only saves people opening PRs by hand from picking the base in the GitHub UI — the plugin passes --base explicitly. The command requires repository administration permission; it is not needed for the plugin itself.

gh repo edit <OWNER>/<REPO> --default-branch development

Then record both in .jst/jira-sdlc-tools.env:

DEFAULT_BASE_BRANCH=development
PRODUCTION_BRANCH=main

Protecting both branches is recommended: everything reaches them through a reviewed PR, which is exactly the flow the skills produce.