Run time-boxed technical investigations and produce evidence-based findings artifacts.
npx skills add https://github.com/softwaresalt/csv-managed --skill spike-softwaresalt
Please help me install this Agent Skill. Skill: Spike Source: https://github.com/softwaresalt/csv-managed/tree/main/.github/skills/spike Command: npx skills add https://github.com/softwaresalt/csv-managed --skill spike-softwaresalt
This Skill helps you answer a specific technical uncertainty by running a time-boxed investigation and producing grounded findings you can act on.
Use the Spike skill to investigate the feasibility of your chosen technical question within a 4h time-box and generate a long-lived findings artifact linked for next workflow steps.
High-intent search queries and answers about installing and using this skill.
A technical spike is a time-boxed investigation applied to pre-implementation uncertainty such as technology selection, performance measurement, or migration path comparison. It evaluates a feasibility hypothesis through prototyping or benchmarking to produce evidence-based findings.
Execute a time-boxed investigation to answer a specific technical question using code reading, prototyping, or benchmarking. This feasibility study evaluates your hypothesis within a defined duration and generates a findings artifact with a clear recommendation.
Yes, you can evaluate technology selection and prototype performance within a defined time-box. The investigation applies to pre-implementation uncertainty by measuring performance and comparing migration paths to produce grounded, actionable findings.
The best way to document a benchmarking study is to produce an evidence-based findings artifact. This artifact captures the goal, approach, evidence, recommendation to proceed or pivot, confidence level, and optional promotion to planning or learnings workflows.
You promote feasibility study findings by using the actionable promotion workflow. This optionally converts the evidence-based recommendation into planning items, queue work, institutional learnings, and creates backlog items when supported.
You should not use a time-boxed investigation when pre-implementation uncertainty is absent. If the technical question is already answered or requires no technology selection, performance measurement, or migration path comparison, a spike investigation is unnecessary.
paulinghamCoordinate time-boxed technical research and output a findings document with a recommendation.
aslaiiReview backlog items and promote or remove them into active milestones.
WarrenZhu050413List, view, add, and update TODOs in Markdown files by project.
product-on-purposeDocument time-boxed spike results with findings and recommendations.
