a9a7a328e6
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
58 lines
2.1 KiB
Markdown
58 lines
2.1 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>
|
|
|
|
<runtime_note>
|
|
**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`.
|
|
</runtime_note>
|
|
|
|
<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>
|