spike-review

Summarize spike results and create follow-up tickets from implementation steps.

24|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/yves-s/just-ship --skill spike-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spike-review
Source: https://github.com/yves-s/just-ship/tree/main/skills/spike-review
Command: npx skills add https://github.com/yves-s/just-ship --skill spike-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It streamlines the review of completed spike tickets by locating the spike document, summarizing its outcomes, generating follow‑up tickets from implementation steps, and closing the original spike.

Core Features & Use Cases

  • Document Retrieval: Automatically finds the relevant spike markdown in the repository.
  • Summary Generation: Produces a concise overview with key findings and recommendations.
  • Follow‑Up Ticket Drafting: Converts each implementation step into a ready‑to‑create ticket draft.
  • Automated or Interactive Closure: Supports both hands‑off (--auto) execution and guided operator approval.
  • Use Case: After a research spike is finished, run this skill to turn the research into actionable development tickets and close the spike in a single flow.

Quick Start

Run /spike-review T-472 (or add --auto for full automation) to review the spike, create follow‑up tickets, and close the spike.

Frequently Asked Questions about spike-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn spike findings into actionable follow-up tickets and close the original spike?

To turn spike findings into follow-up tickets, the skill reviews your spike document, generates a concise summary of outcomes, drafts ready-to-create tickets from implementation steps, and closes the original spike in a single flow.

Can I automate spike ticket closure and follow-up ticket creation in a pipeline?

Yes, you can automate spike ticket closure by running the skill with the `--auto` flag for hands-off pipeline execution, or use interactive mode for guided operator approval before creating tickets and closing the spike.

What do I need to generate follow-up tickets from a completed spike document?

You need a completed spike ticket with an existing spike markdown document in the repository, board API access for ticket creation, and optional pipeline configuration for automated execution.

How does the spike review process summarize research outcomes for the board?

The spike review process automatically retrieves the relevant spike markdown, produces a concise overview of key findings and recommendations, and converts each implementation step into a ready-to-create ticket draft.

What is the best way to close a spike ticket after research is finished?

The best way to close a finished spike ticket is to run the spike review command with the ticket ID, which summarizes the research, creates follow-up tickets from implementation steps, and closes the spike.

Does the follow-up ticket generation work without manual intervention?

Yes, follow-up ticket generation works without manual intervention when using the `--auto` flag, allowing fully automated execution to draft tickets and close the spike without operator approval.