conduct-spike
SolidInteractively conduct a time-boxed spike — collaboratively reduce uncertainty through discussion mixed with agent-driven research (and small throwaway prototypes where a question is empirical), then record the outcome on the spike's work item. Use when a work item or brief poses open questions that must be resolved before planning or implementation can proceed with confidence.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- atomicinnovation
- Repository
- atomicinnovation/accelerator
- Created
- 6 months ago
- Last Updated
- today
- Language
- HTML
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
rig-spike
Run a time-boxed research spike to answer an open technical question or de-risk an approach BEFORE committing to implementation. Produces written findings + a recommendation (and optionally a throwaway prototype), not production code. Use when the team needs to evaluate feasibility, compare options, or reduce uncertainty before a feature is planned. Triggers on: 'spike', 'research spike', 'investigate', 'evaluate feasibility', 'de-risk', 'proof of concept', 'POC', 'compare options', 'can we', 'what would it take'.
running-a-spike
Answer an open technical question with a time-boxed throwaway experiment instead of arguing or over-building. Use when the team does not know whether an approach will work, which library to pick, or how much a change would cost.
spike
Use when the user wants to feel out an idea before committing to a real build — "spike this out", "try it", "is this even possible?", "compare A vs B". Throwaway experiments that decompose into 2-5 feasibility questions, build minimal observable prototypes, and return VALIDATED / PARTIAL / INVALIDATED verdicts. Disposable by design. Adapted from Hermes Agent / GSD.