skills.rest
AbdelrhmanUZaki
AbdelrhmanUZakiCOMMUNITY
Explore all skills by this author →
𝕏@abdelrhmanuzakiGitHub

gsd-spike

Spike ideas through experiential exploration and propose frontier experiments for future builds.

2|Updated Mar 7, 2025
Search Tags:#planning#codex#prototyping#experiment#spike#gsd#feasibility validation
One-click install
npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill gsd-spike-abdelrhmanuzaki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-spike
Source: https://github.com/AbdelrhmanUZaki/KnowledgeNuggets/tree/main/2-setup/shared/codex/skills/gsd-spike
Command: npx skills add https://github.com/AbdelrhmanUZaki/KnowledgeNuggets --skill gsd-spike-abdelrhmanuzaki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Validating whether an idea is technically feasible before committing to a full build is risky and unstructured. This Skill turns an idea into focused, verifiable experiments (spikes) that produce verified knowledge for the real build. ## Core Features & Use Cases - Idea Mode: Describe an idea and the Skill decomposes it into focused experiments, ordered by risk, with research and verification gates. - Frontier Mode: Run without arguments to analyze the existing spike landscape and propose integration and frontier spikes. - Wrap-Up Packaging: Use the --wrap-up flag to package spike findings into a persistent project skill for future build conversations. - Use Case: Before building a new real-time collaboration feature, spike the WebSocket sync approach to validate feasibility, then wrap up the findings so the actual build starts with verified knowledge. ## Quick Start Invoke $gsd-spike followed by a description of the idea you want to validate, or run it with no arguments to get frontier spike proposals.

Frequently Asked Questions about gsd-spike

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a technical idea before building it?▼

Invoke $gsd-spike with a description of your idea. The workflow decomposes it into focused experiments, orders them by risk, runs research and verification gates, and stores results in .planning/spikes/ for the real build.

What is frontier mode in a spike workflow?▼

Frontier mode runs when you invoke $gsd-spike with no arguments or the word 'frontier'. It analyzes your existing spike landscape and proposes integration spikes and new frontier spikes to explore next.

Can I skip the decomposition phase when spiking an idea?▼

Yes, pass the --quick flag to skip decomposition and alignment and jump straight to building. Use this when you already know exactly what to spike.

How do I turn spike findings into reusable project knowledge?▼

Run $gsd-spike with the --wrap-up flag. This executes the spike-wrap-up workflow, which packages spike findings into a persistent project skill available in future build conversations.

Does the spike workflow work in non-interactive environments?▼

Yes, use the --text flag to present questions as plain-text numbered lists instead of interactive prompts. The workflow waits for your reply rather than silently defaulting, unless you pass --auto or --all.

Related Skills

Explore More Software Engineering Skills→
amplitudeamplitude
142

craft-experiment-design

Generate complete experiment plans with hypotheses, metrics, guardrails, and duration.

Official
Advanced
jedmamostojedmamosto

gsd-spike

Validate product or engineering ideas through structured spike experiments.

Community
Intermediate
aslaiiaslaii

gsd-spike

Create single-question feasibility spikes stored in .planning/spikes.

Community
Intermediate
jzallenjzallen
1

build-one-to-throw-away

Structure throwaway prototypes with a three-phase build, learn, and rebuild process.

Community
Basic