Building Spike Tickets

A spike is a time-boxed investigation ticket whose goal is to reduce uncertainty before committing to a solution. It answers a specific technical question — it does not deliver functionality. When the spike is done, you close it and create follow-up stories based on what you learned.

Generate minimal Jira Spike tickets. Output in English, Jira Markdown, inside a code block.

When to Create a Spike

Create a spike when the team cannot estimate a story because something is unknown:

• Technology feasibility: "Can we integrate X with Y?"
• Architecture uncertainty: "Which of these two approaches should we take?"
• Performance unknowns: "Will this scale to N requests?"
• Third-party API exploration: "What does this API actually support?"
• Security or compliance questions: "How does the library handle auth?"

A spike is not needed when the team already knows how to do the work. If the answer is obvious, skip the spike and write the story directly.

Output Format