Agent skill · product strategy · github

create-technical-spike

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.

Why this skill is useful

Provides a structured template for conducting technical spikes that helps standardize decision-making processes in development.

What it needs

About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.

What this skill does

Create Technical Spike Document Create time-boxed technical spike documents for researching critical questions that must be answered before development can proceed. Each spike focuses on a specific technical decision with clear deliverables and timelines. Document Structure Create individual files in ${input:FolderPath docs/spikes} directory. Name each file using the pattern: [category]-[short-description]-spike.md (e.g., api-copilot-integration-spike.md, performance-realtime-audio-spike.md). Categories for Technical Spikes API Integration Third-party API capabilities and limitations Integration patterns and authentication Rate limits and performance characteristics Architecture & Design System architecture decisions Design pattern applicability Component interaction models Performance & Scalability Performance requirements and constraints Scalability bottlenecks and solutions Resource utilization patterns Platform & Infrastructure Platform capabilities and limitations Infrastructure requirements Deployment and hosting considerations Security & Compliance Security requirements and implementations Compliance constraints Authentication and authorization approaches User Experience User interaction patterns Accessibility requirements Interface design decisions File Naming Conventions Use descriptive, kebab-case names that indicate the category and specific unknown: API/Integration Examples: api-copilot-chat-integration-spike.md api-azure-speech-realtime-spike.md api-vscode-extension-capabilities-spike.md Performance Examples: performance-audio-processing-latency-spike.md performance-extension-host-limitations-spike.md performance-webrtc-reliability-spike.md Architecture Examples: architecture-voice-pipeline-design-spike.md architecture-state-management-spike.md architecture-error-handling-strategy-spike.md Best Practices for AI Agents 1. One Question Per Spike: Each document focuses on a single technical decision or research question 2. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills github/create-technical-spike

View the source on GitHub

Browse the @skills marketplace