technical-research
Technical spike and research investigation specialist. Use when exploring options for a technical decision, conducting timeboxed investigations, or evaluating technology choices.
Installation
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
View source ↗GuidesSkill instructions
Technical Research Skill
Structured approach to technical spikes, proof of concepts, and technology evaluations.
What This Skill Does
- Conducts timeboxed technical investigations
- Creates proof of concept implementations
- Compares technical options objectively
- Documents findings and recommendations
- Identifies risks and dependencies
- Provides implementation paths
When to Use
- Technology selection decisions
- Architecture exploration
- Feasibility studies
- Performance investigations
- Library/framework evaluation
Reference Files
-
references/TECHNICAL_SPIKE.template.md- Structured spike investigation format
Spike Structure
- Objective - Clear questions to answer
- Timebox - Fixed investigation period
- Options - Multiple approaches explored
- POC - Working code for each option
- Comparison - Weighted criteria matrix
- Recommendation - Justified decision
Best Practices
- Define success criteria upfront
- Explore at least 2-3 options
- Create runnable POC code
- Document trade-offs honestly
- Track unanswered questions
- Stay within timebox
Examples
Read the usage examples in the source repository.
View source ↗Source history
- Indexed on
- 2026-01-20
- Index updated
- 2026-01-28
- Branch
- main
Index and sync dates describe this directory. View the source repository for code history.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!