he-spike

Execute time-boxed investigations and throwaway prototypes to validate technical feasibility.

4|1|Updated Feb 14, 2026

Search Tags:#planning #investigation #validation #feasibility #prototype #spike

Ready to run

npx skills add https://github.com/mattjefferson/harness-engineering --skill he-spike

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: he-spike
Source: https://github.com/mattjefferson/harness-engineering/tree/main/skills/he-spike
Command: npx skills add https://github.com/mattjefferson/harness-engineering --skill he-spike

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses uncertainty by running focused, time-boxed investigations or throwaway prototypes to validate feasibility, reduce ambiguity, or compare approaches before committing to a plan.

Core Features & Use Cases

Feasibility Validation: Use when new technology, unfamiliar APIs, or unclear constraints make the path forward uncertain.
Approach Comparison: Run parallel subagents to explore and compare multiple valid approaches.
Use Case: Before planning a complex feature involving a new third-party API, use he-spike to build a small prototype that tests the API's core functionality and identifies potential integration challenges.

Quick Start

Use the he-spike skill to investigate the feasibility of integrating the new payment gateway.

Frequently Asked Questions about he-spike

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a spike in software engineering and when is it needed?▼

A spike is a time-boxed investigation or throwaway prototype used to validate technical feasibility and reduce ambiguity before formal planning. It is needed when facing uncertain technology, unfamiliar APIs, or unclear constraints.

How do I validate technical feasibility before committing to a feature plan?▼

Validate technical feasibility by running focused, time-boxed investigations to test core functionality and identify potential integration challenges. This approach documents findings and recommends next steps for informed decision-making.

What's the best way to compare multiple technical approaches for a new feature?▼

Comparing multiple technical approaches is best done by running parallel subagents to explore and evaluate each valid option. This method reduces ambiguity and documents findings to recommend the most informed next steps.

Can I use a throwaway prototype to test unfamiliar third-party APIs?▼

Yes, you can use a throwaway prototype to test unfamiliar third-party APIs. Building a small prototype tests the API's core functionality and identifies potential integration challenges before committing to a formal plan.

Does a feasibility spike require formal planning beforehand?▼

No, a feasibility spike does not require formal planning beforehand. It executes time-boxed investigations specifically to reduce ambiguity and validate constraints, enabling informed decision-making before the formal planning phase begins.