bm:spike

Spike an idea through experiential exploration — build focused experiments to feel the pieces of a future app, validate feasibility, and produce verified knowledge for the real build. Spikes live in `.planning/spikes/` and integrate with GSD commit patterns, state tracking, and handoff workflows.

Two modes:

• Idea mode (default) — describe an idea to spike
• Frontier mode (no argument or "frontier") — analyzes existing spike landscape and proposes integration and frontier spikes

Does not require /bm:new-project — auto-creates .planning/spikes/ if needed.

<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/spike.md @${CLAUDE_PLUGIN_ROOT}/references/ui-brand.md </execution_context>

<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. </runtime_note>

Idea: $ARGUMENTS

Available flags:

• --quick — Skip decomposition/alignment, jump straight to building. Use when you already know what to spike.
• --text — Use plain-text numbered lists instead of AskUserQuestion (for non-Claude runtimes).

Execute the spike workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/spike.md end-to-end. Preserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns).