convert-to-spike

Create SPIKE cycle artifacts and recommend branch names from EXPLORING work.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/leuzeus/aidn --skill convert-to-spike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: convert-to-spike
Source: https://github.com/leuzeus/aidn/tree/main/tests/fixtures/repo-installed-core/.codex/skills/convert-to-spike
Command: npx skills add https://github.com/leuzeus/aidn --skill convert-to-spike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert ongoing EXPLORING effort into an official SPIKE cycle with dedicated branch recommendations, reducing friction and preserving exploration context.

Core Features & Use Cases

  • Create a new SPIKE cycle via cycle-create with brief.md and decisions.md captures.
  • Recommend branch naming spike/CXXX-<topic> and update current session to reference the new cycle.
  • Update snapshot, CURRENT-STATE, and provide hook-guided workflows for runtime continuity.

Quick Start

Convert an ongoing EXPLORING effort into a SPIKE cycle by following the steps in this skill.

Frequently Asked Questions about convert-to-spike

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

FAQPage Schema
How do I convert exploratory work into a formal SPIKE cycle?

To convert exploratory work into a SPIKE cycle, the skill automates artifact creation, updates the current session, and recommends a dedicated branch name once a relevance threshold is reached.

What is a SPIKE cycle in software branching workflows?

A SPIKE cycle formalizes exploratory work into a dedicated branch to preserve context and reduce friction. It captures outcomes in artifacts like brief.md and decisions.md.

When should I create a SPIKE branch instead of continuing normal exploration?

You should create a SPIKE branch when exploration effort hits a relevance threshold, measured by time spent or files touched, ensuring minimal disruption to the main workflow.

How do I document outcomes from a SPIKE cycle?

You document SPIKE cycle outcomes by updating CURRENT-STATE and creating spike artifacts. The runtime hook ensures project context faithfully reflects the adoption and captures results.

Does converting to a SPIKE cycle force changes to my current workflow?

Converting to a SPIKE cycle prefers recommendations over forced changes to ensure minimal disruption. It updates snapshots and provides hook-guided workflows for continuity.