Develop Spike Summary

Documents the results of a completed technical or design spike, capturing the original question, approach, evidence-backed findings, and a clear proceed-or-not recommendation so the team does not re-litigate the exploration. Use once a time-boxed investigation has concluded. For the architecture decision the spike informs, use develop-adr instead; for research-based exploration, use discover-interview-synthesis.

819 stars 104 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add product-on-purpose/pm-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add product-on-purpose/pm-skills --skill develop-spike-summary
Manual install
git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/develop-spike-summary ~/.claude/skills/develop-spike-summary

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Spike Summary

A spike summary documents the results of a time-boxed exploration - a focused investigation to reduce uncertainty before committing to implementation. Spikes answer specific questions like "Can we integrate with this API?" or "Is this technology viable for our use case?" The summary captures findings so the team can make informed decisions without the spike participants needing to repeat explanations.

## When to Use

- After completing a time-boxed technical exploration
- When evaluating technology choices or vendor options
- After proof-of-concept work that needs to inform team decisions
- When investigating feasibility of a proposed solution
- Before committing engineering resources to a new approach

## When NOT to Use

- You are recording the resulting architecture decision itself -> use `develop-adr`; the spike informs, the ADR decides
- The exploration was user research, not technical or design feasibility -> use `discover-interview-synthesis`
- You want to propose the solution the spike pointed to -> use `develop-solution-brief`
- The spike has not happened yet: this skill documents results; time-box and run the exploration first

## Instructions

When asked to document a spike, follow these steps:

1. **State the Question Clearly**
Read the full skill on GitHub

Details

Skill name
develop-spike-summary
Path
skills/develop-spike-summary/SKILL.md
License
Apache-2.0
Repo updated
17 November 2026

FAQ

What does the Develop Spike Summary skill do?

Documents the results of a completed technical or design spike, capturing the original question, approach, evidence-backed findings, and a clear proceed-or-not recommendation so the team does not re-litigate the exploration. Use once a time-boxed investigation has concluded. For the architecture decision the spike informs, use develop-adr instead; for research-based exploration, use discover-interview-synthesis.

How do I install the Develop Spike Summary skill?

Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Develop Spike Summary popular?

It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.

Related skills

<phase or Classification Skill Name>

819

product-on-purpose/pm-skills

<single-line 20-100 word description; include trigger keywords and do not use folded YAML>

Skill & Plugin AuthoringIn 2 lists104

Define Hypothesis

819

product-on-purpose/pm-skills

Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.

Finance & CryptoIn 2 lists104

Define Jtbd Canvas

819

product-on-purpose/pm-skills

Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.

Frontend & DesignIn 2 lists104

Discover Market Sizing

819

product-on-purpose/pm-skills

Estimate market opportunity (TAM, SAM, SOM) using multiple sizing frameworks (top-down, bottom-up, comparable company, analogous market). Triangulates across frameworks, highlights where they converge and diverge as signal, and produces a calibrated range with source-graded confidence labels. Refuses unbounded fabrications; always offers a labeled lower-confidence path when data is thin. Used for investment cases, go/no-go decisions, and stakeholder pitches.

Software DevelopmentIn 2 lists104

Develop Solution Brief

819

product-on-purpose/pm-skills

Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.

Software DevelopmentIn 2 lists104

Extension to Functions Codebase

519

firebase/agent-skills

Skill for converting an installed Firebase Extension (or extension source) into a standalone Cloud Functions for Firebase codebase or publishable npm package, including V1 to V2 trigger upgrades, lifecycle hooks, and declarative security

Software Development116

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.