jst-install

Guides first-time setup of the jira-sdlc plugin with per-section verification gates.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/kantorv/jira-sdlc-tools --skill jst-install-kantorv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jst-install
Source: https://github.com/kantorv/jira-sdlc-tools/tree/main/plugins/jira-sdlc/skills/jst-install
Command: npx skills add https://github.com/kantorv/jira-sdlc-tools --skill jst-install-kantorv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a Jira-plus-Gitflow automation plugin involves local tooling, GitHub branch preparation, Jira board configuration, and credential wiring, and a single missed step (a missing development branch, a misspelled status name) only surfaces mid-run. This Skill walks the four setup sections in order and verifies each one with a bundled statuscheck script before moving on. ## Core Features & Use Cases - Guided four-section setup: local tooling and .jst/ scaffold, GitHub repository preparation (base branch, worktrees directory), Jira board preparation (project key and status discovery via the Jira REST API), and a full per-role healthcheck. - Verification gates: runs the same statuscheck script the runtime skills use after each section, treating FAIL rows as the worklist until everything is green. - Safe credential handling: writes the team-shared .jst/jira-sdlc-tools.env directly but never reads or edits the secrets file .jst/jira-sdlc-tools.local.env, handing the user the key list to fill in by hand. - Use Case: After installing the jira-sdlc plugin into a project, run this Skill once from the project root to create the .jst/ config, confirm the GitHub PAT can access the repo, map the four Jira status names off the real board, and prove the workflow transitions with a scratch issue. ## Quick Start Run the jst-install skill from my project root to walk through and verify the jira-sdlc plugin setup step by step.

Frequently Asked Questions about jst-install

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the jira-sdlc plugin in my own project?

Run the jst-install skill once from your project root before the first jira-task-assigner run. It walks four sections in order — local tooling, GitHub repo preparation, Jira board preparation, and a healthcheck — verifying each with the bundled statuscheck script.

How do I configure Jira status names for Gitflow automation?

The skill fetches the real status names from your chosen Jira project via the REST API rather than relying on defaults, then asks you to map STATUS_TODO, STATUS_IN_PROGRESS, STATUS_IN_REVIEW, and STATUS_DONE onto them. This avoids literal-match failures from names like "In progress" versus "In Progress".

Does the setup skill read my Jira tokens or GitHub PAT?

No. It never opens or edits `.jst/jira-sdlc-tools.local.env`, which holds the three Jira role tokens and GitHub PAT. It copies the placeholder template into place, hands you the key list, and waits for you to fill it in by hand.

Why does statuscheck fail during installation?

Failing rows are expected mid-install — they are the worklist, not errors. Each section settles its own rows (for example `gh_auth` and `gh_repo_access` in the GitHub section), and later sections' rows stay red until their turn.

Can I rerun jst-install after a token rotation or branch rename?

Yes, rerunning is safe. Every write is create-if-missing or an overwrite of a value you just confirmed, and an existing local.env file is never overwritten, so re-running after changes just confirms what is already in place.