Run throwaway experiments and produce a README with a formal verdict.
npx skills add https://github.com/StarryCod/cogitum --skill spike-starrycod
Please help me install this Agent Skill. Skill: spike Source: https://github.com/StarryCod/cogitum/tree/main/cogitum/data/skills/software-development/spike Command: npx skills add https://github.com/StarryCod/cogitum --skill spike-starrycod
Quick, throwaway experiments to validate ideas before committing to a full build, helping teams avoid wasted effort.
Define a 2-5 spike questions, run lightweight experiments, and capture a verdict for decision-making.
High-intent search queries and answers about installing and using this skill.
A spike is a lightweight, throwaway experiment used to validate ideas and test feasibility before committing to a full software build. You need a spike when exploring technical approaches or making informed planning decisions to avoid wasted effort.
You validate software feasibility by defining 2-5 spike questions and running disposable experiments. This structured workflow decomposes the problem, researches options, builds prototypes, and produces a formal verdict for decision-making.
Yes, you can run a spike experiment for idea validation entirely standalone. It requires no external dependencies or components, allowing you to quickly test feasibility and capture a verdict without complex setup.
The best way to document feasibility experiment results is by producing a README with a formal verdict. It enforces clear Given/When/Then framing to capture structured outcomes for informed planning decisions.
Throwaway experiments prevent wasted effort by validating ideas quickly before full development. Unlike a committed prototype, a spike focuses on answering specific feasibility questions and delivering a verdict, not producing production code.
You should not use a spike when you need production-ready code or long-term maintenance. Spikes are disposable experiments designed for quick feasibility exploration and idea validation, not for delivering final software components.
JamesFincherDecompose proposals into feasibility questions and run disposable implementation spikes.
servitolaCoordinate spike experiments to validate ideas and issue verdicts.
deerawanRoute user intent to the appropriate ideation or capture workflow.
davpatel605-beepValidate uncertain software ideas through disposable experiments and evidence-based verdicts.
