create-technical-spike
installsforks
How to install create-technical-spike?
github/awesome-copilot/create-technical-spike
$npx -y skills add github/awesome-copilot --skill create-technical-spikeCreate time-boxed technical spike documents for researching and resolving critical development decisions before implementation.
SKILL.md
| 1 | # Create Technical Spike Document |
| 2 | |
| 3 | 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. |
| 4 | |
| 5 | ## Document Structure |
| 6 | |
| 7 | 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`). |
| 8 | |
| 9 | ```md |
| 10 | --- |
| 11 | title: "${input:SpikeTitle}" |
| 12 | category: "${input:Category|Technical}" |
| 13 | status: "🔴 Not Started" |
| 14 | priority: "${input:Priority|High}" |
| 15 | timebox: "${input:Timebox|1 week}" |
| 16 | created: [YYYY-MM-DD] |
| 17 | updated: [YYYY-MM-DD] |
| 18 | owner: "${input:Owner}" |
| 19 | tags: ["technical-spike", "${input:Category|technical}", "research"] |
| 20 | --- |
| 21 | |
| 22 | # ${input:SpikeTitle} |
| 23 | |
| 24 | ## Summary |
| 25 | |
| 26 | **Spike Objective:** [Clear, specific question or decision that needs resolution] |
| 27 | |
| 28 | **Why This Matters:** [Impact on development/architecture decisions] |
| 29 | |
| 30 | **Timebox:** [How much time allocated to this spike] |
| 31 | |
| 32 | **Decision Deadline:** [When this must be resolved to avoid blocking development] |
| 33 | |
| 34 | ## Research Question(s) |
| 35 | |
| 36 | **Primary Question:** [Main technical question that needs answering] |
| 37 | |
| 38 | **Secondary Questions:** |
| 39 | |
| 40 | - [Related question 1] |
| 41 | - [Related question 2] |
| 42 | - [Related question 3] |
| 43 | |
| 44 | ## Investigation Plan |
| 45 | |
| 46 | ### Research Tasks |
| 47 | |
| 48 | - [ ] [Specific research task 1] |
| 49 | - [ ] [Specific research task 2] |
| 50 | - [ ] [Specific research task 3] |
| 51 | - [ ] [Create proof of concept/prototype] |
| 52 | - [ ] [Document findings and recommendations] |
| 53 | |
| 54 | ### Success Criteria |
| 55 | |
| 56 | **This spike is complete when:** |
| 57 | |
| 58 | - [ ] [Specific criteria 1] |
| 59 | - [ ] [Specific criteria 2] |
| 60 | - [ ] [Clear recommendation documented] |
| 61 | - [ ] [Proof of concept completed (if applicable)] |
| 62 | |
| 63 | ## Technical Context |
| 64 | |
| 65 | **Related Components:** [List system components affected by this decision] |
| 66 | |
| 67 | **Dependencies:** [What other spikes or decisions depend on resolving this] |
| 68 | |
| 69 | **Constraints:** [Known limitations or requirements that affect the solution] |
| 70 | |
| 71 | ## Research Findings |
| 72 | |
| 73 | ### Investigation Results |
| 74 | |
| 75 | [Document research findings, test results, and evidence gathered] |
| 76 | |
| 77 | ### Prototype/Testing Notes |
| 78 | |
| 79 | [Results from any prototypes, spikes, or technical experiments] |
| 80 | |
| 81 | ### External Resources |
| 82 | |
| 83 | - [Link to relevant documentation] |
| 84 | - [Link to API references] |
| 85 | - [Link to community discussions] |
| 86 | - [Link to examples/tutorials] |
| 87 | |
| 88 | ## Decision |
| 89 | |
| 90 | ### Recommendation |
| 91 | |
| 92 | [Clear recommendation based on research findings] |
| 93 | |
| 94 | ### Rationale |
| 95 | |
| 96 | [Why this approach was chosen over alternatives] |
| 97 | |
| 98 | ### Implementation Notes |
| 99 | |
| 100 | [Key considerations for implementation] |
| 101 | |
| 102 | ### Follow-up Actions |
| 103 | |
| 104 | - [ ] [Action item 1] |
| 105 | - [ ] [Action item 2] |
| 106 | - [ ] [Update architecture documents] |
| 107 | - [ ] [Create implementation tasks] |
| 108 | |
| 109 | ## Status History |
| 110 | |
| 111 | | Date | Status | Notes | |
| 112 | | ------ | -------------- | -------------------------- | |
| 113 | | [Date] | 🔴 Not Started | Spike created and scoped | |
| 114 | | [Date] | 🟡 In Progress | Research commenced | |
| 115 | | [Date] | 🟢 Complete | [Resolution summary] | |
| 116 | |
| 117 | --- |
| 118 | |
| 119 | _Last updated: [Date] by [Name]_ |
| 120 | ``` |
| 121 | |
| 122 | ## Categories for Technical Spikes |
| 123 | |
| 124 | ### API Integration |
| 125 | |
| 126 | - Third-party API capabilities and limitations |
| 127 | - Integration patterns and authentication |
| 128 | - Rate limits and performance characteristics |
| 129 | |
| 130 | ### Architecture & Design |
| 131 | |
| 132 | - System architecture decisions |
| 133 | - Design pattern applicability |
| 134 | - Component interaction models |
| 135 | |
| 136 | ### Performance & Scalability |
| 137 | |
| 138 | - Performance requirements and constraints |
| 139 | - Scalability bottlenecks and solutions |
| 140 | - Resource utilization patterns |
| 141 | |
| 142 | ### Platform & Infrastructure |
| 143 | |
| 144 | - Platform capabilities and limitations |
| 145 | - Infrastructure requirements |
| 146 | - Deployment and hosting considerations |
| 147 | |
| 148 | ### Security & Compliance |
| 149 | |
| 150 | - Security requirements and implementations |
| 151 | - Compliance constraints |
| 152 | - Authentication and authorization approaches |
| 153 | |
| 154 | ### User Experience |
| 155 | |
| 156 | - User interaction patterns |
| 157 | - Accessibility requirements |
| 158 | - Interface design decisions |
| 159 | |
| 160 | ## File Naming Conventions |
| 161 | |
| 162 | Use descriptive, kebab-case names that indicate the category and specific unknown: |
| 163 | |
| 164 | **API/Integration Examples:** |
| 165 | |
| 166 | - `api-copilot-chat-integration-spike.md` |
| 167 | - `api-azure-speech-realtime-spike.md` |
| 168 | - `api-vscode-extension-capabilities-spike.md` |
| 169 | |
| 170 | **Performance Examples:** |
| 171 | |
| 172 | - `performance-audio-processing-latency-spike.md` |
| 173 | - `performance-extension-host-limitations-spike.md` |
| 174 | - `performance-webrtc-reliability-spike.md` |
| 175 | |
| 176 | **Architecture Examples:** |
| 177 | |
| 178 | - `architecture-voice-pipeline-design-spike.md` |
| 179 | - `architecture-state-management-spike.md` |
| 180 | - `architecture-error-handling-strategy-spike.md` |
| 181 | |
| 182 | ## Best Practices for AI Agents |
| 183 | |
| 184 | 1. **One Question Per Spike:** Each document focuses on a single technical decision or research question |
| 185 | |
| 186 | 2. **Time-Boxed Research:** Define specific time limits and deliverables for each spike |
| 187 | |
| 188 | 3. **Evidence-Ba |
People who liked this also viewed
6 picksType
- grill-with-docsA relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.SkillsJul 2026
- lark-minutes飞书妙记：搜索妙记、查看妙记基础信息、下载/上传音视频、读取或编辑妙记的产物内容、改标题、替换说话人/关键词、申请妙记查看/编辑权限。当给出minute_token、本地音视频文件，要查/改/转妙记产物，或用户明确要主动申请妙记权限时使用；本地音视频转纪要/逐字稿优先走本 skill，不要用 ffmpeg/whisper 本地转写。不负责：获取会议关联妙记，或仅按自然语言标题定位纪要SkillsJul 2026
- lark-markdown飞书 Markdown：查看、创建、上传、编辑和比较 Markdown 文件。当用户需要创建或编辑 Markdown 文件、读取、修改、局部 patch 或比较差异时使用。不负责将 Markdown 导入为飞书在线文档，也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。SkillsJul 2026
- docxUse this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', SkillsJul 2026
- edit-articleSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- lark-note飞书会议纪要（Note）直查：已知 note_id 时查询纪要详情、展示类型、关联文档 token，并读取 unified 原始逐字记录。当用户已持有 note_id，或从文档显式 vc-node-id 获得 note_id 时使用。不负责会议/日程/妙记定位、文档标题搜索或 Docx 正文读取。SkillsJul 2026
