6cfa0c55d2
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.
54 lines
1.9 KiB
Markdown
54 lines
1.9 KiB
Markdown
---
|
|
name: msd:spike
|
|
description: Spike an idea through experiential exploration, or propose what to spike next (frontier mode)
|
|
argument-hint: "[idea to validate] [--quick] [--text] [--wrap-up] or [frontier]"
|
|
allowed-tools:
|
|
- Read
|
|
- Write
|
|
- Edit
|
|
- Bash
|
|
- Grep
|
|
- Glob
|
|
- AskUserQuestion
|
|
- WebSearch
|
|
- WebFetch
|
|
- mcp__context7__resolve-library-id
|
|
- mcp__context7__query-docs
|
|
requires: []
|
|
---
|
|
<objective>
|
|
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.
|
|
</objective>
|
|
|
|
<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>
|
|
|
|
<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.
|
|
</context>
|
|
|
|
<process>
|
|
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).
|
|
</process>
|