Skip to content
TilloTech Docs

How to resolve a spike ticket

Use /resolve-spike-ticket when you have an existing Jira spike key or URL. Use /create-spike-ticket when you need a new spike.

The resolver:

  1. Reads the existing Jira issue before it drafts changes.
  2. Validates the canonical key, Jira project, and spike issue type.
  3. Asks focused questions for the remaining unknowns.
  4. Preserves content that you did not ask to change.
  5. Shows the complete Jira update draft.
  6. Waits for your explicit confirmation.
  7. Updates Jira only.
  8. Applies a transition to Jira's done status category when all unknowns are resolved.

The resolver stops when the key does not identify a valid spike. It also stops when Jira does not provide a transition to a done status category. It does not create a duplicate parent or subtask, and it does not write to Notion.

After the spike reaches a done status, return to its originating workflow: /create-project, /create-enhancement-ticket, /create-tsd-section, or /create-implementation-plan.