srstomp/spike
plugins/pokayokay/skills/spike/SKILL.md
Time-boxed technical investigation with structured output. Use for feasibility studies, architecture exploration, integration assessment, performance analysis, or risk evaluation. Creates spike tasks in ohno, enforces time-boxing, generates spike reports, and creates actionable follow-up tasks.
$ install --global
skillsauthnpx skillsauth add srstomp/pokayokay spikeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 7:05 AM45.4s4 files scanned
SKILL.md
- name:
- spike
- agents:
- [yokay-spike-runner]
- description:
- Time-boxed technical investigation with structured output. Use for feasibility studies, architecture exploration, integration assessment, performance analysis, or risk evaluation. Creates spike tasks in ohno, enforces time-boxing, generates spike reports, and creates actionable follow-up tasks.
Spike
Structured technical investigation to reduce uncertainty. Answer specific questions, not "explore X."
Key Principles
- Every spike answers a specific, measurable question
- Strict time-box (default 4h) — produce a decision at the end, even if incomplete
- Output is a decision (GO/NO-GO/PIVOT/MORE-INFO), not a general exploration
- Create follow-up tasks from findings, not just a report
When NOT to Use
- Multi-day evaluations — Use
deep-researchfor comprehensive technology evaluations with stakeholder reports - Already know what to build — Skip straight to implementation; spikes are for reducing uncertainty, not planning known work
- Bug investigation — Use
error-handlingor/fix; bugs have reproduction steps, spikes have open questions
Quick Start Checklist
- Define the question clearly (what are we trying to learn?)
- Set a time-box (hours, not days — use deep-research for multi-day)
- Identify evaluation criteria upfront
- Investigate with focused experiments or prototypes
- Checkpoint at 50% — assess progress, decide if pivoting
- Produce mandatory conclusion: GO / NO-GO / PIVOT / MORE-INFO
Mandatory Outputs
- Decision: GO, NO-GO, PIVOT, or MORE-INFO
- Evidence: What was tested, results observed
- Follow-up tasks: Created in ohno if GO
- Report: Saved to
.claude/spikes/[name]-[date].md
References
| Reference | Description | |-----------|-------------| | spike-types.md | Feasibility, architecture, integration, performance spikes | | question-patterns.md | How to frame good spike questions | | output-templates.md | Spike report templates and examples |
Related Skills
srstomp/worktrees
development
VerifiedTrustedCommunity
Git worktree management for isolated task development
6SKILL.mdUpdated Apr 27, 2026
srstomp/work-session
development
VerifiedTrustedCommunity
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
6SKILL.mdUpdated Apr 27, 2026
srstomp/verification-before-completion
testing
VerifiedTrustedCommunity
Use before claiming work is done, fixed, passing, ready to commit, ready to PR, or ready to mark complete. Requires fresh verification evidence and explicit command output before success claims.
6SKILL.mdUpdated Apr 27, 2026
srstomp/testing-strategy
development
VerifiedTrustedCommunity
Use when designing test architecture, building API test suites, validating API contracts, setting up component or E2E testing, managing test data, debugging flaky tests, reviewing coverage strategy, or organizing test files. Covers test pyramid, mocking (MSW), frontend (React Testing Library, Playwright), and CI integration.
6SKILL.mdUpdated Apr 27, 2026