jira-to-speckit
Jira to Speckit
Use this skill when a Jira ticket is the source of truth for a new feature, task, or change request and a caller needs it turned into a Speckit-ready brief.
This skill is a pure Jira reader, not an orchestrator: it fetches one Jira issue, compacts it
under strict size budgets, optionally persists a full-fidelity snapshot of the ticket to a file the
caller names, and returns a structured brief plus a Jira-key-based feature name. It never invokes
speckit.specify or any other Speckit/Spec Kit command, never runs clarification or
review loops, never performs git operations, and never tracks an execution report — all of that is
owned by the caller (speckit-auto's shared intake reference and its provider
stage-01-preflight-intake.md files).
Portability note: allowed-tools uses GitHub Copilot-style names (bash view create). Claude Code
and OpenCode expose the same capabilities under their own names (Bash, Read, Write). Hermes
Agent exposes them as terminal, read_file, write_file. The workflow below is identical on
all four hosts.