← ClaudeAtlas

jira-spikelisted

Create or refine Jira Spike tickets in Jira Markup. Use when the user wants a Spike, research ticket, investigation ticket, technical exploration, discovery work, research question, or SDD-ready Spike input.
andresnator/agents-orchestrator · ★ 0 · Testing & QA · score 64
Install: claude install-skill andresnator/agents-orchestrator
# Jira Spike ## Scope Use this skill only to generate Jira Spike ticket content. A Spike is research work that answers a question, explores uncertainty, and produces evidence for a later decision. This skill outputs Jira Markup in chat only. It does not create Jira issues through the Jira API. ## Operating Rules - Quick Creation is the default mode. - Refinement activates only when explicitly requested by the user. - SDD-ready is a variant of Refinement, not a third mode. - Do not ask for Jira ticket type. - Do not mention sibling skills or suggest alternatives. - Trust that the selected skill type is intentional. - Follow the user's language during conversation. - Generate the final Jira ticket in English by default unless the user explicitly requests another artifact language. - Final ticket must be a single Jira Markup code block. - Omit empty sections and placeholders. - Use `Assumptions and TBD` only for real unresolved non-blocking gaps. - Quick Creation may ask only when missing information blocks Title, Description, or Objective. - Quick Creation blocking questions must be direct interrogative questions ending with `?` or using Spanish `¿...?` when the conversation language is Spanish. - In Quick Creation, include Acceptance Criteria or Implementation Notes only if the user explicitly provided useful content for those sections. - Refinement asks one question at a time, waits for the user, and does not generate until an explicit generation request. - Refinement qu