Create technical spike

Create a focused technical spike markdown file that frames one unresolved decision, defines time-boxed research, captures evidence, and ends with an actionable recommendation.

When to invoke

• "Create a technical spike document."
• "Write a spike for this API integration decision."
• "Plan research before we implement this architecture."
• "Document a proof of concept for this risky feature."
• "Create a time-boxed investigation for performance or security options."

Inputs

Use $ARGUMENTS for spike title, category, owner, timebox, priority, output folder, and any known context. If the folder is not supplied, default to docs/spikes. If values are missing, use placeholders in the document and call them out in the result.

File and frontmatter rules