Create a new spike investigation.

Initializes a spike with a problem statement, creates the directory structure, and generates the meta-design template for Phase 0.

Args: name: Filesystem-safe name (alphanumeric, hyphens, underscores, max 64 chars) problem_statement: The problem this spike investigates

List all spike investigations with summary information.

Permanently delete a spike investigation.

Args: name: Spike name to delete confirm: Must be True to confirm deletion

Archive a spike investigation (move to archive directory).

Args: name: Spike name to archive

Approve meta-design and advance spike from Phase 0 to Phase 1.

This is a gate: the spike cannot proceed to divergent exploration until the problem framing is approved.

Args: name: Spike name

Record a confidence rating for the spike.

All ratings are 0-100. Tracks confidence evolution over time.

Args: name: Spike name problem_understanding: How well is the problem understood (0-100) success_criteria_clarity: How clear are the success criteria (0-100) exploration_completeness: How complete is the exploration (0-100) solving_right_problem: Confidence we're solving the right problem (0-100) reason: Optional reason for this assessment

Register a new exploration branch for a spike.

Branches represent distinct approaches to solving the problem. Can be added during Phase 0 (planning) or Phase 1 (divergent).

Args: name: Spike name branch_name: Filesystem-safe branch name description: What this branch explores

Mark a branch as explored and record findings.

The findings markdown replaces the branch template content. When enough branches are explored (>=3), the spike automatically advances to Phase 2 (adversarial).

Args: name: Spike name branch_name: Branch to mark as explored findings_md: Markdown content with exploration findings

Mark a branch as a dead end and document why.

Dead-end branches are excluded from synthesis but their documentation is preserved for future reference.

Args: name: Spike name branch_name: Branch to mark as dead end reason: Why this branch was abandoned salvageable: Any insights salvageable from this branch

Add adversarial challenge to a branch.

Challenges document failure modes, hidden assumptions, and edge cases. When all explored branches are challenged, the spike automatically advances to Phase 3 (synthesis).

Args: name: Spike name branch_name: Branch to challenge (must be in EXPLORED status) challenge_md: Markdown content with adversarial challenge

Create synthesis document comparing all explored branches.

Args: name: Spike name synthesis_md: Markdown content with synthesis analysis

Generate an Architecture Decision Record from spike artifacts.

Builds alternatives from challenged branches and renders the ADR template.

Args: name: Spike name title: ADR title context_text: Context/background for the decision decision: The decision being documented

Approve the ADR and mark the spike as completed.

This is the final gate. The spike transitions to COMPLETED status.

Args: name: Spike name

Get the current state of a spike investigation.

Args: name: Spike name

Create a checkpoint of the current spike state.

Checkpoints allow rolling back to a previous state if exploration goes down an unproductive path.

Args: name: Spike name label: Human-readable checkpoint label

Rollback spike to a previous checkpoint.

Restores the full state from the checkpoint snapshot.

Args: name: Spike name checkpoint_id: Checkpoint ID to restore from