da4a86d8c1
Phase B-provide of epic #1258. Adds a build-generated skills/ dir + a skills manifest field so plugin-installed GSD exposes gsd-core:<skill> the native Claude Code way. Closes the gap where plugin-only installs lacked the skill surface because bin/install.js never ran. - scripts/gen-plugin-skills.cjs: build step converting commands/gsd/*.md to skills/gsd-<stem>/SKILL.md via convertClaudeCommandToClaudeSkill - .claude-plugin/plugin.json: add "skills": "./skills/" - package.json: add skills to files, gen:plugin-skills to build chain - tests/issue-766-plugin-manifest.test.cjs: Section H conformance (manifest field + dir + frontmatter + count parity) + C2 skills symlink - docs/adr/766-*.md: dated amendment adding skills surface row - .changeset/rapid-bears-hum.md: type Added - skills/: 69 generated gsd-<stem>/SKILL.md files (build-committed) Closes #1596
58 lines
2.1 KiB
Markdown
58 lines
2.1 KiB
Markdown
---
|
|
name: gsd-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
|
|
---
|
|
|
|
<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 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 prior new-project setup — auto-creates `.planning/spikes/` if needed.
|
|
</objective>
|
|
|
|
<execution_context>
|
|
@~/.claude/gsd-core/workflows/spike.md
|
|
@~/.claude/gsd-core/workflows/spike-wrap-up.md
|
|
@~/.claude/gsd-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>
|