Run a time-boxed spike workflow with research, prototyping, and evaluation phases.
npx skills add https://github.com/phuthuycoding/moicle --skill spike-phuthuycoding
Please help me install this Agent Skill. Skill: spike Source: https://github.com/phuthuycoding/moicle/tree/main/assets/skills/spike Command: npx skills add https://github.com/phuthuycoding/moicle --skill spike-phuthuycoding
Spike/Research workflow provides a structured, time-boxed approach to exploring unknowns before committing to implementation, reducing risk and guiding decision-making early.
To begin a spike, create a new spike doc, define a specific research question within a timebox (2–7 days), identify relevant architecture docs, log findings as you go, and conclude with a recommended path and required artifacts (ADR/decision record).
High-intent search queries and answers about installing and using this skill.
A timeboxed spike workflow is a structured approach to exploring technical unknowns before committing to implementation, reducing risk by guiding decision-making early through defined research, prototyping, and evaluation phases.
To create an architecture decision record after a proof of concept, conclude your timeboxed research by logging findings and outputting a recommended path with required artifacts like an ADR to inform project direction.
You need to use a spike for validating technical assumptions when you must prototype proof-of-concepts and de-risk unknowns before full-scale development, typically within a defined 2 to 7 day timebox.
The best way to structure a spike investigation across cross-stack contexts is to enforce architecture read-throughs, define specific research questions within a timebox, and log findings continuously to produce decision records.
A key limitation of timeboxed research is the strict 2 to 7 day boundary, meaning complex architecture exploration may require multiple sequential spikes rather than a single extended evaluation phase to thoroughly resolve unknowns.
edwardmonteiroCreates structured tech-spike charters with evaluation criteria and work plans.
crgarcia12Create and manage Architecture Decision Records for technical decisions.
t0dorakisCreate and manage Architecture Decision Records using established templates.
SQDR2Explore codebases and surface questions to shape OpenSpec requirements.
