Skip to content

Add jira-lifecycle to community workflow catalog - #5434

Open
praveenlavu wants to merge 1 commit into
github:mainfrom
praveenlavu:workflow/jira-lifecycle-catalog
Open

praveenlavu wants to merge 1 commit into
github:mainfrom
praveenlavu:workflow/jira-lifecycle-catalog

Conversation

@praveenlavu

@praveenlavu praveenlavu commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

Description

Adds the jira-lifecycle workflow (v0.1.0) to workflows/catalog.community.json, following Publishing workflows (workflow entries are a pull request; there is no workflow-definition issue form). The entry sits after ado-lifecycle (alphabetical) and the catalog's updated_at is bumped. Catalog-only change: one entry, no code touched.

  • Workflow ID: jira-lifecycle Name: Spec Kit lifecycle for Jira Version: 0.1.0 License: MIT
  • Repository: https://github.com/praveenlavu/spec-kit-jira (tag v0.1.0, GitHub release)
  • Pinned URL: https://raw.githubusercontent.com/praveenlavu/spec-kit-jira/v0.1.0/workflows/jira-lifecycle/workflow.yml
  • sha256 of that file: 799d2b2309a6cd8b53bdb27ecb57b8be3c8bdccc7139d37c62ac1bdf409edf1a
  • Related submissions: extension issue [Extension]: Add jira-lifecycle #5433; a bundle that installs both will follow once both are listed.

The workflow takes a Jira Cloud story to an open pull request (spec, plan, tasks, push, implement, gate, review, PR). Every Jira or PR change is a shell preview that writes a plan file, a gate that shows that file, and a shell apply that refuses unless the plan is unchanged. The story is closed only after the merge, by the extension's done command, outside the workflow.

Required integrations: any coding agent that Spec Kit can run headless (claude, copilot, gemini, opencode, alquimia are listed). Spec Kit starts the agent without a terminal, so with Claude Code the agent needs a permission list; the repository ships a tested one (docs/claude-permissions.json) that allows the read and local-write commands and denies every Jira or PR write and git push. Without it the check after each agent step stops the run instead of carrying on with nothing done.

Side effects: writes to Jira (comments, subtasks, the ledger attachment) and opens a pull request happen only in the workflow's own apply steps, each after a human gate. The agent steps make local commits to the current branch. Requires the skj CLI (Python standard library only) from the same repository and tag.

Gate and resume: gates pause with no terminal and are answered with specify workflow resume <run> --input issue_number=<n> plus the verdict input. If the plan changed after it was approved, the apply step refuses and a new run is needed. Known Spec Kit behaviour: a plain resume reads the run's saved inputs without re-checking them; this is documented in the workflow header.

Testing

Run on 2026-11, macOS, Spec Kit 1.2.4.dev0, Claude Code as the agent, against a real Jira Cloud Free site (team-managed project) and a private scratch GitHub repository.

  • Install from the pinned URL, run today: specify workflow add https://raw.githubusercontent.com/praveenlavu/spec-kit-jira/v0.1.0/workflows/jira-lifecycle/workflow.yml installs jira-lifecycle v0.1.0 in a fresh specify init project and specify workflow list shows it.
  • Live end-to-end run on a real story: spec, questions, plan, tasks, 11 subtasks pushed to Jira, implement (test-first code), decisions posted, review, and a pull request opened on the scratch repository.
  • Rejection path: a rejected gate left Jira unchanged. A second and a third run on the same story added no duplicate comment or subtask.
  • Running it found six problems (headless permissions, a missing check after each agent step, a stale ledger at review gates, and others); all are fixed in 0.1.0 and covered by tests.
  • Hosted CI on the tagged commit is green: tests on Python 3.9 and 3.13, and a contract job against Spec Kit 1.2.1 (the minimum) and the latest release.
  • Not verified: approvals by comment with a second Atlassian user (experimental), company-managed Jira projects, live 429/503/timeout behaviour, Windows and Linux token storage.
  • Catalog-only change: the Spec Kit test suite was not run (no code is touched); the JSON round-trips unchanged and keys are in order.

AI Disclosure

  • I did not use AI assistance for this contribution
  • I did use AI assistance (disclosure below)

AI disclosure: Tool: Claude Code (Anthropic's CLI/desktop app). Model: Claude Sonnet 5.5 for this pull request, the catalog entry and this text; the workflow and its CLI were built over several weeks with Claude Code. Settings/mode: default settings, human-supervised (not autonomous): the owner approved the submission. Extent: the catalog entry, this description and the checks described above were produced with AI assistance; the workflow and the CLI it calls were also written with it.

🤖 Generated with Claude Code

Adds the jira-lifecycle workflow (v0.1.0) from praveenlavu/spec-kit-jira,
pinned to the v0.1.0 tag with the sha256 of workflow.yml. Catalog-only change.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@praveenlavu
praveenlavu requested a review from mnriem as a code owner November 15, 2026 21:33
Copilot AI dynamic review requested due to automatic review settings November 15, 2026 21:33

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The catalog change leaves the community workflows documentation missing the new pinned Jira workflow entry, so the repository’s catalog and documentation are inconsistent.

1 open issue
What changed in this PR

Adds the version-pinned jira-lifecycle v0.1.0 workflow to Spec Kit’s community catalog for discoverability and installation.

Changes:

  • Registers workflow metadata, repository links, requirements, integrations, tags, and SHA-256 digest.
  • Places the entry alphabetically after ado-lifecycle.
  • Updates the catalog’s updated_at timestamp.
File Description
workflows/​catalog.community.json Registers the pinned jira-lifecycle v0.1.0 community workflow and refreshes the catalog metadata.

Review effort: Lite (dynamic)

"created_at": "2026-11-08T00:00:00Z",
"updated_at": "2026-11-09T00:00:00Z"
},
"jira-lifecycle": {
@mnriem mnriem added the triage-must-have Verdict: high-value, important work for Spec Kit — do first label Nov 15, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage-must-have Verdict: high-value, important work for Spec Kit — do first

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants