spike

Included with Lifetime

$97 forever

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.

General

What this skill does


# 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-research` for 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-handling` or `/fix`; bugs have reproduction steps, spikes have open questions

## Quick Start Checklist

1. Define the question clearly (what are we trying to learn?)
2. Set a time-box (hours, not days — use deep-research for multi-day)
3. Identify evaluation criteria upfront
4. Investigate with focused experiments or prototypes
5. Checkpoint at 50% — assess progress, decide if pivoting
6. 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](references/spike-types.md) | Feasibility, architecture, integration, performance spikes |
| [question-patterns.md](references/question-patterns.md) | How to frame good spike questions |
| [output-templates.md](references/output-templates.md) | Spike report templates and examples |

Files: 4

Size: 27.2 KB

Complexity: 49/100

Category: General

Source: https://github.com/srstomp/pokayokay/tree/main/plugins/pokayokay/skills/spike

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts