Runs throwaway experiments to validate feasibility of ideas before committing.
npx skills add https://github.com/Dq666dinger/my-hermes --skill spike-dq666dinger
Please help me install this Agent Skill. Skill: spike Source: https://github.com/Dq666dinger/my-hermes/tree/main/skills/software-development/spike Command: npx skills add https://github.com/Dq666dinger/my-hermes --skill spike-dq666dinger
Feasibility spikes enable teams to rapidly validate ideas before committing to full development, reducing risk and wasted effort.
Create a new spike directory under spikes/NNN-descriptive-name, add a README.md and a SKILL.md documenting the spike's question, approach, and verdict.
High-intent search queries and answers about installing and using this skill.
A feasibility spike is a lightweight, throwaway experiment used to validate a single assumption before committing to full development, reducing risk and wasted effort on early-stage product concepts.
Create a standalone directory under spikes/NNN-descriptive-name, document the question and approach in a README.md and SKILL.md, run the experiment, and capture the final VERDICT to validate your architecture concept.
Use a feasibility spike when you need to isolate and test a single assumption for early-stage product concepts, research experiments, or process design before committing resources to build the full feature.
No dependencies are required to run a feasibility spike, though you can include optional scripts, references, and assets within the standalone spike directory to support your experiment.
The best way to structure a throwaway experiment is using a consistent standalone directory format with a README and VERDICT flow, ensuring you capture the question, approach, and results repeatably.
Feasibility spikes need a standalone directory structure to isolate the throwaway experiment from the main codebase, keeping the lightweight validation cleanly separated until a VERDICT is reached.
pe-menezesStructure project hypotheses across strategic, user, and business dimensions.
MichaelSolatiGuide pre-production game teams through an 8-phase vertical slice workflow with verdict reporting.
servitolaCoordinate spike experiments to validate ideas and issue verdicts.
tranhieuttPlans and executes throwaway proof-of-concept projects with structured reporting.
