create-spike

To convert a vague problem description into a structured GitHub issue, provide a single-sentence summary to trigger the spike workflow. The process conducts a deep codebase investigation and outputs a ready-to-file issue with full technical context.

A spike issue in software engineering is a structured ticket designed to explore and clarify complex feature ideas, bugs, or performance concerns. It maps architectural implications and data flows to define new work before implementation begins.

To investigate codebase implications for a complex feature idea, the spike workflow uses a principal-engineer-reviewer to map components and data flows. This deep investigation determines scope, labels, and risk while guiding the technical exploration.

You do not need a fully detailed problem statement to generate a spike issue. The workflow gathers the problem statement in a single pass and will ask one round of clarifying questions if needed before conducting the technical investigation.

Yes, you can use this spike workflow for codebases of any size. It is applicable to small and large repositories alike, helping to define new work or clarify complex architectural concerns regardless of the project scale.

The best way to triage high-level bugs into actionable development tasks is to generate a complete spike issue. This produces a stakeholder-friendly summary alongside a full technical investigation, enabling fast exploration and downstream implementation.