create-technical-spike

Create structured spike documents with frontmatter in docs/spikes.

Updated Apr 2, 2026

Search Tags:#planning #documentation #decision-making #technical-research #spike #engineering-process

Ready to run

npx skills add https://github.com/lucasgaldinos/my-skills --skill create-technical-spike-lucasgaldinos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-technical-spike
Source: https://github.com/lucasgaldinos/my-skills/tree/main/skills/create-technical-spike
Command: npx skills add https://github.com/lucasgaldinos/my-skills --skill create-technical-spike-lucasgaldinos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Create Technical Spike Document skill standardizes how teams scope and document critical technical uncertainties, ensuring research outputs lead to concrete decisions and actionable next steps.

Core Features & Use Cases

Structured spike templates for clear research questions, plans, success criteria, and findings.
Automated document creation in the docs/spikes directory with consistent naming and frontmatter.
Guided content sections including summary, investigation plan, and decision proposals for faster stakeholder alignment.

Quick Start

Provide a spike topic and timebox, then run the spike generator to create a new spike document in docs/spikes with the recommended structure.

Frequently Asked Questions about create-technical-spike

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document a technical spike for engineering research?▼

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.

What is a time-boxed technical spike in software engineering?▼

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.

How do I structure technical research findings for 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.

Can I include scripts and references when scoping a technical decision document?▼

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.

What is the best way to track technical unknowns during project scoping?▼

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.

Does this technical spike generator enforce a specific directory structure?▼

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.