Skip to content

[Extension]: Add jira-lifecycle #5433

Done

Description

@praveenlavu

Extension ID

jira-lifecycle

Extension Name

Spec Kit lifecycle for Jira

Version

0.1.0

Description

A Jira story to Done through Spec Kit, with a human sign-off before every Jira or PR write.

Author

praveenlavu

Repository URL

https://github.com/praveenlavu/spec-kit-jira

Download URL

https://github.com/praveenlavu/spec-kit-jira/archive/refs/tags/v0.1.0.zip

License

MIT

Homepage (optional)

https://github.com/praveenlavu/spec-kit-jira

Documentation URL (optional)

https://github.com/praveenlavu/spec-kit-jira/blob/v0.1.0/README.md

Changelog URL (optional)

https://github.com/praveenlavu/spec-kit-jira/blob/v0.1.0/CHANGELOG.md

Required Spec Kit Version

=1.2.1

Required Tools (optional)

- skj (>=0.1.0) - required; the CLI from the same repository and tag: pipx install "git+https://github.com/praveenlavu/spec-kit-jira@v0.1.0"
- git - required
- gh - optional; only to open PRs on GitHub

Number of Commands

13

Number of Hooks (optional)

2

Tags

jira, issue-tracking, hitl, workflow, governance

Key Features

  • Reads a Jira Cloud story and seeds a Definition-of-Done ledger from its acceptance criteria
  • Posts open questions and recorded decisions to the story once, never duplicated
  • Pushes the task list as Jira subtasks; every Jira or PR write is shown first and applies only the plan you approved
  • Ties each acceptance criterion to the test that proves it; a gate before merge reports gaps and drift
  • Optional strict mode and business rules read from Epics; closes the story only after the merge and a human yes
  • Python standard library only; the API token stays in your keychain

Testing Checklist

  • Extension installs successfully via download URL
  • All commands execute without errors
  • Documentation is complete and accurate
  • No security vulnerabilities identified
  • Tested on at least one real project

Submission Requirements

  • Valid extension.yml manifest included
  • README.md with installation and usage instructions
  • LICENSE file included
  • GitHub release created with version tag
  • All command files exist and are properly formatted
  • Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Environment: macOS (Apple silicon), Python 3.9, Spec Kit 1.2.4.dev0 (specify); GitHub-hosted Ubuntu CI on Python 3.9 and 3.13, with a contract job against Spec Kit 1.2.1 (the minimum) and the latest release. Both were green at the tagged commit (v0.1.0, 6286ae8).

Test project: a real Jira Cloud Free site (a team-managed project) and a private scratch GitHub repository.

Scenarios, all against the real site: setup and doctor; get and comments (100+ comments, pagination); dod seed and refresh with acceptance-criteria drift; decisions and questions (posted once, never duplicated); push of subtasks; the gate; strict mode (refusals and the success path); business rules on a real Epic chain; pr link; done with the ledger attachment; about 600 checks in all. The defects those checks found were fixed and re-tested.

Install: specify extension add jira-lifecycle --from https://github.com/praveenlavu/spec-kit-jira/archive/refs/tags/v0.1.0.zip on 2026-11-15 installs the extension with 13 commands, 2 hooks and 13 skills.

Commands: each of the 13 was run by a real agent (Claude Code) on a real story. pull, plan, tasks, implement, gate and review ran inside one real run of the jira-lifecycle workflow, from story to an open pull request (the workflow's own apply steps ran the Jira subtask push and opened the pull request, each after a human gate). The other seven (push and pr as previews, done to its refusal because the story was not merged, status, setup, stack and constitution) were run headless afterwards; they wrote only local files, and no Jira or GitHub write was made by them. A rejected gate left Jira unchanged, and a second and third run added no duplicate comment or subtask.

Not covered: company-managed projects, comment approval by a second Atlassian user (experimental), live 429/503/timeout/403 behaviour, the token store on Linux and Windows, and skj done after a real merge with human-validated decisions. These are listed in docs/unverified.md in the repository.

Security check before filing: no secrets or token shapes in the tree or history; no shell=True, eval or exec in the shipped code; HTTPS only with certificate checks on, and redirects refused so the Authorization header never leaves the site; the token is read from the OS keychain or a 0600 file and is not logged; the agent permission list denies every Jira or PR write and git push.

Example Usage

pipx install "git+https://github.com/praveenlavu/spec-kit-jira@v0.1.0"
skj setup --site your-site.atlassian.net --project PROJ
specify extension add jira-lifecycle --from https://github.com/praveenlavu/spec-kit-jira/archive/refs/tags/v0.1.0.zip
/speckit.jira-lifecycle.pull PROJ-123

Proposed Catalog Entry

{
  "jira-lifecycle": {
    "name": "Spec Kit lifecycle for Jira",
    "id": "jira-lifecycle",
    "description": "A Jira story to Done through Spec Kit, with a human sign-off before every Jira or PR write.",
    "author": "praveenlavu",
    "version": "0.1.0",
    "download_url": "https://github.com/praveenlavu/spec-kit-jira/archive/refs/tags/v0.1.0.zip",
    "sha256": "2ef9ca5ea40b3cc05b1043fc39dd01019615ad9d5766e46e5d7389d2e1159902",
    "repository": "https://github.com/praveenlavu/spec-kit-jira",
    "homepage": "https://github.com/praveenlavu/spec-kit-jira",
    "documentation": "https://github.com/praveenlavu/spec-kit-jira/blob/v0.1.0/README.md",
    "changelog": "https://github.com/praveenlavu/spec-kit-jira/blob/v0.1.0/CHANGELOG.md",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=1.2.1",
      "tools": [
        {"name": "skj", "version": ">=0.1.0", "required": true},
        {"name": "git", "required": true},
        {"name": "gh", "required": false}
      ]
    },
    "provides": {"commands": 13, "hooks": 2},
    "tags": ["jira", "issue-tracking", "hitl", "workflow", "governance"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-11-15T00:00:00Z",
    "updated_at": "2026-11-15T00:00:00Z"
  }
}

Additional Context

The skj command-line program (Python standard library only) ships in the same repository at the same version. The jira-lifecycle workflow is submitted to the workflow catalog by pull request, and a bundle that installs both will be submitted separately once both are listed. Other Jira entries exist in the catalog (jira, jira-mirror, jira-sync, maqa-jira); this one differs in being a human-gated lifecycle: every Jira or PR write is a preview, a gate and an apply; a Definition-of-Done ledger ties each acceptance criterion to a test; it fails closed; and it supports team-managed projects only in 0.1. Its sibling for Azure DevOps is ado.

Activity

  1. added
    triage-must-haveVerdict: high-value, important work for Spec Kit — do first
    on Nov 15, 2026
  2. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    cc @github/spec-kit-maintainers — new catalog submission for review.

  3. added a commit that references this issue on Nov 16, 2026
    696e0ba
  4. github-actions commented on Nov 16, 2026

    @github-actions
    Contributor

    Pull request created: #5438

    Generated by Add Community Extension from Issue Submission · copilot · gpt53codex · 34.5 AIC · ⌖ 0.718 AIC · ⊞ 28.5K

  5. added a commit that references this issue on Nov 16, 2026
    4a637b2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions