product-on-purpose/pm-skills/develop-spike-summary

Claude Code and agent skill by product-on-purpose/pm-skills

Trust tier 2
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

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.

Install

npx vskill@latest install product-on-purpose/pm-skills/develop-spike-summary

SKILL.md

The same SKILL.md was published earlier as product-on-purpose/pm-skills/develop-spike-summary.

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

Articulate the specific question the spike was designed to answer. Good spike questions are focused and answerable with the time-box available. If the question evolved during the spike, document both the original and final versions.

  1. Define the Time-Box

Document the time allocated (e.g., 3 days) and actual time spent. If the spike exceeded its time-box, explain why and note any remaining work.

  1. Describe the Approach

Explain what was tried, in what order, and why. This helps future readers understand the methodology and whether alternative approaches were considered.

  1. Present Findings with Evidence

Document what was learned, supported by concrete evidence - code samples, performance benchmarks, screenshots, or API responses. Distinguish between verified findings and hypotheses that need more testing.

  1. Make a Clear Recommendation

Answer the original question directly: proceed, do not proceed, or proceed with conditions. Avoid hedging - the team needs actionable guidance.

  1. Document Artifacts

Link to any code, prototypes, diagrams, or documentation created during the spike. These artifacts often have ongoing value beyond the summary.

  1. Capture Open Questions

Note what the spike didn't answer and what additional investigation might be needed.

Output Format

Use the template in references/TEMPLATE.md to structure the output. A complete spike summary fills every template section: Overview; Background; Approach; Findings; Recommendation; Artifacts; Open Questions; and Follow-up Items.

Quality Checklist

Before finalizing, verify:

  • [ ] Original question is clearly stated
  • [ ] Time-box is documented (allocated vs. actual)
  • [ ] Findings are supported by evidence, not just opinions
  • [ ] Recommendation directly answers the question
  • [ ] Artifacts (code, diagrams) are linked or attached
  • [ ] Open questions identify remaining unknowns

Examples

See references/EXAMPLE.md for a completed example.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
698
Repository forks
88
7-day trend score
33

Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 4 Aug 2026, 3 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/product-on-purpose/pm-skills/develop-spike-summary/badge)](https://verified-skill.com/skills/product-on-purpose/pm-skills/develop-spike-summary)

Something wrong with this skill or its page? Tell us.