agentleFS
Sign inStart free
sp1esp1e/claude-skills/gsd-spike/SKILL.md

gsd-spike

Skill1 starsChanged 31 days agoMITView on GitHub

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

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

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

    line 30
  2. Very specific:

    Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion.

    line 40
  3. Very specific:

    If it is --wrap-up: strip the flag, execute the spike-wrap-up workflow

    line 54

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<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 /gsd-new-project — auto-creates .planning/spikes/ if needed. </objective>

<execution_context> @$HOME/.claude/get-shit-done/workflows/spike.md @$HOME/.claude/get-shit-done/workflows/spike-wrap-up.md @$HOME/.claude/get-shit-done/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>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free