
Technical Research
- 59 installs
- 4 repo stars
- Updated April 11, 2026
- 89jobrien/steve
technical-research is a Claude Code skill for timeboxed technical spikes, proofs of concept, and technology evaluations.
About
technical-research is a Claude Code skill for structured technical spikes and technology evaluations. It runs timeboxed investigations, builds proof-of-concept code for multiple options, and compares them on weighted criteria. Developers use it when making a technology or architecture decision. It documents trade-offs, risks, and a justified recommendation using a spike template.
- Runs timeboxed technical spikes and proof-of-concept investigations
- Compares 2-3 technical options with a weighted criteria matrix
- Documents findings, risks, and a justified recommendation
Technical Research by the numbers
- 59 all-time installs (skills.sh)
- Ranked #1,560 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 28, 2026 (Skillselion catalog sync)
technical-research capabilities & compatibility
- Capabilities
- technical spike · option comparison · feasibility study
- Use cases
- research
What technical-research says it does
Structured approach to technical spikes, proof of concepts, and technology evaluations.
Explore at least 2-3 options
npx skills add https://github.com/89jobrien/steve --skill technical-researchAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 59 |
|---|---|
| repo stars | ★ 4 |
| Last updated | April 11, 2026 |
| Repository | 89jobrien/steve ↗ |
What it does
Run a timeboxed technical spike comparing 2-3 options with proof-of-concept code and a justified recommendation.
Who is it for?
Developers making a technology or architecture decision who need a structured, evidence-based comparison.
When should I use this skill?
Exploring options for a technical decision, conducting a timeboxed investigation, or evaluating technology choices.
What you get
A documented spike with POC code, a criteria matrix, and a justified recommendation.
- A technical spike document
- Proof-of-concept code
- A weighted comparison matrix
By the numbers
- 6-part spike structure
- Explores at least 2-3 options
Files
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
1. Objective - Clear questions to answer 2. Timebox - Fixed investigation period 3. Options - Multiple approaches explored 4. POC - Working code for each option 5. Comparison - Weighted criteria matrix 6. 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
Technical Spike: {{SPIKE_TITLE}}
Ticket: {{TICKET_ID}} Date: {{YYYY-MM-DD}} Engineer: {{NAME}} Timebox: {{HOURS}} hours
---
Objective
{{WHAT_ARE_WE_TRYING_TO_LEARN}}
Questions to Answer
1. {{QUESTION_1}} 2. {{QUESTION_2}} 3. {{QUESTION_3}}
Success Criteria
- [ ] {{CRITERION_1}}
- [ ] {{CRITERION_2}}
- [ ] {{CRITERION_3}}
---
Background
Context
{{WHY_IS_THIS_SPIKE_NEEDED}}
Constraints
- {{CONSTRAINT_1}}
- {{CONSTRAINT_2}}
Assumptions
- {{ASSUMPTION_1}}
- {{ASSUMPTION_2}}
---
Options Explored
Option 1: {{OPTION_NAME}}
Description: {{BRIEF_DESCRIPTION}}
Proof of Concept:
```{{LANGUAGE}} {{CODE_SAMPLE}}
**Findings:**
- {{FINDING_1}}
- {{FINDING_2}}
**Pros:**
- {{PRO_1}}
- {{PRO_2}}
**Cons:**
- {{CON_1}}
- {{CON_2}}
**Effort Estimate:** {{LOW/MEDIUM/HIGH}}
---
### Option 2: {{OPTION_NAME}}
**Description:** {{BRIEF_DESCRIPTION}}
**Proof of Concept:**
{{CODE_SAMPLE}}
**Findings:**
- {{FINDING_1}}
**Pros:**
- {{PRO_1}}
**Cons:**
- {{CON_1}}
**Effort Estimate:** {{LOW/MEDIUM/HIGH}}
---
### Option 3: {{OPTION_NAME}}
**Description:** {{BRIEF_DESCRIPTION}}
**Findings:**
- {{FINDING_1}}
**Verdict:** {{VIABLE/NOT_VIABLE}}
---
## Comparison Matrix
| Criteria | Weight | Option 1 | Option 2 | Option 3 |
|----------|--------|----------|----------|----------|
| {{CRITERIA_1}} | {{1-5}} | {{SCORE}} | {{SCORE}} | {{SCORE}} |
| {{CRITERIA_2}} | {{1-5}} | {{SCORE}} | {{SCORE}} | {{SCORE}} |
| {{CRITERIA_3}} | {{1-5}} | {{SCORE}} | {{SCORE}} | {{SCORE}} |
| **Weighted Total** | - | {{TOTAL}} | {{TOTAL}} | {{TOTAL}} |
---
## Recommendation
**Recommended Option:** {{OPTION_NAME}}
### Rationale
{{WHY_THIS_OPTION}}
### Risks
| Risk | Likelihood | Impact | Mitigation |
|------|------------|--------|------------|
| {{RISK_1}} | {{H/M/L}} | {{H/M/L}} | {{STRATEGY}} |
| {{RISK_2}} | {{H/M/L}} | {{H/M/L}} | {{STRATEGY}} |
### Dependencies
- {{DEPENDENCY_1}}
- {{DEPENDENCY_2}}
---
## Implementation Path
### Phase 1: {{PHASE_NAME}}
- {{TASK_1}}
- {{TASK_2}}
### Phase 2: {{PHASE_NAME}}
- {{TASK_1}}
- {{TASK_2}}
### Estimated Effort
| Component | Estimate |
|-----------|----------|
| {{COMPONENT_1}} | {{POINTS/DAYS}} |
| {{COMPONENT_2}} | {{POINTS/DAYS}} |
| **Total** | {{TOTAL}} |
---
## Open Questions
1. {{UNANSWERED_QUESTION_1}}
2. {{UNANSWERED_QUESTION_2}}
---
## References
- [{{DOC_1}}]({{URL}})
- [{{DOC_2}}]({{URL}})
### Code Artifacts
- Branch: `spike/{{BRANCH_NAME}}`
- POC Location: `{{PATH}}`
---
## Answers to Original Questions
| Question | Answer |
|----------|--------|
| {{QUESTION_1}} | {{ANSWER}} |
| {{QUESTION_2}} | {{ANSWER}} |
| {{QUESTION_3}} | {{ANSWER}} |
---
## Quality Checklist
- [ ] All original questions answered
- [ ] Multiple options explored
- [ ] POC code tested
- [ ] Recommendation justified
- [ ] Risks identified
- [ ] Implementation path clear
- [ ] Timeboxed appropriately
Related skills
FAQ
How many options should a spike explore?
At least 2-3 options, each with runnable POC code and a trade-off comparison.
What does the skill produce?
A structured spike with objective, timebox, options, POCs, a weighted comparison, and a justified recommendation.