One-click install
npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-spike-mcampbellr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-spike
Source: https://github.com/mcampbellr/.dotfiles/tree/main/claude/.claude/skills/gsd-spike
Command: npx skills add https://github.com/mcampbellr/.dotfiles --skill gsd-spike-mcampbellr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps validate and explore ideas by building focused experiments, assessing feasibility, and producing knowledge for future development.

Core Features & Use Cases

  • Idea Mode: Describe an idea to spike, and the Skill will guide through the experiential exploration process.
  • Frontier Mode: Analyze existing spike landscape and propose integration and frontier spikes.
  • Integration with GSD: Spikes are integrated with GSD commit patterns, state tracking, and handoff workflows.

Quick Start

To spike an idea, use the command: gsd-spike [idea to validate].

Frequently Asked Questions about gsd-spike

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

FAQPage Schema
What is experiential spiking in software development?

Experiential spiking is a rapid prototyping technique used to validate ideas, assess feasibility, and produce knowledge for future development by building focused experiments.

How do I validate an idea or product design through rapid prototyping?

You can validate an idea by using the Idea Mode command, which guides you through the experiential exploration process to assess feasibility and generate development knowledge.

Can I analyze existing experiments to propose new integration spikes?

Yes, Frontier Mode analyzes your existing spike landscape to propose new integration and frontier spikes, helping you map out future rapid prototyping and validation workflows.

Does this spiking approach work with commit patterns and state tracking?

Yes, spikes are fully integrated with Getting Stuff Done (GSD) commit patterns, state tracking, and handoff workflows to ensure experiments are documented and transitioned smoothly.

When should I use a spike workflow for feasibility assessment?

You should use a spike workflow when you need to validate a software development or product design idea, requiring rapid prototyping to assess technical feasibility before full implementation.

Why does my rapid prototyping workflow need state tracking?

State tracking is needed to maintain context during feasibility assessment, ensuring that knowledge produced from experiential spiking is captured and integrated with your commit patterns and handoff workflows.