Use when the user wants to test an idea before committing to a real build: "spike this", "quick prototype", "is this possible", "compare A/B", "before we build".

Do not use when reading docs/code can answer the question, or when the user clearly asked for production implementation.

Loop

Question: state the concrete feasibility question.
Research: read enough docs/source to choose credible approach.
Build: create the smallest runnable artifact that validates or invalidates the idea.
Stress: try one edge case or failure mode.
Verdict: VALIDATED, PARTIAL, or INVALIDATED.

Output shape

Default workspace: .tmp/openclaw-spikes/<slug> unless user asks for a tracked repo-local path.
Repo-local option: spikes/<NNN-slug>/ with README.md and minimal code.
Prefer runnable CLI, tiny HTML, one endpoint, or focused test.
Avoid package sprawl, Docker, env files, app frameworks, and production cleanup.

Multi-spike ideas

Split into 2-5 independent questions.
Run the riskiest question first.
For A/B comparisons, keep inputs equal and measure the same dimensions.
Ask before building all variants if the work is more than a small prototype.

Verdict format

## Verdict: VALIDATED | PARTIAL | INVALIDATED

Question: ...
Evidence: exact command/output/measurement.
What worked: ...
What failed or surprised us: ...
Recommendation: ship / adjust / avoid, with the next production step.

Rules

An invalidated spike is useful when it rules out a path with evidence.
Do not merge spike code into production without rewriting it normally.
If external dependencies are evaluated, check health: recent release/commit, docs, license, install friction.

PilotDeck Migration Note

Source: /var/folders/27/xyyzc_n172l3jjmnxgqmhhzh0000gn/T/tmp.AyWDWGKoS4/openclaw/skills/spike
Review status: candidate for PilotDeck native skills pack.
Platform-specific OpenClaw/Hermes metadata was removed or should be ignored during review.

Más de este repositorio

mismo repositorio

meeting-recorder-assistant

OpenBMB/PilotDeck

Intelligent meeting recording and transcription assistant with automated minutes generation, action item extraction, and sentiment analysis. Supports audio transcription, speaker diarization, meeting summarization, and task extraction. Use when users need to record meetings, transcribe audio, generate meeting minutes, extract action items, or analyze meeting content.

2026-06-093.7k

1password

OpenBMB/PilotDeck

Set up and use 1Password CLI for sign-in, desktop integration, and reading or injecting secrets.

2026-06-093.7k

apple-notes

OpenBMB/PilotDeck

Create, view, edit, delete, search, move, or export Apple Notes via the memo CLI on macOS.

2026-06-093.7k

apple-reminders

OpenBMB/PilotDeck

List, add, edit, complete, or delete Apple Reminders and reminder lists via remindctl.

2026-06-093.7k

bear-notes

OpenBMB/PilotDeck

Create, search, and manage Bear notes via grizzly CLI.

2026-06-093.7k

blogwatcher

OpenBMB/PilotDeck

Monitor blogs and RSS/Atom feeds for updates using the blogwatcher CLI.

2026-06-093.7k

Spike

Use when the user wants to test an idea before committing to a real build: "spike this", "quick prototype", "is this possible", "compare A/B", "before we build".

Do not use when reading docs/code can answer the question, or when the user clearly asked for production implementation.

Loop

Question: state the concrete feasibility question.

Research: read enough docs/source to choose credible approach.

Build: create the smallest runnable artifact that validates or invalidates the idea.

Stress: try one edge case or failure mode.

Verdict: VALIDATED, PARTIAL, or INVALIDATED.

Output shape

Default workspace: .tmp/openclaw-spikes/<slug> unless user asks for a tracked repo-local path.

Repo-local option: spikes/<NNN-slug>/ with README.md and minimal code.

Prefer runnable CLI, tiny HTML, one endpoint, or focused test.

Avoid package sprawl, Docker, env files, app frameworks, and production cleanup.

Multi-spike ideas

Split into 2-5 independent questions.

Run the riskiest question first.

For A/B comparisons, keep inputs equal and measure the same dimensions.

Ask before building all variants if the work is more than a small prototype.

Verdict format

## Verdict: VALIDATED | PARTIAL | INVALIDATED Question: ... Evidence: exact command/output/measurement. What worked: ... What failed or surprised us: ... Recommendation: ship / adjust / avoid, with the next production step.

Rules

An invalidated spike is useful when it rules out a path with evidence.

Do not merge spike code into production without rewriting it normally.

If external dependencies are evaluated, check health: recent release/commit, docs, license, install friction.

PilotDeck Migration Note

Source: /var/folders/27/xyyzc_n172l3jjmnxgqmhhzh0000gn/T/tmp.AyWDWGKoS4/openclaw/skills/spike

Review status: candidate for PilotDeck native skills pack.

Platform-specific OpenClaw/Hermes metadata was removed or should be ignored during review.