PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
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…
Install Develop Spike Summary
$ npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install product-on-purpose/pm-skills develop-spike-summary --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/develop-spike-summary .claude/skills/develop-spike-summary && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "develop-spike-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-spike-summary into .claude/skills/develop-spike-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-spike-summary", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-spike-summaryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install product-on-purpose/pm-skills develop-spike-summary --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/develop-spike-summary .agents/skills/develop-spike-summary && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "develop-spike-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-spike-summary into .agents/skills/develop-spike-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-spike-summary", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install product-on-purpose/pm-skills develop-spike-summary --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/develop-spike-summary .cursor/skills/develop-spike-summary && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "develop-spike-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-spike-summary into .cursor/skills/develop-spike-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-spike-summary", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/product-on-purpose/pm-skills.git --path skills/develop-spike-summary--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install product-on-purpose/pm-skills develop-spike-summary --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/develop-spike-summary .gemini/skills/develop-spike-summary && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "develop-spike-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-spike-summary into .gemini/skills/develop-spike-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-spike-summary", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install product-on-purpose/pm-skills develop-spike-summaryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/develop-spike-summary .github/skills/develop-spike-summary && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "develop-spike-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-spike-summary into .github/skills/develop-spike-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-spike-summary", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install product-on-purpose/pm-skills develop-spike-summary --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/develop-spike-summary .opencode/skills/develop-spike-summary && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "develop-spike-summary" agent skill from https://github.com/product-on-purpose/pm-skills/tree/main/skills/develop-spike-summary into .opencode/skills/develop-spike-summary/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "develop-spike-summary", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
develop-spike-summary- GitHub stars
- 715
- Token cost
- ~1k tokens
- SKILL.md length
- 440 words
- Files
- 5 (incl. references)
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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…
- Works in 7 steps: State the Question Clearly → Define the Time-Box → Describe the Approach → …
- Tasks that involve Architecture decision records
- SKILL.md covers When to Use, When NOT to Use, Instructions and Output Format, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Develop Spike Summary is an agent skill from product-on-purpose/pm-skills. 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.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `HISTORY.md`, `evals/trigger-fixtures.json` and `references/EXAMPLE.md`).
It sits in Development, covering Architecture decision records. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.
When your agent uses it
- Tasks that involve Architecture decision records
Example prompts
- “Use the develop-spike-summary skill to document the results of a completed technical or design spike, capturing the original question, approach…”
- “/develop-spike-summary”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- State the Question Clearly
- Define the Time-Box
- Describe the Approach
- Present Findings with Evidence
- Make a Clear Recommendation
- Document Artifacts
- Capture Open Questions
What it can do on your machine
Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Develop Spike Summary loads about 1k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 109 tokens; SKILL.md has 440 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 440 words, ~1,007 tokens.
Download SKILL.mdSave it as
.claude/skills/develop-spike-summary/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- develop-spike-summary
- description
- 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.
- license
- Apache-2.0
- metadata.phase
- develop
- metadata.version
- 2.2.0
- metadata.updated
- 2026-07-04
- metadata.category
- coordination
- metadata.frameworks
- triple-diamond, lean-startup, design-thinking
- metadata.author
- product-on-purpose
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->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:
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.
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.
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.
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.
Make a Clear Recommendation Answer the original question directly: proceed, do not proceed, or proceed with conditions. Avoid hedging - the team needs actionable guidance.
Document Artifacts Link to any code, prototypes, diagrams, or documentation created during the spike. These artifacts often have ongoing value beyond the summary.
Capture Open Questions Note what the spike didn't answer and what additional investigation might be needed.
Show full SKILL.md (78 more words)Show less
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.
© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/develop-spike-summary of product-on-purpose/pm-skills.
- SKILL.md
- HISTORY.md
- evals/trigger-fixtures.json
- references/EXAMPLE.md
- references/TEMPLATE.md
Open the folder on GitHubat commit 1cef1a9
Compare with similar skills
Develop Spike Summary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Develop Spike Summary this skillproduct-on-purpose/pm-skills | 715 | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 380 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Design Doc MermaidSpillwaveSolutions/design-doc-mermaid | 175 | 1 repos | ~5.6k | Automated safety check: Pass | None |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
Learning Opportunities
DrCatHicks/learning-opportunities
Facilitates deliberate skill development during AI-assisted coding.
More from product-on-purpose/pm-skills
All 68 skills in this repoDefine Hypothesis
product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach.
Define Jtbd Canvas
product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.
Define Opportunity Tree
product-on-purpose/pm-skills
Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.
Define Problem Statement
product-on-purpose/pm-skills
Creates a clear problem framing document with user impact, business context, and success criteria.
Deliver Acceptance Criteria
product-on-purpose/pm-skills
Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.
Deliver Launch Checklist
product-on-purpose/pm-skills
Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…
Related
Categories
Questions about Develop Spike Summary
What does Develop Spike Summary 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…. Develop Spike Summary is an agent skill from product-on-purpose/pm-skills. 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.
When should I use Develop Spike Summary?
Develop Spike Summary fits situations like: tasks that involve Architecture decision records.
How do I install Develop Spike Summary in Claude Code?
Run `npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a claude-code`. Or copy the skill folder (skills/develop-spike-summary in product-on-purpose/pm-skills) into .claude/skills/develop-spike-summary in your project. Claude Code loads it when a task matches its description.
How do I install Develop Spike Summary in Codex?
Run `npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a codex`. Or copy the skill folder (skills/develop-spike-summary in product-on-purpose/pm-skills) into .agents/skills/develop-spike-summary in your project. Codex loads it when a task matches its description.
Can I use Develop Spike Summary in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill develop-spike-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/develop-spike-summary, .gemini/skills/develop-spike-summary, .github/skills/develop-spike-summary and .opencode/skills/develop-spike-summary in your project.
What does Develop Spike Summary need to run?
SKILL.md names no scripts, command-line tools or credentials: Develop Spike Summary is instructions for the agent only.
Does Develop Spike Summary access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Develop Spike Summary safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Develop Spike Summary use?
Develop Spike Summary is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Develop Spike Summary use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.1k tokens, read only when the agent opens those files.
What are the alternatives to Develop Spike Summary?
Skills that share tags, products or a category with Develop Spike Summary: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Develop Spike Summary?
product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 715 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 4, 2026.
Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.