Run a time-boxed technical spike to produce a findings document and recommendation.
npx skills add https://github.com/xiduzo/wtf --skill wtf-spike
Please help me install this Agent Skill. Skill: wtf.spike Source: https://github.com/xiduzo/wtf/tree/main/skills/wtf.spike Command: npx skills add https://github.com/xiduzo/wtf --skill wtf-spike
Spike addresses the need to investigate a technical unknown before committing to an approach, turning uncertainty into a concrete finding and a recommendation that informs whether to write an epic or a task.
Run a time-boxed technical spike to investigate a defined unknown and produce a findings document with a concrete recommendation.
High-intent search queries and answers about installing and using this skill.
A technical spike is a time-boxed investigation used to solve a technical unknown before committing to an architecture or tooling approach. It yields a concrete findings document and a recommendation to inform whether to write an epic or a task.
Run a time-boxed spike with a clear scope and duration to investigate the technical unknown. This produces a findings document and a concrete recommendation that feeds directly into writing your epic or task.
You need a spike when teams face uncertainty around architecture, approach, or tooling before committing to an epic or task. The spike prevents drift by time-boxing the investigation and delivering a concrete recommendation.
The best way to prevent scope drift is to enforce a time-boxed spike with a predefined scope and duration. This structure ensures the investigation yields a concrete finding and recommendation without unbounded research.
A spike maintains traceability by linking the research findings and concrete recommendations directly to decisions in the issue and PR workflow. This connects the technical investigation to the resulting epic or task.
A technical spike must deliver a findings document and a concrete recommendation. These outputs feed directly into planning, allowing teams to confidently write an epic or task based on the resolved unknown.
GabeujinGenerates time-boxed technical spike documents for researching critical development decisions before implementation.
raydocsGenerate epics and tasks in the .flow/ directory from feature descriptions.
aroidoAutomates feature implementation workflow from issue tracking to pull request merging.
oscardlfrConducts technical research using WebSearch, Context7, and codebase analysis.
