msd-core/commands/msd/spike.md at next

Files

Jakub Zych 6cfa0c55d2 refactor: drop 12 runtimes, keep Claude, Codex, OpenCode, Cursor, ZCode, Antigravity

Removes kilo, kimi, kimi-code, copilot, windsurf, augment, trae, qwen, hermes,
cline, codebuddy and pi end to end: capability descriptors, installer branches
and converters (bin/install.js 14.9k -> 11.2k lines), TypeScript converters,
hook surfaces and runtime homes, review lanes qwen/kimi-code, the two pi
migrations, Kimi payload normalization in the hook guards, dead hostBehaviors
vocabulary, launcher home probes, fixtures, runtime-specific tests and the
prose that presented them as supported.

Installer output for the six kept runtimes is byte-identical to before the
prune. The Kimi tool-vocabulary tests in workflow-guard, read-guard and
read-injection-scanner are left in place pending a decision.

2026-10-06 20:02:40 +02:00

1.9 KiB

Raw Permalink Blame History

name, description, argument-hint, allowed-tools, requires

name

description

argument-hint

allowed-tools

requires

msd:spike

Spike an idea through experiential exploration, or propose what to spike next (frontier mode)

[idea to validate] [--quick] [--text] [--wrap-up] or [frontier]

Read

Write

Edit

Bash

Grep

Glob

AskUserQuestion

WebSearch

WebFetch

mcp__context7__resolve-library-id

mcp__context7__query-docs

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 MSD 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 prior new-project setup — auto-creates .planning/spikes/ if needed.

<execution_context> @~~/.claude/msd-core/workflows/spike.md @~~/.claude/msd-core/workflows/spike-wrap-up.md @~/.claude/msd-core/references/ui-brand.md </execution_context>

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).
--wrap-up — Package spike findings into a persistent project skill for future build conversations. Runs the spike-wrap-up workflow.

Parse the first token of $ARGUMENTS: - If it is `--wrap-up`: strip the flag, execute the spike-wrap-up workflow - Otherwise: pass all of $ARGUMENTS as the idea to the spike workflow end-to-end.

Preserve all workflow gates (prior spike check, decomposition, research, risk ordering, observability assessment, verification, MANIFEST updates, commit patterns).

1.9 KiB Raw Permalink Blame History

1.9 KiB

Raw Permalink Blame History