valentin

Four skills cover the full cycle: jst-install performs guided first-time setup with healthchecks, jira-task-assigner splits a task description into Jira issues with branches and worktrees, jira-task-executor implements the issue and opens a PR, and jira-task-reviewer posts approve or request-changes verdicts to GitHub and Jira.

Software engineers and team leads who manage development through Jira boards and GitHub pull requests. They suit teams running parallel sub-tasks across git worktrees, handling emergency production hotfixes off the production branch, and enforcing structured review cycles with status transitions.

Run jst-install once per project from the project root. It walks local tooling, GitHub repo preparation, Jira board preparation, and a healthcheck, verifying each with the bundled statuscheck script. It writes the shared .jst/jira-sdlc-tools.env and instructs you which secrets to fill into the local env file by hand.

Re-run jira-task-executor bare from the same issue worktree after a review rejects the PR. It reads the reviewer's findings from the Jira issue and updates the existing PR rather than opening a second one. The issue key always comes from the branch name, never from an argument.

You need a GitHub repository, a Jira board, and a project with the plugin installed via jst-install. The assigner writes no code and opens no PRs; the reviewer never merges and only offers to move approved issues to Done; the installer never reads or writes secrets in the local env file.