definition.tech_spike
Scope and prioritize technical spikes that de-risk architecture or implementation questions.
Best use case
definition.tech_spike is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Scope and prioritize technical spikes that de-risk architecture or implementation questions.
Teams using definition.tech_spike should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/definition.tech_spike/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How definition.tech_spike Compares
| Feature / Agent | definition.tech_spike | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Scope and prioritize technical spikes that de-risk architecture or implementation questions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Purpose
Help engineering leaders quickly define spikes that reduce uncertainty and feed confidently into planning conversations.
# Pre-run Checklist
- ✅ Clarify what decision will be unlocked by the spike.
- ✅ Align on timebox and resourcing availability.
- ✅ Gather related research or prior explorations.
# Invocation Guidance
```bash
codex skills run definition.tech_spike \
--vars "topic={{topic}}" \
"desired_outcome={{desired_outcome}}" \
"constraints={{constraints}}" \
"collaborators={{collaborators}}"
```
# Recommended Input Attachments
- Architecture diagrams or RFCs.
- Known issues or bugs impacting the area.
# Claude Workflow Outline
1. Summarize context, desired outcome, and constraints.
2. Define success criteria and explicit questions to answer.
3. Outline the spike plan with tasks, owners, and deliverables.
4. Recommend instrumentation or benchmarks to capture results.
5. Provide guidance for sharing outcomes and converting to stories.
# Output Template
```
## Spike Charter — {{topic}}
### Background
...
### Questions to Answer
1. ...
### Success Criteria
- Criterion:
### Plan & Timebox
| Task | Owner | Duration | Notes |
| --- | --- | --- | --- |
### Reporting Plan
- Artifact:
- Audience:
- Next Steps:
```
# Follow-up Actions
- Create spike tickets in the engineering tracker with links to this output.
- Schedule readout with the product trio to review learnings.
- Convert recommendations into backlog work with acceptance criteria.Related Skills
dma-attack-techniques
Guide for Direct Memory Access (DMA) attack techniques using FPGA hardware. Use this skill when researching PCIe DMA attacks, pcileech, FPGA firmware development, or hardware-based memory access for game security research.
technical-review
No description provided.
anti-reversing-techniques
Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or understanding software protection mechanisms.
technical-architecture
Autonomous Staff Engineer agent that analyzes a product requirement brief, extracts non-functional requirements, and generates a comprehensive technical architecture document. Accepts an optional tech-stack-preferences.md file path. Runs end-to-end without asking questions. Use when turning product requirements into technical architecture decisions.
Requirements Definition
This skill should be used when the user asks to "define requirements", "create specification", "clarify requirements", "write requirements document", or mentions requirement analysis. Provides comprehensive requirements definition methodology.
architechture
本项目里面的各种架构设计, 设计中用到的各种概念例如 system, action, view-function, action-function, action-handler, base, component 等的解释
ai-search-technical-auditor
Audit front-end code for AI search readiness. Use when reviewing HTML structure, meta tags, schema markup, and technical elements that affect how AI crawlers understand and index web pages.
technical-writing
Write clear technical documentation, tutorials, and guides. Use this skill when creating README files, API docs, setup guides, architecture docs, or technical tutorials.
technical-writer
Use for documentation tasks including API docs, user guides, JSDoc comments, grammar documentation, and README updates. Activate when writing or reviewing documentation, creating JSDoc, or updating examples. For public docs in /site, pair with site-maintainer.
technical-accuracy-and-usability-rules
Ensures the documentation is technically accurate and highly usable for the target audience.
agent-technical-writer
Expert technical writer specializing in clear, accurate documentation and content creation. Masters API documentation, user guides, and technical content with focus on making complex information accessible and actionable for diverse audiences.
agent-ops-create-technical-docs
Create focused, specific technical documentation for codebase sections. Analyzes code, identifies topics, presents options before writing. Supports code blocks with line numbers.