create-technical-spike

To document a technical spike, you define a specific research question, timebox, investigation plan, and success criteria. This skill generates a structured markdown file in the docs/spikes directory with frontmatter to standardize the process.

A time-boxed technical spike is a focused research period used to investigate critical technical unknowns. It involves defining a question, planning the investigation, and documenting findings to enable concrete decision-making and stakeholder alignment.

You structure technical research findings by creating a document with a summary, investigation plan, and decision proposals. This ensures research outputs lead to actionable next steps and faster alignment among stakeholders.

Yes, you can include optional references, scripts, and assets when scoping a technical decision document. The structured template supports adding these elements alongside the core findings and investigation plan.

The best way to track technical unknowns is using a standardized spike document with defined frontmatter. This enforces a consistent structure for capturing research questions, success criteria, and findings in the docs/spikes directory.

Yes, the technical spike generator enforces a specific directory structure by automatically creating documents in the docs/spikes directory. It applies consistent naming conventions and requires frontmatter-based entries for organization.