Repository navigation
Add jira-lifecycle to community workflow catalog - #5434
praveenlavu wants to merge 2 commits into
Conversation
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>
There was a problem hiding this comment.
🟡 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_attimestamp.
| 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": { |
There was a problem hiding this comment.
Added the Jira row to the Available workflows table in docs/community/workflows.md (6fe78f0), with the pinned v0.1.0 link and version.
Adds the row for the new catalog entry to the Available workflows table, as the review asked. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
🔵 Needs a closer look
Offline review cannot verify the third-party v0.1.0 release URL, checksum, repository/tag existence, or matching workflow metadata, so maintainer confirmation against the published release is needed.
Review effort: Max (dynamic)
|
Please address Copilot feedback and resolve conflicts |

Description
Adds the
jira-lifecycleworkflow (v0.1.0) toworkflows/catalog.community.json, following Publishing workflows (workflow entries are a pull request; there is no workflow-definition issue form). The entry sits afterado-lifecycle(alphabetical) and the catalog'supdated_atis bumped. Catalog-only change: one entry, no code touched.v0.1.0, GitHub release)https://github.com/raw/praveenlavu/spec-kit-jira/v0.1.0/workflows/jira-lifecycle/workflow.yml799d2b2309a6cd8b53bdb27ecb57b8be3c8bdccc7139d37c62ac1bdf409edf1aThe 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
donecommand, outside the workflow.Required integrations: any coding agent that Spec Kit can run headless (
claude,copilot,gemini,opencode,alquimiaare 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 andgit 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
skjCLI (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 plainresumereads 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.
specify workflow add https://github.com/raw/praveenlavu/spec-kit-jira/v0.1.0/workflows/jira-lifecycle/workflow.ymlinstallsjira-lifecyclev0.1.0 in a freshspecify initproject andspecify workflow listshows it.AI Disclosure
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