run-spike

Structures a time-bound risk spike to evaluate load-bearing unknowns and document decisions.

5|3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/leifericf/agentic-sdk --skill run-spike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-spike
Source: https://github.com/leifericf/agentic-sdk/tree/main/skills/run-spike
Command: npx skills add https://github.com/leifericf/agentic-sdk --skill run-spike

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers address and mitigate risks associated with unknowns in software development, by structuring a risk spike to evaluate and decide on the next steps.

Core Features & Use Cases

  • Risk Evaluation: Structure a risk spike to evaluate a load-bearing unknown.
  • Time-Bound: Run the spike within a predefined time-box.
  • Decision Making: Decide on go, no-go, or mitigation based on the spike's outcome.
  • Documentation: Document failure modes, limits, and workarounds.
  • Outcome Recording: Record decisions and constraints for future reference.
  • Use Case: When facing a complex native edge or real-time budget, use this Skill to build a throwaway harness and exercise the seam to determine the next steps.

Quick Start

Run a risk spike for the 'native edge' unknown by executing the 'run-spike' command.

Frequently Asked Questions about run-spike

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

FAQPage Schema
What is a risk spike in software development?

A risk spike is a time-bound investigation used to evaluate load-bearing unknowns in software development. Developers build a throwaway harness to test a specific seam, allowing them to decide on go, no-go, or mitigation based on performance and stability.

How do I evaluate a load-bearing unknown before committing to an implementation?

To evaluate a load-bearing unknown, structure a risk spike with a predefined time-box. Build a throwaway harness to exercise the unknown seam, document failure modes and limits, then record decisions and constraints for future reference.

When should I run a time-boxed spike instead of full implementation?

Run a time-boxed spike when facing a complex native edge or real-time budget constraint. Use this approach to exercise the seam with a throwaway harness and determine next steps based on actual performance and stability rather than speculation.

How do I document the outcome of a risk spike?

Document a risk spike outcome by recording the go, no-go, or mitigation decision based on performance results. Include failure modes, identified limits, workarounds, and constraints to provide future reference and rationale for the decision.

What is the best way to mitigate unknown risks in a real-time budget scenario?

The best way to mitigate unknown risks in a real-time budget scenario is executing a structured risk spike. Build a throwaway harness to exercise the seam within a time-box, evaluating performance and stability to determine go, no-go, or mitigation.

Does a risk spike require a throwaway harness?

Yes, a risk spike requires a throwaway harness to isolate and exercise the load-bearing unknown. This time-bound execution focuses purely on evaluating performance and stability for decision-making, preventing code entanglement with production systems.