mcpField
T
technical-research

technical-research

github.com/89jobrienDevelopment465 installsUpdated 10w ago
Repository

About technical-research

Technical Research is a skill for structured, timeboxed technical investigations, proofs of concept, and technology evaluations. It helps engineering teams compare options, document risks, and choose an implementation path.

Key features

  1. 01Run timeboxed technical investigations
  2. 02Build proof-of-concept implementations
  3. 03Compare technical options objectively
  4. 04Document findings, risks, and dependencies
  5. 05Recommend implementation paths

Use cases

  1. 01Evaluate libraries or frameworks
  2. 02Explore architecture options
  3. 03Assess technical feasibility
  4. 04Investigate performance questions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/89jobrien/steve --skill technical-research

After installing, type/technical-researchin Claude Code to confirm it loaded.

Bundled filesreferences/technical-spike.template.md

Details

From the project README

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

Comments

Markdown supported