evolutionary-spike

Runs parallel throwaway prototype spikes to resolve design and feasibility questions empirically.

2|2|Updated Jun 28, 2015
One-click install
npx skills add https://github.com/camercu/dotfiles --skill evolutionary-spike-camercu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evolutionary-spike
Source: https://github.com/camercu/dotfiles/tree/main/common/.config/agents/skills/evolutionary-spike
Command: npx skills add https://github.com/camercu/dotfiles --skill evolutionary-spike-camercu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When the right shape or viability of a design is genuinely unknown and cannot be settled by reasoning alone, this Skill resolves the question empirically by building and comparing multiple throwaway prototypes instead of guessing. ## Core Features & Use Cases - Parallel spike tournaments: Dispatches clean-room, informed, and directed agents to build competing prototypes in isolated git worktrees, then eliminates dominated candidates while capturing lessons. - Adaptive tiers: Scales from a light single-round spike (2-4 variants) to a heavy multi-round tournament with independent reviewers and capstone synthesis. - Decision artifacts: Produces a findings document on a spike branch plus a standalone ADR on main with a cost-benefit verdict, including the valid outcome of not building at all. - Use Case: You are unsure which interface shape best fits a new subsystem. Run a spike tournament where three agents prototype different mechanisms, an independent reviewer verifies honesty of claims, and the result lands as an ADR recommending one design. ## Quick Start Ask the agent to spike three approaches to the design problem and compare them to pick a winner.

Frequently Asked Questions about evolutionary-spike

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

FAQPage Schema
How do I compare multiple design approaches before committing to one?▼

Run an evolutionary spike: dispatch parallel agents to build throwaway prototypes of each approach in isolated git worktrees, review them independently, eliminate dominated candidates, and converge on a winner recorded in an ADR.

What is a spike tournament in software design?▼

A spike tournament is a multi-round process where clean-room and informed agents build competing prototypes, independent reviewers verify claims, and weaker designs are eliminated while their lessons are captured, ending in a synthesized decision.

When should I use a spike instead of going straight to TDD?▼

Use a spike when the right shape or viability is genuinely unknown and must be built to know. If one approach is already obvious, skip spiking and go directly to planning or test-driven development.

Does spike prototype code get merged into the main branch?▼

No. Spike code and findings stay on a dedicated spike branch that is never merged or pushed. Only the ADR lands on main, and a winning design is rewritten fresh to production quality rather than cherry-picked.

Why use git worktrees instead of copying the repo for prototypes?▼

Worktrees share the repository object store, so they cost megabytes instead of gigabytes and keep arm commits durable in the repo's own .git. Copies in /tmp are not durable and can be reaped, losing all spike work.

What are the limitations of the light spike tier?▼

The light tier allows self-review, which is polluted by author bias and must be disclosed with reduced confidence. Escalate to a heavy tournament with independent reviewers when spikes disagree or the decision is costly or irreversible.